Make operations repeatable without broadening access

Manage resources through the interface or code with keys and roles attached to each project scope.

One access model for the interface and code

The API, declarative configurations, pipelines and MCP-compatible integrations act on the same resources and respect project scope.

Make operations repeatable through APIs, pipelines or declarative configuration with project-scoped access.

Public API and CI/CD
Manage resources with a project key and integrate deployments into your pipelines.
Stack engine
Describe a project in YAML or JSON, preview changes, apply resources and export the current state.
MCP server
Connect any compatible client to the SailOps MCP server and use structured actions with a project scoped key.
Projects, members and roles
Organize resources by project and assign suitable access to technical, finance or read only team members.

01
Define the scope
Create the project, assign roles and use a key limited to the resources concerned.
02
Describe the actions
Use the public API, a YAML or JSON stack, or a compatible client connected to the SailOps MCP server.
03
Connect your delivery workflow
Preview changes, apply resources and connect deployments to your CI/CD pipelines.

Review compute, memory, data, storage, traffic and observability separately before configuring a project.

Connect your tools directly or discuss access, pipelines and resources to automate with the team.