Available frameworks
Plans
Current per-hour pricing for each plan is shown in the Create Instance dialog and on each instance’s details page.
Billing
Two separate line items make up the cost of a hosted agent:- Compute — a per-hour rate for the instance itself, billed only while the instance is active (creating, starting, running, or stopping). A stopped instance costs nothing.
- Inference — whatever the agent spends on model calls. Each instance gets its own DeepInfra API key, and its LLM usage is billed at standard token prices against your account.
Fair use: instances that exceed an average of their plan’s included network transfer per month (inbound + outbound, prorated by uptime) may be temporarily paused. You can start the instance again from the dashboard once usage normalizes.
Create an instance
1
Add an SSH key
Register your public SSH key at Dashboard → SSH Keys. It’s installed on every instance you create, and you’ll need it to connect over SSH.
2
Open Hosted Agents
Go to Dashboard → Hosted Agents and click Create Instance.
3
Configure and create
Pick a Name (up to 64 characters), an Instance Type (the agent framework), and a Plan, then click Create.
4
Wait for it to come up
Setup is fully automated and takes a few minutes. Once the instance is
running, connect via the dashboard link (OpenClaw) or SSH (any framework).Instance lifecycle
Stopping an instance shuts it down so you’re not billed for compute while it’s idle. Starting it again restores everything as it was.
Manage an instance
From the instance list or its details page you can:- Start / Stop — pause compute billing without losing state.
- Update — when a newer framework version is available, upgrade in place. No restart needed; the agent may be unresponsive for a few minutes.
- Backup — trigger a snapshot on demand (see below).
- Delete — stop and permanently remove the instance. This cannot be undone.
DeepInfra retains administrative SSH access to your instance to automate maintenance tasks (update and restore from backups for example).
Backups
Backups are created automatically every 24 hours, and one is also captured whenever you stop the instance. Snapshots older than 5 days are cleaned up, with at least 2 always retained. You can create one manually anytime with Create Backup on the details page. To roll back, pick a backup in the Backups table and click Restore.HTTP API
Everything above is also available programmatically. Authenticate with your API key. Create an instance:GET /v1/agents/catalog (frameworks, plans, and current pricing), GET /v1/agents/{instance_id}/backups, POST /v1/agents/{instance_id}/backup, and POST /v1/agents/{instance_id}/backups/{backup_id}/restore. See the API Reference for full schemas.
FAQ
How many instances can I run? Up to 5 active instances per account. Where does my instance run? Instances run inus-west-2 by default. Accounts subject to EU data-protection rules are placed in eu-central-1. The region is shown on the instance details page.
What happens to my data when I stop an instance?
Nothing is lost — state is captured in a snapshot and restored when you start it again. Only the public IP changes.
Can DeepInfra access my instance?
DeepInfra retains administrative SSH access for automated maintenance (updates and backup restores for example).
Why was my instance paused?
Most likely it exceeded the fair-use network transfer threshold for its plan. Start it again from the dashboard once usage normalizes.
What happens if my account is suspended?
If your account is suspended — for example when your balance runs out — your instances are automatically stopped within a minute or two, and creating, starting, or restoring instances is blocked. Nothing is deleted: state is preserved the same way as a regular stop, and once your account is back in good standing you can start your instances again. Keep in mind that a running agent spends on inference on its own, so consider enabling Automatic Top-Up if you plan to leave it unattended.
Where do I see what my agent is costing me?
On the Usage page — compute appears as Hosted Agent, and the agent’s model calls appear as regular inference usage.