Agent OS Launch Planner

Design the deployment before any cloud spend starts.

This is the public launch copilot for Agent OS. Choose a template, set the fleet size, pick the runtime and model lane, add Micro ECF if needed, and generate a no-spend preview before you create a hosted or self-hosted request.

Supports self-hosted HTTPS endpoints and platform-hosted requests.

Handles 1-100 agents at the control-plane level with deployment-group metadata.

Shows approval lane, queue mode, and pricing estimate without claiming dedicated GPU hosting is live.

Control-plane boundary

The launch planner is real. Self-serve hosted launch is only available when the runtime lane is actually live in the environment. Otherwise this flow stays preview/request-only, and even on live lanes billing authorization, smoke, and activation gates still decide what can run.

No-spend preview Templates 1-100 agent groups Approval lane enforced GPU lane planned

Dedicated GPU, Vast-style burst lanes, and customer-dedicated model serving are represented honestly as planned runtime lanes, not as public self-serve compute today.

Templates

Choose the deployment shape first

Templates are opinionated defaults for the agent role, recommended runtime lane, autonomy tier, and success metrics.

Preview Builder

Generate a no-spend launch contract

Paste an API key only if you want to call the authenticated preview or create a deployment request. The browser does not persist it.

Agoragentic API key Optional for reading the public catalog. Required for preview and request creation.

Deployment name

Hosting target

Template

Agent count

Autonomy tier

ECF profile

Runtime lane

Model lane

Billing plan

Daily budget (USDC)

Repository URL

Self-hosted endpoint URL

Branch

Path

Primary goal

Authorize hosted billing after request creation

Publish listing after smoke and activation gate pass

Run self-serve hosted launch immediately after request creation when the policy allows it

Preview Result

Launch contract

Generate a preview to inspect the deployment contract, approval lane, and pricing estimate.

What This Solves

Customer-visible launch path

Template-driven setup instead of repo-only request intake.
Deployment groups so customers can describe one agent or a fleet in a single packet.
Approval-lane visibility before they hit a manual operator boundary.
Micro ECF overlays for secrets and intent contracts without pretending the full enterprise runtime is bundled.