Good questions,
clear answers.

Rethrow helps builders migrate existing vibe-coded applications or build new ones on dedicated cloud infrastructure. You keep a familiar AI-assisted development experience, with your application running in an AWS account, GCP project, or Azure subscription that belongs to you.

Founders, startup teams, enterprise innovation teams, agencies, and other builders who value the speed of vibe coding but want greater ownership and control over their infrastructure.

No. Rethrow is designed to make migration and cloud-backed application development accessible without requiring you to become a cloud engineer. Guided workflows and support help you understand the decisions along the way.

Applications with exportable source code or connected repositories from platforms such as Lovable, Base44, Replit, Bolt, and similar products may be eligible. A free assessment checks your application and dependencies before migration. Source platform names describe compatibility, not endorsements.

Migration is $500 one-time per supported application. This includes assessment, a proposed architecture, guided migration, deployment, verification, and migration support. There is no required Rethrow subscription after migration.

Typical supported applications are designed to migrate within hours rather than the weeks often associated with manual migration projects. Complex applications or unusual dependencies may require additional review. Your assessment clarifies the scope before you proceed.

Migration takes place in a cloned repository and a separate target environment. Your current production application remains untouched during migration. You review the new deployment before moving traffic at cutover.

You own the resulting application environment. Continue building in Rethrow Studio, use another compatible development workflow, or work with your own team. A Studio subscription is not required to retain your application or infrastructure.

Rethrow Studio is Rethrow’s browser-based development interface. Describe changes in natural language, review a live application preview, and publish to dedicated cloud infrastructure. Start a new application or continue a migrated one.

No. You can start a brand new application directly in Rethrow Studio. Migration and Studio are two independent paths to dedicated cloud infrastructure. Studio works equally well for new applications and migrated ones.

Studio combines a familiar prompt, preview, and publish experience with an application environment running in a dedicated AWS account, GCP project, or Azure subscription. The distinction is the infrastructure underneath: it belongs to you, with visibility into where your application runs.

Yes. After migration, open your application in Rethrow Studio to keep developing features against your dedicated cloud environment. You do not need to change your way of building just because your infrastructure has changed.

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.

Your application environment uses a dedicated AWS account, GCP project, or Azure subscription rather than being combined with other Rethrow customers in a shared application account. Dedicated refers to account or project isolation, not an unconditional guarantee of dedicated physical servers.

AWS, Google Cloud (GCP), and Microsoft Azure are supported target environments. Choose an AWS account, GCP project, or Azure subscription for your application. Your assessment or project setup determines the appropriate services for your requirements.

Cloud infrastructure usage is metered separately from Studio credits, then added to your monthly Studio bill as its own line item. The amount varies based on the cloud resources your application consumes.

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.

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.

You own your application source code and applicable dedicated cloud resources in your AWS account, GCP project, or Azure subscription. Rethrow may need authorized operational access to deliver migration, publishing, or support. Your project setup defines that access, without changing the ownership principle.

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.

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.

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.

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.

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.

Power includes premium support, monthly office hours, and priority feature requests. Migration includes support for the assessment, deployment, and cutover process.

Yes. The guided migration process includes a support path for questions about your assessment, migration plan, deployment, and cutover.