Good questions, clear answers

Rethrow moves vibe-coded apps onto production cloud infrastructure you own, and lets you keep building them in the browser. Migrate an existing app, or start a new one in Rethrow Studio. Either way, your app runs in your own AWS, Google Cloud, or Azure account, and your code lives in your own GitHub repository.

Founders, startup teams, agencies, and enterprise innovation teams who like the speed of vibe coding but need an app they can run in production: their own cloud account, their own code, and no platform lock-in.

No. Getting started is a guided, one-time setup, and you build by describing changes in plain language. Rethrow picks a secure, cost-efficient architecture for you and explains each decision. If you want help, we offer a free guided walkthrough.

To migrate, connect your app’s GitHub repository and get a free assessment with a proposed architecture and cost estimate. Rethrow then rebuilds the app on that architecture in a new account in your cloud, verifies each part, and deploys it for your review. To build, open Studio, describe what you want, review it in a live preview, and publish. Every deployment goes through a plan you can review.

Almost anything you would build as a web app: SaaS products, customer portals, internal tools, marketplaces, dashboards, APIs, and apps with AI features. Rethrow defaults to a serverless architecture, and supports containers for workloads that need them.

Create a Rethrow account, then complete a one-time setup that takes about 10 to 15 minutes: add a card for Rethrow fees, connect your coding agent with your own API key, and connect your cloud account. After that, migrate an existing app or build a new one.

A cloud account with AWS, Google Cloud, or Azure (your provider will ask for its own payment method), an account and API key with a supported coding agent provider, and a card for Rethrow fees. To migrate an app, you also need its code in a GitHub repository.

During setup, you launch one Rethrow setup template in your cloud organization. It creates a dedicated area for Rethrow apps (on AWS, an organizational unit) with guardrail policies, and grants Rethrow narrowly scoped roles. Each app then gets its own account inside that area. You can see everything it creates, and deleting the setup stack removes Rethrow’s access.

Not at launch. Every app runs in a cloud account that you own, in your own cloud organization. That keeps ownership and billing simple: your provider bills you directly, and your app never needs to be transferred.

Yes. Book a free guided walkthrough during setup, or contact us at any time.

Any app whose source code you can put in a GitHub repository, including apps built with Lovable, Base44, Replit, Bolt, and similar tools. You connect the repository, and a free assessment checks the code and its dependencies before you commit to anything. Platform names describe compatibility, not endorsements.

Migration is $100 per app, one-time. The assessment is free. The $100 covers the target architecture, the migration itself, deployment to your cloud account, verification, and support through go-live. Migrated apps then continue in Rethrow Studio at $50 per app, per month.

Most supported apps migrate in hours, not the weeks a manual migration usually takes. The one-time account setup takes about 10 to 15 minutes. Apps with unusual dependencies may need extra review, and your assessment tells you the scope before you start.

No. Rethrow works on a copy of your repository and deploys to a new, separate cloud account. Your current app keeps running untouched. You review the migrated app before you switch your users over.

The app is yours: it runs in your cloud account and its code is in your GitHub repository. Migrated apps continue in Rethrow Studio at $50 per app, per month, where you keep shipping features with your coding agent. The code and the cloud account stay yours.

Rethrow Studio is a browser-based builder for apps that run in your own cloud. Describe a change, your coding agent makes it, you check it in a live preview, and you publish it to your cloud account. Start a new app or continue a migrated one.

No. You can create a new app directly in Studio. It starts as a working starter app in your own cloud account, and you build from there. Every app lives in Studio, whether you migrate it or start it there.

The building experience is familiar: prompt, preview, publish. The difference is underneath. Your app runs in a dedicated cloud account in your own AWS, Google Cloud, or Azure organization, the code is in your GitHub repository, you choose the coding agent, and every infrastructure change goes through a reviewable plan.

Yes. Open the migrated app in Studio and keep shipping features against the same cloud account. Nothing about how you build has to change because your infrastructure did.

Your app keeps running. It already lives in your cloud account and your GitHub repository, so there is nothing to transfer. Your cloud provider keeps billing you for usage as before, and you can keep developing with your own IDE and tools. If you also want to remove Rethrow’s access, delete the Rethrow setup stack in your cloud account.

Through Publish. Code-only changes deploy in minutes. Infrastructure changes run a Terraform plan first, and if the plan would delete or replace anything, Studio lists those resources and asks you to confirm before anything is applied. You can review a plan before publishing, and roll back to an earlier deployment at any time.

A coding agent is software that wraps an AI model so it can do multi-step work on a codebase. It manages repository context, file edits, shell commands, permissions, tool calls, session state, and MCP integrations, and runs the loop that lets it plan, act, check the result, and continue. Kiro, Claude Code, and Google Gemini are examples.

No. Models such as Claude, GPT, and Gemini do the reasoning and code generation. A coding agent wraps a model with context, tools, permissions, and state so it can work on a codebase. For example, Claude is a model family and Claude Code is a coding agent built around it; Gemini is a model family and Google Gemini, the coding agent, is powered by it.

Rethrow Studio supports Kiro, Claude Code, OpenAI Codex, Cursor, Factory Droid, and Google Gemini. Kiro is the default. Your workspace can set a preferred agent and limit which agents builders may use. More agents are on the way.

Models and agents change quickly, and teams have their own preferences. Rethrow is built for portability: use the agent that suits you, switch later if a better one appears, and Rethrow handles the infrastructure, deployment, and app lifecycle underneath.

