Deploy your first agent.

Before you start

Deploying an agent spends model usage, so it requires an active plan. Monthly plans start with a 7-day trial; during the trial you run one environment on trial hardware. You can fill out the whole deploy form without a plan to see how it works; only the final Deploy action is gated.

• Model access works out of the box with the managed key included in your plan.
• Prefer your own OpenRouter key? Connect BYOK on Account & Billing at any time, including during the trial.

Quick deploy vs. full setup

Quick deploy is the default: choose a template and a target, name the agent, and everything else, schedule, seed files, extras, comes from the template. The full setup flow reveals every step (Target, Template, Model, Environment, Schedule, Workspace, Extras, Review) so you can edit scheduled tasks and seed files before the agent goes live.

The deploy walkthrough

Six decisions take you from an empty form to a running agent.

1. 1Pick a templateThe template decides what the agent does: its scheduled tasks, seed files, and packages. Search the catalog by name or description, filter by category, or start from the curated starter template. Each template declares which runtimes it supports and, sometimes, a minimum environment size. You can also author a custom template under Templates.
2. 2Pick or create an environmentAn environment is the isolated cloud machine your agents run on. If you have none, create one inline from the deploy page: give it a name and pick a size. Bigger environments hold more agents (see the size table below). Every environment, including your first, draws credits by the hour at the rate shown for its size, up to your plan's environment count and size ceiling.
3. 3Name the agentThe name becomes a slug that must be unique on the environment. Each agent runs isolated under its own system user on the machine.
4. 4Choose the runtime and modelTemplates declare their supported runtimes; when there is only one, it is locked. The model defaults to your organization default; change it only when this agent needs a different one. Some model tiers are plan-gated.
5. 5Provide secretsTemplates that need credentials prompt for them. Reuse saved secrets from your vault (opt-in, per deploy) or type values directly; they are sent once over TLS and written to the agent's .env file. When the template needs an OpenRouter key, the platform-managed key (or your connected BYOK key) is injected automatically.
6. 6Deploy and watch the first runThe deploy runs as a tracked job with live progress. When it succeeds, open the agent to watch its first run, read its logs, and send it a message. Deploys that modify the template's tasks or add new env vars go through a safety review first; high-severity findings block the deploy with an explanation.

If something blocks the deploy

The form surfaces the common blockers before the backend does, with a specific fix for each.

• Environment full: each size caps how many agents it can hold. Resize the environment or pick another.
• Below the template's minimum: some templates need an environment that holds more agents. Create or resize to at least the capacity the template asks for.
• Duplicate agent name: the slug must be unique on the environment; the form suggests a free name.
• Billing, capacity, or plan errors: the deploy reports exactly what to change, fix the subscription, resize, or pick a model your plan allows.