A credit costs $0.080–$0.100: 10 credits = $1 on a one-off top-up, and less on a plan. A deployment costs its module fee, with build time included, and in a project RAD created the Google Cloud bill is recharged in credits on top. The first purchase offered is a $15 starter pack of 150 credits, which covers the 100-credit reserve a RAD-managed sandbox project must keep with 50 credits to spare for running (about three days for the lightest apps, less than a day for an app with a database), and your first successful deployment is free of its module fee, whatever the application module: once per account, for a module you deploy and pay for yourself (in a solution, one application's fee: the first to succeed; never a lab session or a client project). Project_GCP and Services_GCP deployed on their own are always charged (10 and 20 credits). Lab sessions and client projects are the exception: they are still charged for build time by the minute. You can work out what you will spend on this page.
You do not need a card to deploy something real.
Granted when you create an account. Enough to deploy several modules from the catalogue and see the whole path end to end.
Free credits refresh on the first of each month. They are assigned rather than accumulated, so an unspent free balance is replaced. From 1 December 2026 the monthly grant goes to accounts with a successful build (a deployment, an update or a deletion) or a purchase in the previous 30 days. A new account keeps its sign-up credits for at least 30 days.
No card, no trial clock, no automatic conversion to a paid plan. You add a payment method when you want more credits, not before.
What credits pay for. Credits pay RAD for the deployment itself. Deploy into your own Google Cloud project and Google bills you directly for the resources, at your own rates. Without a Google Cloud account, RAD can create and govern a project for you instead.
The plans differ in one thing: how many credits you get for your money. Every plan reaches the whole catalogue of 350+ deployment options and all 60+ solutions.
210 credits a month — $0.0952 per credit, 4.8% below the base rate. Solo builders shipping their first cloud applications.
825 credits a month — $0.0909 per credit, 9.1% below the base rate. Active developers shipping across several projects.
2,875 credits a month — $0.0870 per credit, 13.0% below the base rate. Teams running Cloud Run and GKE workloads.
7,500 credits a month — $0.0800 per credit, 20.0% below the base rate. The lowest per-credit price.
There is no listed Enterprise price. Tell us the shape of what you need and we will quote it.
Prices are in US dollars, billed monthly. Subscription credits are granted when a payment succeeds.
One charge for a deployment, its module fee, visible before you confirm with the arithmetic done — builds are included — and, in a project RAD created, the cloud bill on top.
Set per module according to how much infrastructure it stands up, from a single container service to a full GKE platform. A handful of reference options carry no module fee at all. It is 10% lower in a project RAD manages. It is charged when the deployment first succeeds, and an update never carries one.
A deployment pays its module fee and nothing for build time. Each deployment gets 5 free updates a calendar month (UTC), and each further update costs 2 credits; an update RAD makes itself is free. Deleting, purging and any build that fails are free, up to 10 failed builds a day (UTC). Without purchased credits, your builds share 120 free build minutes a day (UTC); once they are used, you can build again the next day, or as soon as you buy credits. You can't start a new build while 3 of yours are running, though a solution's own applications don't hold each other up, and deleting or purging is never limited. The project and shared services RAD sets up beneath an application are included; deployed on their own they cost 10 and 20 credits. Lab sessions and client projects are the exception: they are still charged for build time by the minute.
If a new deployment fails or is cancelled, nothing is charged, and a failed update or teardown is not charged either. Failed builds are free up to 10 a day (UTC): after that, further failed new deployments and updates are charged for build time by the minute if you hold purchased credits, and if you don't, you can build again the next day. Deleting and purging always stay allowed. Failures caused by RAD or Google, such as internal errors and automatic retries, never count, and nor do failed teardowns. Whether a failure carries the module fee is a setting our finance team controls; in the current release it does not.
A 40-credit module costs 40 credits, or $4, however long it takes to build. A 300-credit module costs 300 credits, or $30. Updating it five times in a month costs nothing; a sixth update that month costs 2 credits. Tearing it down later is free.
RAD first creates the project, then the shared services your applications use, then the application, and the confirmation prices that whole chain. The first two are included in the application's price. Excalidraw on Cloud Run quotes 36 credits for the whole chain: its 40-credit fee less the 10% managed-project discount. The confirmation also estimates what the project costs a month to run.
The Conversational Assistant, Build Solution with AI, Ask AI and suggested fixes for a failed build cost no credits. They share one daily allowance per account: up to 100 AI requests a day if you have bought credits (a top-up or a subscription payment) in the last 90 days, and 20 in any 24 hours otherwise. Partners, agents, trainers and RAD's own staff get the larger figure. Buying credits raises a free account's allowance.
Credits are not one pot. Where a credit came from decides when it expires, and RAD spends the soonest-to-expire first: awards, then event credits, then subscription, then bought credits.
Signup and monthly credits, plus 10 per referral once the person you referred, within 90 days of signing up, has a successful deployment or update of an application or buys credits (a bare project, a lab or a client project does not count), up to ten a month. They refresh on the first of the month and do not accumulate: an unspent balance is replaced. From 1 December 2026 the monthly credits go to accounts with a successful build (a deployment, an update or a deletion) or a purchase in the previous 30 days. A new account keeps its sign-up credits for at least 30 days.
Claimed with a code from a RAD partner event. They expire on the code's own date, and they do not pay for Google Cloud usage in a project RAD manages.
Granted when a plan payment succeeds, and unused credits currently roll over. A failed card does not sweep them: only a successful renewal could ever reset this balance.
Credits you purchase as a one-off never expire: no code path that resets a balance can name this one. Subscriptions buy credits cheaper, so top up when a plan runs out.
A solution deploys several applications as one dependency-ordered unit, and the module fees are discounted by its size.
The module fees are reserved as a single sum, and your balance is checked against the whole estimate before the first member starts building, so you cannot run out mid-deployment. In a project RAD manages, the 10% managed-project discount applies on top of the bundle discount. The confirmation screen itemises every member, applies the discounts and shows the resulting balance.
You can deploy into a project RAD creates and governs for you, in one of eight regions, instead of bringing your own. That arrangement has its own rules. A project you already own can instead be linked from the Linked Projects tab on the Credits page: RAD pays Google for it and debits your purchased credits hourly, at Google's list price plus RAD's margin and your VAT rate, while you keep the project, its data and full control. Finance approves each link, and a minimum purchased balance keeps it running.
A RAD-managed project is real Google Cloud infrastructure running on RAD's own billing account. You need a confirmed email address and a minimum balance of credits you have paid for; free and event credits do not count. The minimum depends on which project tier you choose. It is a balance you hold, not a charge, and creating the project adds no surcharge today.
Each tier carries a monthly Google Cloud budget that raises alerts as spend approaches and then exceeds it. Those alerts reach our administrators and finance team, not you, because the spend lands on our billing account. A Google Cloud budget sends notifications: it does not refuse an API call, and raising it does not permit more spend.
RAD pays Google for a managed project and recovers it from your balance: the project's real spend is read hourly from the billing export and converted to credits. The console's public price list shows, for each application, its module fee and what it typically costs to run per day in a managed project. Deploy into your own Google Cloud project instead and none of this applies — Google bills you directly, at your own rates.
The recharge reaches your credit ledger as a single combined row covering all your projects at once. The Project Transactions tab on the Credits page is the breakdown: one row per Google Cloud project, over a date range you choose, carrying the credits debited and the cloud cost behind them. Each row records the cost and the rate at the moment the debit ran, so the tab and the ledger always agree.
RAD is designed to disable billing on a managed project if your purchased credit balance falls below that tier minimum, or its Google Cloud usage goes unpaid, and to restore it once you top up. It checks on a fifteen-minute schedule and only ever reverses a suspension it applied itself.
You can hold one managed project in each tier at a time, so a lab project does not consume your own sandbox. All but a short, named list can be deployed into a managed project; those that cannot are named on the modules page.
Two payment providers, chosen so that where you are does not decide whether you can buy.
Checkout happens on the provider's own hosted page, so card details never reach RAD. Credits are granted server-side only once the provider confirms the payment, in a single transaction carrying an idempotency key. A duplicated webhook cannot grant the same credits twice.
Two things worth saying out loud.
We run a first deployment with your team and hand it over; we author a Terraform module for software you already run; or we compose a solution around a stack you describe. These are priced per engagement rather than listed. Help setting up a single catalogue module is the exception: request it from the module's card in the console, where it is listed at $50 for a Cloud Run module and $150 for GKE, unless the module sets its own price. Tell us what you need.
If you want one container running forever at the lowest monthly figure, a single-app host will beat this. RAD earns its fee when there is more than one thing to stand up, and when it has to be governed and reproducible.
There is one cloud here on purpose. Every module is Terraform, deployed into a Google Cloud project, with state in Cloud Storage. If your infrastructure lives somewhere else, this is not the product for you.
300 credits on signup, 100 more each month you are active, no payment method. Deploy something real into your own project and see what it actually costs you.