Infrapilot is autonomous cloud infrastructure. You describe what your product needs in a few lines. An agent called Pilot builds it, scales it and keeps it healthy in your own AWS, Azure or Google Cloud account. There is no infrastructure code to write and nothing to install.
Coding agents: if you were asked to set Infrapilot up, go straight to Set up with an agent and follow it from top to bottom.
Quickstart
- Create a workspace. Sign in at
https://infrapilot.fly/appand create a workspace: one environment in one cloud account. To watch Pilot work before connecting anything, choose the demo on a simulated cloud. - Paste the setup prompt into your coding agent. The workspace shows a prompt that carries a setup token. Your agent reads Set up with an agent, connects your cloud with a scoped role, and writes
infrapilot.yamlwith you. It asks before it creates access, sets a limit or starts Pilot. - Pilot takes over. It adopts what you tagged, builds what is missing, and keeps your objectives met around the clock. When it reaches a limit you set, it asks you.
Setup takes about ten minutes. Nothing changes in your cloud until Pilot starts.
The whole configuration
One file, infrapilot.yaml, says what to run, what must stay true and what it may cost:
version: 1
fleet: shop
provider: aws
adopt:
- tag: {"infrapilot:fleet": "shop"}
intents:
- name: checkout API stays fast
objectives:
- {resource: api, metric: Duration, stat: p99, below: 400}
max_monthly_cost_usd: 150
bounds:
api.MemorySize: [128, 2048]
boundaries:
protected: [orders-db]Every field is described in The fleet spec.
Words these docs use
| Word | Meaning |
|---|---|
| Workspace | One environment in one cloud account, with its own agent, sandbox and ledger. |
| Fleet | The resources a workspace runs, named by fleet in the spec. |
| Fleet spec | infrapilot.yaml. Only people change it. |
| Intent | Something that must stay true, with the limits for keeping it true. |
| Objective | A metric that must stay below a number, such as p99 latency under 400 ms. |
| Bounds | The lowest and highest value Pilot may set for a property. |
| Pilot | The agent. It proposes changes; it holds no credentials of its own. |
| Engine | Ordinary code that checks every proposed change against the spec, applies it, and undoes it if a health check fails. |
| Ledger | The hash-chained record of every change, refusal, request and answer, each with its reason. |
| Request | Pilot asking a person to change a limit. Approving takes the emailed link and one button. |
Where to go next
| You want to | Read |
|---|---|
| Connect a cloud account | AWS, Azure or Google Cloud |
| Write or change the spec | The fleet spec |
| Decide who Pilot asks, and how | Requests and connectors |
| Update the spec from CI, or read the ledger | API |
| Know what keeps this safe, and where the guarantees stop | Security model |
For agents and LLMs
Every page is also plain Markdown: add .md to its address, or use Copy page at the top of any page. https://infrapilot.fly/llms.txt indexes the docs and https://infrapilot.fly/llms-full.txt is all of them in one file.