Skip to content

Cookie preferences

Choose which cookies and similar technologies this site may use. The strictly necessary ones keep the site working and remember this choice, so they cannot be turned off; they store nothing that identifies you or follows your browsing. Read the cookie notice

Continuumship
Menu

Delivery as code

Your delivery process as code, managed from your own agent.

Flows, guardrails, routing and budgets are definitions in a documented schema. Every change is a plan a person approves before it applies, whether it came from the panel, the command line or your agent.

Talk to us Features
Definitions live in your repository; your pipeline applies the plan a person approved.

Why as code

Forty projects should not take forty afternoons to set up.

  • Configuration drifts, and nobody knows where.

    Each project was set up by hand, a little differently, and no record says how.

  • Platform teams cannot review process changes.

    A workflow edit on a settings page has no diff, no review and no history anyone can read later.

  • Our agents write code, not our delivery setup.

    Asking an agent to configure delivery means handing it credentials nobody would sign off on.

How it works

Definitions, plans, decisions — and a record.

Definitions in your repository

Keep definitions in .continuumship/ in your repository. Your pipeline syncs them by its own identity, against a trust that names what that repository may define.

  • Flows, guardrails, routing, budgets and standards
  • An edit in the product becomes a merge request
  • One manager for each definition, never two

Change sets with a plan and a decision

A change set is a plan: hashed, decided where a decision is needed, applied in order and verified. "Set up my projects" becomes a plan a person approves.

  • Discovery proposes what to Bind, Create, Leave and Decide
  • Drift shown once, and resolved by a person
  • What we do not manage is never reverted

Managed from your own agent

Your agent connects over MCP. It reads definitions, starts discovery, proposes and plans. It cannot approve. Standards roll out to Areas in waves that halt on the first failure.

  • Management scopes a run's credential never carries
  • Repository context every agent receives, nearest first
  • A context file describes and never grants

Questions about delivery as code

Do we have to keep definitions in Git?
No. A definition is managed by the registry, by a path in your repository, or by another system, one manager each. Move a definition to your repository when your platform team wants to review it there.

What does discovery read?
Connection metadata on the platform, and your repositories on your runner. It reports typed facts with their source and method — parsed, observed or inferred — and proposes a setup a person approves.

What happens when someone changes a setting by hand?
Drift is shown, and raised once to the owner Area's maintainers. A person resolves it. Continuumship never reverts what it does not manage.

What can our agent change over MCP, and who decides?
It can read, propose, plan, request a decision and withdraw. It cannot approve. Management scopes are separate from any run's credential, and applying without a decision stays off unless an owner allows it for named, low-risk kinds.

Keep reading

The rest of the control plane.

Design how your company ships software.

Start with a thirty-day shadow pilot on one Area: connect, observe, read the report together, decide.

Talk to us Pricing