Pricing
Simple pricing, affordable plans
There are two pieces to Rift's pricing model. Your plan determines what you can work on and which features you have access to. When your agent uses our virtual machines, you pay for metered usage, which is billed by the second.
Your monthly cost will be a combination of your plan and your metered usage.
Plans
We've priced Rift so that people working on open source projects can use it without paying for a subscription. Today, the main benefit of a subscription is the ability to use Rift to work on private GitHub repos. In the future, monthly subscriptions will unlock additional features that are mostly useful in a professional context.
Basic
Any organization
No monthly fee
- VMs bill by the second, at the metered rates
- Connect Rift to public GitHub repos
Payment method still required; see metered usage.
See featuresPersonal plan
Your personal organization
$9 a month
alpha$5 a month during alpha period
- Use Rift with private repos owned by your personal GitHub account
To work on a private repository owned by a GitHub Organization, use a team plan.
See featuresTeam plan
A team organization
$49 per seat per month
alpha$28 per seat during alpha period
- Use Rift with private GitHub repos owned by GitHub organizations
Features
- Public reposavailable
Use Rift to work on public GitHub repositories. This is one way we hope to give back to the open source community.
- Basic
- Personal
- Team
- Private repos under your personal GitHub accountavailable
Use Rift to work on private GitHub repositories associated with your personal GitHub account.
- Basic
- —
- Personal
- Team
- —
- Private repos under a GitHub team organizationavailable
Use Rift to work on private GitHub repositories associated with a GitHub team organization.
- Basic
- —
- Personal
- —
- Team
- Use any agentavailable
Start and stop VMs from any agent, harness, or model, as long as it speaks MCP.
- Basic
- Personal
- Team
- Work in parallelavailable
Run multiple VMs at the same time. Chase dozens of bugs at once.
- Basic
- Personal
- Team
- Isolated workstreamsavailable
Give your agents the ability to isolate workstreams, so they can stop stepping on each others' toes.
- Basic
- Personal
- Team
- Custom agent dev environmentsavailable
Give your agents the right tools for the job. VMs boot with any binaries you want. Describe development dependencies in git, so your agents always have what they need at their fingertips.
- Basic
- Personal
- Team
- VM audit logscoming
A record of every command your agents run on each VM. Retention varies by subscription.
- Basic
- —
- Personal
- Team
- Port forwardingcoming
Open a port on a VM from your machine, to see a dev server or attach a debugger.
- Basic
- —
- Personal
- Team
- Task-wide machine networkscoming
VMs in the same task share a private network.
- Basic
- —
- Personal
- Team
- SSO (OIDC)coming
Members sign in through your identity provider, at no extra charge.
- Basic
- —
- Personal
- —
- Team
| Feature | Status | Basic | Personal | Team |
|---|---|---|---|---|
| Public reposUse Rift to work on public GitHub repositories. This is one way we hope to give back to the open source community. | available | |||
| Private repos under your personal GitHub accountUse Rift to work on private GitHub repositories associated with your personal GitHub account. | available | — | — | |
| Private repos under a GitHub team organizationUse Rift to work on private GitHub repositories associated with a GitHub team organization. | available | — | — | |
| Use any agentStart and stop VMs from any agent, harness, or model, as long as it speaks MCP. | available | |||
| Work in parallelRun multiple VMs at the same time. Chase dozens of bugs at once. | available | |||
| Isolated workstreamsGive your agents the ability to isolate workstreams, so they can stop stepping on each others' toes. | available | |||
| Custom agent dev environmentsGive your agents the right tools for the job. VMs boot with any binaries you want. Describe development dependencies in git, so your agents always have what they need at their fingertips. | available | |||
| VM audit logsA record of every command your agents run on each VM. Retention varies by subscription. | coming | — | ||
| Port forwardingOpen a port on a VM from your machine, to see a dev server or attach a debugger. | coming | — | ||
| Task-wide machine networksVMs in the same task share a private network. | coming | — | ||
| SSO (OIDC)Members sign in through your identity provider, at no extra charge. | coming | — | — |
Metered usage
Every VM is billed by the second, at the same rates on every plan, whether or not you have a subscription.
| VM state · an hour | Small2 vCPU · 4 GB · 10 GB | Additional machine sizescoming soon |
|---|---|---|
| Running | $0.14 | — |
| Suspended | $0.004 | — |
| Stopped | $0.002 | — |
| Destroyed | $0 | — |
Additional machine sizescoming soon
What each state means
- Running
- When a VM is in a running state, your agent can run commands on it.
- Suspended
- Your agent suspends a VM when it won't need it for a little while, such as when it's waiting on you. Suspended VMs typically resume in a couple of seconds.
- Stopped
- Your agent may stop a VM when it won't need it for a while. A stopped VM keeps its disk but not its running processes. Stopped VMs are cheaper, but take longer to resume.
- Destroyed
- Your agent destroys a VM when its work is done, and closing a task destroys all of its VMs. A destroyed VM and its disk are gone, and cost nothing.
- We count to the millisecond and round only the total, to the cent. We start counting a VM's usage as soon as your agent starts it.
- For scale: 8 hours running a Small VM is $1.12; one suspended for a month is $2.92. A warm pool keeps up to 3 VMs ready for a branch you watch. Each waits suspended, about $2.92 a month for a Small VM, and runs while it rebuilds after each push. A rebuild takes about 2 minutes (p90 about 2.5 minutes), longer for a bigger image, so a push costs about 0.5 cents a VM, or 1.4 cents for a full pool of 3.
Changing your plan
Billing periods run from the 1st of each month.
- Adding a plan or a seat starts the plan immediately. We charge for the rest of the period.
- Removing a plan will cancel it at the end of the billing period.
- Moving up to a higher plan credits any unused time from your current plan toward the new plan.
If a plan lapses
If you cancel your plan, it will lapse at the end of its billing period. Three days after a missed payment, we will downgrade your organization to Basic, which has no monthly fee and bills usage by the second. If usage charges are unpaid, we will suspend VMs. They will be deleted after 14 days.
Questions
When do you charge for usage?
We charge for usage monthly, or more frequently when a payment method is new.
Does canceling a plan close my account?
No. Your account stays open, and you pay only for usage.
Where can I learn more?
Our Terms of Service and Cancellation policy explain our pricing model in more detail.