Yes. Some coding agents are tied to one model provider, while others work with models from several. The coding agent controls how the model uses tools, files, terminals, permissions, and project context; the model provides the reasoning.

No. Rethrow runs the coding agent you choose. Rethrow provides the layer around it: migration, your dedicated cloud account, live previews, reviewed deployments, monitoring, and the rest of the app lifecycle.

No. Each app gets its own dedicated cloud account (an AWS account, Google Cloud project, or Azure subscription) inside your organization. Nothing is shared with other Rethrow customers. Dedicated means account-level isolation; the provider’s physical hardware is still shared as usual in the public cloud.

At launch, Rethrow supports AWS, Google Cloud (GCP), and Microsoft Azure. Oracle Cloud Infrastructure (OCI) is planned as a fast follow, depending on demand. Each app runs in a cloud account you own.

Yes. Your cloud provider bills you directly for what your app uses, on your own account. Rethrow never resells cloud usage or adds it to your Rethrow bill, and Rethrow’s access can’t change your billing or payment settings.

Studio shows each app’s cloud costs, read from your cloud account: month to date, a month-end forecast, last month, and breakdowns by service and by day. It also shows logs, health, and an architecture diagram. Because the account is yours, you can also set budgets and alerts in your cloud provider’s console.

Two things: your architecture and how much your app is used. Rethrow defaults to a serverless architecture, so an idle app costs very little and costs grow with real traffic. Adding always-on components, such as a container service, raises the baseline. AI features in your app are billed by your coding agent provider, not your cloud. More users means more requests, reads, writes, and storage. Check the costs view in Studio regularly, and set a budget with your cloud provider.

On AWS, the default is serverless: AWS Lambda and Amazon API Gateway for the backend, Amazon DynamoDB for data, Amazon S3 and Amazon CloudFront for files and the frontend, and Amazon Cognito for sign-in. Containers on AWS Fargate are available for work that serverless functions can’t do. Infrastructure is defined as code with Terraform, in your repository.

No. The agent has read-only access to your app’s cloud account, without access to secret values. Every cloud change is made in code and applied through Publish, so it is planned, reviewable, and recorded.

Only what the setup grants: scoped roles inside the Rethrow area of your organization, assumed with a unique external ID. Rethrow can’t change your billing or payment settings, close accounts, or touch accounts outside that area. Guardrail policies limit app accounts to approved services, and you can remove Rethrow’s access by deleting the setup stack.

Agent API keys are stored encrypted in a managed secrets store and are never shown again after you add them. Your app’s secrets are stored in its own cloud account; Studio can set them but never displays them. Secret values never appear in logs, previews, or deployment records.

Everything that makes up your app. The source code is in your GitHub repository. The cloud resources run in an account inside your own cloud organization, billed to you by your provider. Rethrow works through narrowly scoped roles that you grant during setup and can remove at any time.

One flat plan: $50 per app, per month, with every feature included and no tiers. You bring your own coding agent (Kiro, Claude Code, OpenAI Codex, Cursor, Factory Droid, or Google Gemini), and that provider bills you for model usage, including any AI features in your app. Your cloud provider bills you for cloud usage. Every app in a workspace bills to one card on file, and teammates can join the same workspace.

Kiro, Claude Code, OpenAI Codex, Cursor, Factory Droid, or Google Gemini. Kiro is the default. Each builder adds their own provider API key, so the agent runs on your credentials and the provider bills you directly. The $50 per-app fee covers Studio itself: the builder, live previews, publishing to your cloud, specs and guardrails, permissions, monitoring, and support.

Your coding agent’s model usage (the input and output tokens it uses while working on your code) is metered and billed by your agent provider on your own account. Rethrow doesn’t sell or bundle model credits. If your app has AI features, its model calls use the same provider key, so that usage is billed by your agent provider too. The flat $50 per-app fee covers the platform, and your cloud provider bills cloud usage separately.

Each app in Studio is $50 per month. A workspace has one card on file and all its apps are on one monthly bill, so three apps cost $150 per month. The bill is charged on the 1st, and an app’s first month is prorated from the day it goes live: an app that goes live on November 3 is charged $46.67 for November 3 to December 1, then $50 on the 1st. Model usage is billed by each builder’s agent provider, and cloud usage by your cloud provider.

There are no tiers to change. Add an app to Studio, or remove one, at any time, and your monthly bill changes by $50 for that app. Your other apps and their cloud accounts are unaffected. Contact support if you’d like help.

Usage limits and overages are set by your agent provider’s account, not by Rethrow. The Studio plan has no model-usage cap of its own. Hitting a provider limit pauses the agent; it doesn’t affect your app, your code, or your cloud account.

No. Your cloud provider bills you directly. For example, migrating one app and keeping it in Studio costs $150 from Rethrow in the first month ($100 migration plus $50 Studio), then $50 per month. Your cloud provider bills its usage separately, and the amount depends on your app’s architecture and traffic.

Your coding agent provider. When your app calls an AI model, it uses your coding agent’s API key, so that usage shows up on your agent provider’s bill at their API rates, next to your agent subscription. Rethrow doesn’t resell or mark up model usage.

Rethrow uses Stripe to store your card and process payments, so Rethrow never stores your card details. There are no plans to upgrade or downgrade: Studio is $50 per app, per month, and your workspace can hold as many apps as you like. When you delete an app, we stop charging you for it. Your full billing history is in your account settings.

Yes. Every app in Studio includes support, including support cases and monthly office hours. There is one plan, so every app gets the same support.

Yes. Every migration includes support for the assessment, the migration plan, deployment, and go-live.