ArchieThe Agentic Development PlatformRequest a pilot

Infrastructure, through your agent

Your agent asks.
Archie governs.

Developers get infrastructure by asking. Platform rules are built into every golden path, and every outcome is visible to the team.

Your agent, the UI or the API: every way in reaches the same governed platform.

Request a pilot

Self-hosted in your cloud
AWS · GCP · Azure · Kubernetes
Works with Claude, Cursor, Codex or any MCP agent

Archie's catalog: the published EKS Platform golden path with Deploy, and two drafts in their smoke tests

The control plane, not another agent

Your agents get a governed interface.
Your cloud stays yours.

Archie isn't an agent. Your engineers keep Claude, Cursor, Codex or any MCP client, and Archie is the control plane between them and your cloud.

ReasonYour agentClaude, Cursor, Codex or any MCP client, in your own flow.
GovernArchieRules, checks, approvals and a record of every decision.
RunYour cloudYour accounts and clusters. Your state, your repos.

How it works

Four things to know.

1Golden pathA governed recipe your platform engineer publishes once: the parts, the rules and a passing smoke test.find_golden_pathdeploy_golden_path
2AppWhat a developer gets by deploying a path: every part wired together, with its path and version on record.describe_app
3Add-onsMore parts for an app that's already running: a cache, a queue, a read replica.add_to_app
4Day-2 actionsUpgrade, rollback, drift fix and governed destroy, each previewed before it runs.upgrade_approllback_appremediate_appdestroy_app

The status quo

You already have a platform.
Nobody designed it for agents.

It accumulated over time. No one owns it, and now your engineers' agents are asking it for infrastructure.

waiting on tickets~~Every request is a ticket.~~Ask, and it's deployed.A developer asks their agent; a published golden path deploys without a ticket.
IaC complexity~~Infrastructure code is a specialty.~~Nobody writes the IaC by hand.Archie composes it from what you already trust; people answer a few questions.
found at audit~~Gaps surface at audit.~~Rules apply at deploy.Your org rules gate every path and request, and every decision is on record.

No platform team? One person owns the rules. Archie is the platform team you didn't have to hire.Already have one? Archie gives your agents the same governed golden paths to consume and extend, inside your existing standards.

Ways in

Three ways to ask.
One governed loop.

Your developer's agentClaude, Cursor, Codex or any MCP client asks in a sentence.
A Jira ticketA Jira Cloud ticket becomes a request, and the plan and receipt are written back to it.
The UIPick a published golden path from the catalog and deploy it with a form.

Whichever way it comes in, the same org rules, approvals and receipts apply.

Step by step

One request, from intent to day two.

No Terraform. No fifty-variable forms. No ten-tool stack to assemble. A request goes in; a governed golden path comes out.

Step 1 · Platform engineer

Confirm the intent

The platform engineer describes the path in plain language. Archie reads back every component it understood, and nothing is composed until they confirm.

EKS Platform golden patharchie MCP

The agent's chat: the ask, the tools it used, and Archie's reading of every component, with why it's there and what it installs

Archie's intent review: each component, why it's there and where it comes from, and the decision to confirm the intent, send it back, or decline — The ask and Archie's reading, side by side, before anything is built.

Step 7 · Platform engineer

Keep it healthy

Every deploy becomes stacks you can see. Fixing drift, upgrading, rolling back and tearing down each go through your agent, under the same rules.

Archie's Stacks view of the platform-eks deploy: nine stacks, each healthy and in sync, with cost and version — The developer's deploy as stacks: health, drift, cost and version for each.

The estate view shows how the stacks depend on each other. Every change after launch is one ask away:

DriftPut back what changed outside Archie.remediate_drift
UpgradeMove to the newer path version.upgrade_stack
Roll backReturn to an earlier version.rollback_stack
DestroyTear it down, with a receipt.destroy_stack

One workflow across clouds and clusters, with the IaC engines your teams already use.

AWS

Google Cloud

Azure

KubernetesTerraformOpenTofuPulumiHelm

And it connects to what you already have.

Git reposGitHubGitLabAzure DevOpsimport your IaC as-is
Existing clustersEKSAKSGKEenroll, don't rebuild
GitOpsArgo CDFluxa GitHub PR, for Helm workloads
NotificationsSlackdeploys, approvals, drift

Greenfield or brownfield

Start clean, or adopt what's already running.

GreenfieldStart clean

Describe what you needcompose_golden_path
Review the draft pathdescribe_golden_path
Prove it with a smoke test, then publishpublish_golden_path

BrownfieldAdopt what's running

Scan an account for what's runningscan_cloud_account
Plan the import: zero creates, zero destroysplan_adoption
A person approves; it's adopted in placein the UI

BrownfieldBring your IaC

Import your Terraform repo or Helm chartsimport_terraform_app
Get governed modules, wired into a draft pathdescribe_golden_path
Take over the existing state, without rebuildingadopt_terraform_state

Every step is a sentence to your agent, and Archie's MCP tools do the work. Approvals stay with a person.

Two surfaces

The tools act. The UI reviews and controls.

Both roles ask in plain language. What differs is the toolset each is handed, and what they're allowed to change.

The tools, to act

Compose, govern, deploy, operate.

