Infrastructure from the pipeline
Your CI/CD pipeline creates environments instead of someone clicking in the Cockpit. Whatever the interface can do, the API can too, with separate credentials and scopes per application.
The entire platform is built API-first: whatever the Cockpit can do, your pipeline can do too. Where standards exist, we speak them – S3 for storage, OpenTelemetry for logs, OIDC for login.
Applications authenticate with their own credentials and scopes.
Existing SDKs and tools keep working – no lock-in.
Resources separated by project, with roles per team.
Your CI/CD pipeline creates environments instead of someone clicking in the Cockpit. Whatever the interface can do, the API can too, with separate credentials and scopes per application.
Your SaaS product should automatically provision resources for every new customer. Your application calls the API – database and domain are up without your team stepping in.
You switch the platform, not your tools: storage speaks S3, logs arrive via OpenTelemetry, login runs over OIDC. Existing SDKs keep working.
Several teams or customer projects share one organization. Resources are separated by project, and roles define who may automate what.
One million API requests are free every month.
REST API comes in three operating models – and you can switch at any time as your team grows or wants to focus on other things.
You automate yourself – with API, MCP and your own pipelines.
We set up projects, access and pipeline templates for your team.
We take over CI/CD and automation as your DevOps department.