Pricing & Billing

Remotehost has two costs: a plan's base price, and usage — allocated resource time for the sandboxes you run. Sandboxes are metered by the second while running; stopping one stops its billing immediately.

Sandbox profiles

New sandboxes should be created with a workload profile. auto is the default profile: it starts from the smallest viable shape and can grow from measured CPU, memory, disk, and runtime pressure. Named profiles make heavier intent explicit when you already know the workload shape.

Machine sizes

Machine sizes are the current coarse allocation tiers behind profile starts and legacy clients:

An hour of a large sandbox running counts as 2 machine-hours against your plan's included allowance or overage; an hour of small counts as 0.5. Profile-aware billing will keep the same second-level metering discipline and rate usage from the resources actually allocated to the sandbox. Newer usage events record allocated vCPU, memory, and disk directly; older events fall back to sandbox profile or legacy machine size.

Plans

Individual — $20/mo

7-day free trial, self-serve.

• 610 included standard machine-hours/mo
• 35 included concurrent sandboxes, scaling up to 1,200
• Up to 24-hour sandbox sessions
• Personal org controls
• Community support, with direct access to the team while you evaluate Remotehost for your org
• Overage: $0.64 per standard machine-hour past the included allowance, with profile rates metered by second

Individual is single-player: no team members, invitations, or shared-org billing. It's the plan for the person evaluating and advocating for Remotehost inside their team, not a scaled-down team plan — move to the Team plan below once you're ready to bring others on.

Team — $300/seat/mo (2-seat minimum, $600/mo floor)

7-day free trial, self-serve.

• 100 included machine-hours per seat
• Dedicated sandbox pool for production workloads
• Shared org billing, limits, and controls
• Audit logs for sandbox lifecycle events
• Custom base images and repository templates
• Up to 24-hour sandbox sessions
• Priority support
• Overage: $4.712 per standard machine-hour past the included allowance, with profile rates metered by second

Enterprise — Custom

Contact sales@remotehost.ai.

• Everything in Team
• SSO and SCIM
• Custom concurrency limits
• Dedicated regions and capacity planning
• Custom dedicated host pools
• Security review and procurement support

Managing billing

Subscribe, change plans, and view usage against your included allowance from the console's Billing page.

Checkout requires acknowledgement that sandbox usage is measured from allocated resource-time and may be billed after the included allowance. The same disclosure is sent to Stripe Checkout for the subscription.

Usage guardrails

Subscriptions have sandbox usage guardrails:

• sandboxMachineHourLimit is the hard cap for the current billing period.
• sandboxOverageEnabled controls whether usage may continue past the included allowance.
• When overage is disabled and no explicit cap is set, the effective cap is the plan's included machine-hour allowance.

The API checks this cap before creating or resuming sandboxes, and current usage includes both stopped interval events and still-running allocation intervals. The console surfaces warning states at 80%, 95%, and 100% of the effective cap.

Metronome prices usage by billing_profile, not legacy machine_size. agent-small, agent-standard, browser-heavy, repo-large, build-heavy, long-running, and custom-heavy each have explicit profile rates. auto maps to the billing profile that matches the actual allocation for that runtime interval.