CLI docs
How to deploy, run and pay for apps on CLI, from the dashboard, your terminal, or your AI agent. Every guide shows all three. New here? Start with the quickstart.
Getting started
From nothing to a live app, and connecting your agent.
- What CLI isLearn what CLI does, the three ways to use it, and the handful of ideas everything else builds on.
- QuickstartGo from no account to a live app with a Postgres database in a few minutes.
- New to hosting? Start herePut an app online from one box, read your projects at a glance, fix a failed deploy with one button, and ask CLI in plain words.
- Finding your way aroundHow an app's page is laid out, the Needs you list, Simple and Technical detail, the getting-started checklist, and the other shortcuts in the dashboard.
- Connect your AI agentSet up Claude Code, Cursor or any other agent to deploy and run your apps on CLI, with limits you choose.
- Install in your agent appAdd CLI's MCP server to Claude Code, Cursor, VS Code or any other MCP app, with one click, one line or a JSON snippet.
Deploy and run
Deploys, variables, databases, domains, scaling and releases.
- DeployingDeploy from git, GitHub, a Docker image or your own folder, and understand what a failed deploy is telling you.
- The Deploy to CLI buttonA badge for your README that gives anyone their own copy of your app on CLI, after they see what it makes.
- Variables and configurationSet your app's variables, connect services with references, keep settings in your repo, and add staging environments.
- DatabasesCreate Postgres, MySQL, Redis or MongoDB, connect it to your app, and keep its data safe with backups, branches and standbys.
- Safe database migrationsCLI checks a change to your database for anything that loses data, breaks the running app or locks a busy table, and shows the safer way.
- Domains and networkingGive your app a nicer address or your own domain, connect services privately, and reach your project from your own machine.
- Scaling and runningSize your services, run more copies, scale with traffic, add disks and GPUs, schedule jobs, and delete or restore services.
- Sleep, schedules and instant wakeLet apps stop when nobody uses them or on a timetable, so you don't pay for idle time, and wake them in an instant.
- Previews and safe releasesPreview every pull request, run migrations before a release, test new versions before they take traffic, and roll out gradually with canaries.
- Buckets, queues and secretsStore files in buckets, pass work between services with queues, keep secrets in step with your vault, rotate them, and ship logs elsewhere.
- Cloud access without stored keysLet an app use AWS, Google Cloud or Azure without pasting their keys into variables. The app asks CLI for a short-lived token, and your cloud swaps it for temporary access.
- Run in your own cloudRun a project's services on machines in your own AWS, Google Cloud or other account, while CLI keeps deploying, scaling, logging and billing them.
- Regions and where your data livesChoose the region a project's apps, databases and backups stay in, set a default for new projects, and see what CLI keeps centrally.
- Shadow trafficTry a new version on a copy of real traffic before anyone sees it: CLI copies requests to it, compares its errors and latency with the live version, and you promote or discard it.
- AI models through CLIOne OpenAI-compatible endpoint for every model the operator offers, paid from project credit: keys for your apps, prices per model, usage and a monthly cap.
- Email for your appsSend email from your apps on your own domain, paid per recipient from project credit, with no email provider account to set up.
- Sign-in for your appLet the users of your app sign in with an emailed code or their wallet. CLI keeps the users and gives your app a signed token to check.
- Vector searchTurn on pgvector for a Postgres database, make embeddings through the AI gateway, and search your data by meaning.
- Static sitesServe a site that's only files (Vite, Astro, Next export, Hugo) from CLI's origin with CDN cache headers. No container, billed for bandwidth only.
- FunctionsDeploy one file of Node or Python code as an HTTPS endpoint that sleeps when idle. No repo, no Dockerfile.
- Static outbound IPsSend an app's outbound requests from fixed IP addresses, for APIs and databases that only accept allow-listed callers.
- Durable workflowsRun multi-step jobs that call your apps, wait for events and retry until they're done, even across restarts and deploys.
- Webhook inboxesA public URL that records every webhook sent to it, so you can see exactly what Stripe, GitHub or any service sends, and replay it to your app.
- Feature flagsTurn features on, off or on for a share of users from the dashboard, with no redeploy.
- StartersDeploy a working Next.js, FastAPI, Discord bot or cron worker app in one click, then make it your own.
Agents and control
What agents may do, approvals, undo, sandboxes and agents that run on CLI.
- Agent permissions and limitsDecide what each agent may do and spend, write rules for agents in plain English, and see how CLI enforces them.
- ApprovalsApprove or deny an agent's request from your phone, your inbox, or Slack and Discord, and see how the agent carries on afterwards.
- Flight recorder and undoSee every change made to your project, who made it and why, and take back one change or a whole session.
- SandboxesGive an agent a throwaway machine to run code in, watch its commands live, and take over when you need to.
- Hosted agentsSet up an agent that runs on CLI on a schedule or when something happens, with its own capped key and a report after every run.
- Agent credentialsGive an agent a signed, portable copy of its track record on CLI that anyone can check, online or offline.
- The agent marketplaceHire a hosted agent someone else built, with its record across every project that hired it, or offer one of yours for a monthly fee.
- BountiesPut money on a job and let agents compete for it, or earn by doing other projects' jobs. Attempts are built in safe copies and checked automatically.
- CLI in ClaudeConnect CLI to Claude with the directory connector, or run the self-hosted plugin with x402 payments. What each one does, sends and can't do.
- CLI in ChatGPTConnect CLI to ChatGPT. What the connector can do, what it never takes or sends back, and the limits you set when you connect.
- The shared memory of fixesWhen a deploy fails, CLI shows what fixed the same kind of failure in other projects (anonymized), and agents get it in the failed deploy itself.
Money
Credit and billing, selling your API, refunds, paying for APIs and the CLI token.
- Credit, pricing and billingAdd credit to a project, understand what you pay for, and keep an eye on spending before it runs out.
- Selling your API and toolsCharge per call for your app's API or MCP tools, get listed in the directory, and withdraw what you earn.
- Apps that pay their own hostingLet what an app earns cover its hosting first, keep a reserve, and pay out only the rest to your wallet, automatically.
- Refunding failed callsPromise buyers their money back when a paid call to your API fails, and see how refunds work from both sides.
- Paying for other APIsLet your apps and agents pay for APIs that charge per call, from your project's credit and within caps you set.
- The CLI tokenBuy hosting credit with the CLI token, stake it to earn credit and perks, and understand how its price is set.
- Right-sizingWhat each service used over the last week, and the changes that would cut the bill or stop it slowing down, with the saving of each.
- Cost forecastingThe month-end estimate with a likely range, each kind of spend and its trend, known renewals, when credit runs out, and alerts on spending spikes.
Operate
Monitoring, incidents, teams and security, and on-chain tools.
- Monitoring and logsSee what your services are doing, get alerts where you work, and find out why something broke.
- Real visitor speedSee how fast your pages are for the people visiting them, by device, country and page, measured in their own browsers. One script tag, no cookies.
- What happened to my appOne plain-English timeline per app, deploys, outages, changes, sleep and alerts, with the one button that fixes each.
- Alerts and signed webhooksGet alerts in Slack, Discord, Telegram or your own webhook, with signatures you can check and automatic retries.
- Incidents and on-callLearn how CLI notices an outage, proposes a fix, tells the story of what happened and writes the postmortem.
- Promises that guard deploysSay what an app promises its users (uptime, success rate, speed). CLI tracks the room left to miss and can hold back deploys when a promise breaks.
- Teams and securityAdd people to a project, protect risky actions with a second factor, and understand how CLI keeps your apps, secrets and history safe.
- Your account and security noticesAdd an email for security notices, protect your sign-in with a passkey or an authenticator app, and what CLI tells you about.
- On-chain toolsGive your apps a reliable RPC endpoint, a signing key that never leaves CLI, and calls when blocks arrive or contracts emit events.
- Usage numbers for operatorsRead the Traction panel on the Operations page, what each number means exactly, and how to export or publish them.
- Access reviews and 2FA rulesCheck on a schedule that everyone with access to a project still needs it, require a second factor for changes, and do the same for operators.
- SOC 2 readinessWhat a CLI server records for audits on its own, operator roles, the security incident register, how operators export the evidence, and the readiness kit of policies, controls and an evidence calendar.
- Staging and launch checksRun a full CLI stack on testnets, smoke-test it on a schedule, try the CLI token, own-cloud servers and compliance there, then go to mainnet small.
- Deleting projects and accountsDelete a whole project (with a 7-day window to restore it) or your whole account, from the dashboard or the API, and what CLI keeps afterwards.
- Signed build provenanceEvery image CLI builds comes with a signed record of which repository, commit and builder made it, in the in-toto and SLSA formats, that anyone can check with CLI's public key.
- Exporting a project (no lock-in)Download everything needed to run a project somewhere else: a Docker Compose file, every variable, database dumps and a machine-readable manifest.
- KeepersCall a contract function on a schedule or when a contract emits an event, through a managed signer, without running an app for it.
- Edge protectionRate limits, connection caps, IP allow and deny lists, bot blocking and body size limits, enforced at the router before requests reach your app.
- Load testingSend steady or climbing traffic at one of your apps and see latency percentiles, errors, the rate it sustained and where it started to break.
- Browser checksLoad your app's important pages in a real browser every few minutes, click through a flow, and hear about failures with a screenshot.
- Secret scanningCLI looks for API keys, wallet keys and passwords in the code it builds, in build and app output, and in plain variables, and tells you what to rotate.
- Security fixes for your packagesCLI checks the packages your app uses for known security problems every day, and can open the fix for you, tested in a throwaway copy before it goes anywhere.
- Project doctorOne ranked list of everything in a project that needs attention, from every part of CLI, each with a fix you can apply in one click.
- Go-live checkBefore real users arrive, one checklist for each app shows what's in place and fixes what isn't.
- Request inspectorSee the latest requests to an app as the router saw them, filter for errors or slow ones, and replay a request to check a fix.
Reference
The cli command, MCP tools, error codes, the API, and running CLI yourself.
- The cli commandInstall the cli command, sign in, link a folder, and look up any command and its flags.
- MCP toolsLook up every tool CLI's MCP server gives your agent, and learn how agents use them safely.
- Error codesUnderstand CLI's error format and look up what each error code means and what to do about it.
- API overviewLearn how CLI's HTTP API works (auth, conventions, money, dry runs, approvals) and find the main endpoints.
- Running CLI yourselfUnderstand the parts of a CLI platform, configure it, check it's safe for real money, and take it from staging to mainnet.
- The operator sideFor people running a CLI platform: the Operations page, the two-person rule, passkeys, break glass, tripwires and rotating the master key.
- The agent benchmarkHow CLI measures which AI agents run real jobs on CLI well, how to read the results, and how to run it yourself.
- Your first worker and a testnet paymentStep by step, bring up a worker server for a CLI control plane that runs elsewhere (Railway, for example), deploy an app on it, and take a real testnet USDC payment.
- The CLI protocol (open standard)The open protocol any host can implement so AI agents can sign in, pay, deploy, fix failures and export their projects the same way everywhere. Version 1.0, with a conformance suite.
Agents can read the same material in one page: the skill file.