ComposeDraft a golden path from a sentence, or import Terraform, Pulumi or Helm.compose_golden_pathimport_terraform
GovernOrg rules, approvals, and a smoke test before anything is published.set_org_rulepublish_golden_path
DeployDeploy a path, add to a running app, promote it between environments.deploy_golden_pathadd_to_apppromote_app
OperateDrift, remediation, upgrades, rollback and teardown.check_driftupgrade_stackrollback_stack

The UI, to review and control

Watch, confirm, approve, audit.

Archie's Stacks view: every deployed stack with its health, drift, cost and version

Refusals become your backlog

Every no is a signal.

When people and agents keep hitting the same refusal, it lands on the Decisions screen with a count. Either the rule is right, so keep it and say why, or the path should allow it, so change the path.

Archie's Decisions screen, Platform backlog: a deploy refused 5 times because its instance size and backup retention are outside the org's approved list, with Change the path and Keep the rule

Proof

Receipts, not claims.

A refused publishA path whose smoke test fails can't reach the developer menu. The failed run stays up for diagnosis, then is cleaned up.
The smoke testDeployed for real in your non-production account. A second plan must show zero changes and health checks must pass. Then it's torn down.
On camera, uneditedAn agent works a real Jira ticket through Archie, with no cloud keys of its own. Episode one, below.

Watch it run, unedited

EP01 · The ticketI gave an AI agent a Jira ticket — and no AWS keys.

Live run #002 · Part 1I asked an AI agent to put a real domain in front of a live app — without touching it.

Live run #002 · Part 2I let an AI agent compose a K8S golden path, then cutover to EKS behind the same domain.

All episodes on Rethink DevOps

Tested by the community

Platform Engineering Perú · YouTubePlatform Engineering Perú puts Archie through a live golden path, from the ask to a running app, in Spanish.

Who it's for

One platform floor, whoever you run it for.

One person owns the rules.

Your platform engineer defines the golden paths and your developers ask for infrastructure, both from their own AI agent.

Golden paths composed from what you already run
Org rules, approvals and smoke tests on every path
Developers self-serve, and every deploy is on record

Security

The agent asks.
Archie holds the keys.

Credentials stay in ArchieCloud credentials are encrypted with a dedicated KMS key inside Archie, and keyless connections store no secret at all. The agent never receives one.
Roles enforced on the serverEvery tool call is checked against the caller's role on the server, not just hidden from the menu.
Outside code waits for reviewA registry or generated module deploys only after a platform engineer approves that version.
Teardowns are gatedProduction and live-traffic teardowns wait for approval. Add a data-loss check and a snapshot before delete if you want them.
A record of every decisionEach golden path has a receipt, and every approval records who decided and when.

Self-hosted, in your own account.

Sign in with Google, GitHub or Microsoft; your own identity provider is coming
Credentials never leave your VPC
Your encryption keys, your state, your Git repo and IaC engine

Want to try it before installing? We can set up an org for you on our instance for a quick test.

No lock-in

You can always leave.

Stop using Archie and you lose the governance, the catalog and drift detection. Your infrastructure doesn't notice.

It runs in your cloud accountsEverything Archie deploys lands in your own AWS, GCP or Azure accounts and your clusters, and your own Archie keeps its state in your bucket. Stop using Archie and it keeps running, untouched.
Plain Terraform, applied with OpenTofuGolden paths are standard Terraform, not a format only Archie can read.
Export a path and run it yourselfOne call writes a golden path into your GitHub repo as Terraform: a directory per component, and a manifest of the deploy order and wiring.

Plans

Pick the shape of your platform.

Every plan includes the full governed loop. Plans differ in scale, hosting and who you run it for.

StarterSmall teams, one cloud

1 cloud account
Golden paths and any MCP agent
Drift, upgrade, rollback
Self-hosted in your account

Most teamsTeamPlatform teams, multi-cloud

Everything in Starter
AWS, GCP, Azure and Kubernetes
Role-scoped engineer and developer access
Approvals, smoke tests, fleet upgrades

EnterpriseSelf-hosted, regulated

Runs in your own account
Your keys, your state
Unlimited accounts and clusters
Custom org rules and publish gates

MSP & Cloud PartnerRun Archie for your clients

Multi-client workspaces
Shared catalog, sent to clients
Fleet view across every client
Per-client receipts

Pricing is set with each design partner during the pilot. Stop any time: what Archie built, and its state, stay in your cloud.

Design partner pilot · free · 4–6 weeks

Bring one workflow. Leave with a governed path.

Start with a scan. In week one, Archie scans your account (what's running, what it costs, what's ungoverned) and we plan your golden path against it together. Nothing is applied until you approve it.

Request a pilot

What you get

A findings report on what's running, and which changes your agents could make today unchecked
One governed golden path in your account, which you keep
Direct influence on the roadmap
A named or anonymous reference, your choice

What we ask

One workflow
One person with cloud access
Two or three short sessions
Honest feedback

Built by Greg Lazarus, a solutions architect who wanted repeatable infrastructure to be easier to deliver, and easier to govern.

Rethink DevOps

Your agent asks.
Archie governs.

Your agents get a governed interface.
Your cloud stays yours.

Four things to know.

You already have a platform.
Nobody designed it for agents.

Three ways to ask.
One governed loop.

One request, from intent to day two.

Confirm the intent

Compose from what you trust

Decide, then approve

Your rules, on every path

Prove it runs, then publish

Developers deploy it

Keep it healthy

Start clean, or adopt what's already running.