Before you enter
What do you need today?
Choose a Cycloid homepage related to your need, or close this box for a general overview. You can always switch homepage with 1-click.
Here for the AI side? See how assistants build on Cycloid ↗
Set guardrails once*. Stop maintaining glue.
*Environments, naming rules and four-layer authorisation, set once on an internal developer platform. Developers self-serve inside them from Day 0.
In production with
Platform engineering is the impossible job
Every new layer makes your job heavier. More tools to stitch together, more consoles to check, more things to be accountable for, and the same sized team. Six months later the queue is still growing.
You didn’t take the job to write glue, police naming conventions or rebuild CI that already works. That’s where the week goes, and every new request lands on the same team.
518 platform teams surveyed: 29.6% don’t measure success at all, and 47.4% run on under $1M a year. DORA has a name for where most of them end up: the “Ticket-ops” trap.
29.6%
Platform teams measure nothing
90%
Have a platform (DORA, 2025)
47.4%
Platforms run on under $1M
63%
Devs say leaders don’t get it
Product tour
Watch one request go from form to production
<1hr
New environment at Alchemy
5–10
Deployments a day at Hotel Spider
<4 weeks
To full production at cloudXcelerate
4x
Faster delivery at Orange Business
Customising, for platform teams
Design it yourself.
Just not from scratch.
A bank and a logistics company don’t share the same idea of dev freedom – and no vendor should tell you how much freedom devs should have either. You set the rules in Cycloid: golden paths and Form fields in the Blueprint, then environment types, naming, and approvals across the platform.
The engine underneath comes with the platform. Policy checks run when a Form is submitted, before anything’s created, with four-layer authorisation and the audit trail already in place. We maintain the engine, you own the Blueprints.
For you: When your org changes a process, you edit a Blueprint and every Form built on it picks it up. You shape the views every resource of that type shows. There’s no portal fork to rebase at the next release.
An assistant meets the same design. It will find any gap you leave.
A successful platform provides enabling constraints while offering enough flexibility for teams to use the right tools for their specific jobs.
DORA Platform engineering capability, January 2026
Under the hood
Swap any layer. Keep your stack.
Your Terraform and OpenTofu, Ansible and Helm stay yours. Each layer is documented and replaceable, and what you build is stored in open formats, so you can see how the platform works before you trust it with yours.
Deployment model, SSO, four-layer authorisation, environment types and naming rules. Set once, enforced everywhere.
The catalogue, dependency graph and adoption analytics show whether the golden path is being used.
Publish Blueprints and Forms. Developers deploy, run and promote inside the rules you set.
Build vs buy
Build it? Price it first.
What your team builds, then maintains, for every layer.
In-house
Portal customisation
Fork the UI, then carry the fork
Sidebar, resource pages and branding set in the portal
Maintenance cost
You own and maintain everything you build.
We maintain it, you own Blueprints.
Governance enforcement
Advisory or bolt-on – issues found in audit, not prevented at the source.
Policy checks run at Form submission. A non-compliant resource is never created.
Day-2 operations
Separate runbooks and tooling. The audit trail is incomplete.
Day-2 Actions live in the Blueprint. Same chain, same audit trail as Day-1.
The same request, end to end
Same staging request. Nobody on your team touches it.
Here’s how it plays out with and without Cycloid.
D0Opens a ticket, describes the environment in proseD2Platform team asks which region, which size, which accountD4Security asks who will have access, and for how longD8Someone hand-writes the Terraform or OpenTofuD11Deployed, untagged, invisible to the inventory
T+0Picks “Staging environment” from the catalogT+3Region, size and owner are fields on the formT+4Policy result on the same screen, before submittingT+7The Blueprint already contains the Terraform or OpenTofuT+9Live in the inventory and the audit log
Write Blueprints, not compliance reports
ISO 27001 certified, B Corp score 95. Your team writes Blueprints instead of assembling the compliance case.
ISO 27001 Certified
B Corp Certified
IDC Market Glance
COOL VENDOR 2024
Cool Vendor 2024
The developer fills a Form.
The environment exists, named by your rules.
Already built, so you don’t start from scratch
01
A customisable portal, your layout
You set the tabs every resource of a Blueprint gets. Team leads own their pages and sidebar sections, your logo and colours sit on top, and nobody maintains a fork.
02
Plug-ins for the tools you already run
Official and custom plug-ins, a documented API and an MCP server. Nothing to rip out first.
03
The same access rules for people and assistants
Your organisation model and SSO through Entra ID, Okta, Keycloak, OIDC or SAML, then four-layer authorisation on every Action. If a check can’t decide, the answer is no, and every change lands in the audit log.
04
Your environments, your naming rules
Predefine environment types for every form, Blueprint and promotion path, and enforce naming rules. Nobody creates “staging-2-final”.
05
Runners you control
Native runners on your infrastructure, alongside the CI you already have. You don’t re-specify pipelines that work.
Deployment
Deploy it where your infrastructure already lives
Works with the Terraform and OpenTofu, Ansible and Helm you already run, and with GitHub Actions, GitLab CI or any CI through a webhook.
Bring your stack
Terraform
IaC
OpenTofu
IaC
Ansible
Config
Helm
Kubernetes
GitHub Actions
CI
GitLab CI
CI
Jenkins, Azure DevOps, CircleCI, Bitbucket Pipelines, Argo Workflows, Your own scripts
via webhook
Cycloid
Run it on
What it means
Where your data sits
Self-hosted, on-prem or bare metal
Every module on your infrastructure, next to your runners and CI.
Your network. Air-gapped, OIDC-first.
Dedicated SaaS
We run every module in an account you pick. You keep the Blueprints.
Isolated account on AWS, Azure, GCP, Scaleway, OVH or Outscale.
Hybrid
Control plane managed by us, native runners in your environment.
Workloads and runners stay local.
SaaS
Fully managed, nothing to upgrade.
EU-hosted available.
One portal for the European Commission's sovereign multi-cloud
How Cycloid became the self-service front door to the Commission’s sovereign cloud framework.
Self-service portal
Replacing a 10-year-old in-house & ITSM interface with a modern developer experience
4 clouds, 1 portal
Developers can access any environment they need, without infra knowledge or waiting.
Bought, not built
Cycloid works in existing brownfield IT ecosystems. No need for bespoke solutions.
Watch a step disappear from your week
Bring your worst provisioning flow. Most tickets, or the longest wait. In twenty minutes, see where the Blueprint Form replaces it, and whether your pattern actually fits.
