Clear pricing, no lock-in.Clear pricing, No lock-in.
MIGRATE$500one-timeExisting App
Migrate to dedicated infrastructure.
Connect an application built on a supported vibe coding platform and let Rethrow agents assess the current architecture, prepare the target environment, and orchestrate the migration to dedicated cloud infrastructure.
Create a new application or continue developing post-migration in Rethrow Studio. Prompt, preview, and publish against infrastructure you own through a familiar interface while Rethrow handles the deployments.
Connect an application built on a supported vibe coding platform and let Rethrow agents assess the current architecture, prepare the target environment, and orchestrate the migration to dedicated cloud infrastructure.
Straight answers about credits, cloud costs, plans, and ownership.Common pricing questions
How much does Rethrow Studio cost?
Starter is $100 per month with 2,000 credits. Pro is $200 per month with 5,000 credits. Power is $500 per month with 10,000 credits. Cloud infrastructure usage is metered separately and added to your monthly Studio bill.
What are credits?
A credit is a metered Studio usage unit based on the input and output tokens used by the agent and associated language models to write your application code. Credits cover building activity in Studio and are not tied to your cloud infrastructure usage.
Are cloud charges included?
No. Studio covers the builder interface and included credits. Your cloud infrastructure usage is metered separately and added to the same monthly bill as a distinct charge. For example, a customer with a $500 one-time migration, a $200 Pro plan, and $25 in AWS usage owes $725 in the first month, then $225 per month if AWS usage remains the same.
How do I monitor cloud infrastructure usage?
When you enable Studio, we surface your cloud infrastructure usage directly in Studio under the Monitoring tab. It shows a daily breakdown of your cloud spend, which is added to your monthly Studio subscription bill.
What influences my cloud usage?
Two things drive it: your architecture and your volume of usage. When we migrate your app, we default to a cost-efficient, secure, and scalable architecture built on serverless building blocks, so you generally only pay when real users start interacting with your app. If you change that architecture — for example, adding a firewall policy or requiring in-app inference for AI-powered features — your cloud bill naturally increases. Separately, as more users interact with your app, that means more reads, writes, file uploads, and traffic that your cloud provider bills for. Our recommendation: once you enable Studio, open the Monitoring tab for your app. We update usage daily, and you can set up alerts, budgets, and more to track cloud infrastructure costs.
Can I change Studio plans?
Yes. You can move between Starter, Pro, and Power as your needs change. Review the effective date and billing details shown in your account before confirming a plan change, or contact support for help.
What happens when I run out of credits?
Review your usage and available plan options in your account, or contact support to discuss your needs. Any additional usage options and charges should be confirmed before you proceed. Running out of Studio credits does not transfer ownership of your application.
What happens if I cancel Studio?
If you cancel Studio, we initiate an offboarding process to transfer your repository and cloud environment to a standalone account that you own, separate from our managed organization. You will need to attach a credit card to that account for ongoing cloud charges. Once the transfer is complete, you take full ownership and can connect your preferred integrated development environment (IDE) and tooling to continue building.