Solutions / Self-service
Self-service that doesn't stop at deploy: run, promote and compose in one portal
Give developers everything they need, when they need it, without waiting. Your platform team publishes the golden paths. Developers deploy, run, promote and compose inside them, with no ticket queue on a structured path. People and AI assistants get the same checks.
Developers
Pick a golden path, fill in a form, get an environment. Then run it and promote it yourself. No ticket queue, and approvals only where a rule asks for one.
Platform & DevOps
Publish Blueprints once and every request runs through them, checked before anything’s created.
Executives
Delivery moves at the speed of the team that needs it, on infrastructure your organisation still controls.
Why
Code gets faster every year. The ticket queue doesn't.
The gap sits between a developer who needs an environment and the platform team that has to build it by hand – safely, correctly, and after the other twelve requests.
Without it
The ticket queue
Every environment is a request, every request is a queue, and the platform team is the queue. Developers wait, then work around it. The workaround is shadow IT, and the bill for it arrives later.
Signs it’s your problem
- A dev environment takes days, so people share one or skip it
- The platform team spends its week on requests, not the platform
- Console-built infrastructure appears that nobody codified
With Cycloid
Golden path or compose, both governed
Take a golden path: pick a Blueprint or fill in a Form. Or compose from scratch: the compute, data and storage you need, inside the limits the parent sets. Either way the authorisation chain checks every request and the Native Runner runs it. The platform team gets its week back.
What changes
- A developer deploys, runs and promotes without joining a ticket queue
- The checks run before the resource exists, so it’s compliant on arrival
- The same path serves a person or an AI assistant, with the same checks
The trade-off · speed vs control · self-service keeps both
How
From one Blueprint to production, in four steps
One path, written once, used by everyone. Each step has its own page with the detail.
Platform team
01
Publish a Blueprint
Wrap an existing Terraform, Ansible or Helm module as a Blueprint, with the guardrails already inside it.
What
Eight features behind every self-service request
Each has a page of its own. Here’s what it does, how, and who it’s for.
In this pillar
Blueprints & golden paths
Packages infrastructure and delivery as a pre-approved path a developer can deploy without joining a ticket queue.
Built on your existing Terraform, Ansible and Helm. Developers can compose their own environment from it, inside the limits the parent sets.
Built for
Platform & DevOps
Developers
Self-service catalog
Lists every published path, scoped to the requester’s role, team and Resource Group.
Scoped by the four-layer authorisation model, so the catalog you see is the catalog you can use.
Built for
Developers
Executives
Forms
Turns a module into a form with only the fields a requester may change, validated before submission.
The Form validates every field, then the authorisation chain checks the request before anything’s created.
Built for
Developers
Platform & DevOps
Promotion Path
Promotes an environment or an application version from dev to QA, staging and production.
The platform team sets the gates, such as soak time, an approval or a scorecard at Silver or above. The promotion checks them first.
Built for
Developers
Platform & DevOps
Day-2 actions
Runs what follows a deploy, such as scale, restart, upgrade or run a plan, from a page that shows what the resource depends on.
Defined in the Blueprint and run by the Native Runner or your own CI, with the same checks and audit trail as the first deploy.
Built for
Developers
Platform & DevOps
Approval workflows
Routes a request to the right approver when a rule says one is needed, and lets everything else through.
Approval rules route the request and record the sign-off in the audit trail, next to the change.
Built for
Platform & DevOps
Executives
Work with your AI assistant (MCP)
Lets Cycloid’s own assistant, or any MCP host you use, request and run Forms and Actions.
Same rules, whoever’s asking. Hold an assistant below its user’s rights, read-only or no destroy.
Built for
Developers
Platform & DevOps
Executives
Integrated Blueprints and Forms
Built for
Developers
Platform & DevOps
The whole picture of the Self-service pillar
One path, and where it leads
One path, written once, used by everyone. Each step has its own page with the detail.
Bring the request that's always in the queue
The most tickets or the longest wait. In twenty minutes we’ll show you it as a golden path.