Start free, no payment method

You do not need a card to deploy something real.

300 signup credits

Granted when you create an account. Enough to deploy several modules from the catalogue and see the whole path end to end.

100 monthly credits

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 payment required

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.

Plans

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.

Starter

$20 / month

210 credits a month — $0.0952 per credit, 4.8% below the base rate. Solo builders shipping their first cloud applications.

  • 210 credits each month
  • Unused subscription credits currently roll over
  • Every module and every solution
  • Your own project or a RAD-managed one
Choose Starter

Pro

$75 / month

825 credits a month — $0.0909 per credit, 9.1% below the base rate. Active developers shipping across several projects.

  • 825 credits each month
  • Unused subscription credits currently roll over
  • Every module and every solution
  • Your own project or a RAD-managed one
Choose Pro

Business

$250 / month

2,875 credits a month — $0.0870 per credit, 13.0% below the base rate. Teams running Cloud Run and GKE workloads.

  • 2,875 credits each month
  • Unused subscription credits currently roll over
  • Every module and every solution
  • Your own project or a RAD-managed one
Choose Business

Scale

$600 / month

7,500 credits a month — $0.0800 per credit, 20.0% below the base rate. The lowest per-credit price.

  • 7,500 credits each month
  • Unused subscription credits currently roll over
  • Every module and every solution
  • Your own project or a RAD-managed one
Choose Scale

Enterprise

Talk to us

There is no listed Enterprise price. Tell us the shape of what you need and we will quote it.

  • A technical evaluation run with our team
  • Publishing your own Terraform modules
  • Assisted deployment and evaluation support
  • A private mode for internal use only
Contact sales

Prices are in US dollars, billed monthly. Subscription credits are granted when a payment succeeds.

How a deployment is charged

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.

  • The module fee: 40 to 300 credits

    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.

  • Builds are included in the price

    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.

  • A failed deployment costs nothing, up to 10 a day

    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.

  • Two worked examples

    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.

  • In a managed project, one deploy is three

    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.

  • AI help is never charged in credits

    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.

RAD's deployment confirmation screen for Excalidraw CloudRun, listing the Google Cloud services the module will create, then a 38-credit cost: a 36-credit module fee (40 at list, less the 10% RAD-managed project discount) reserved on confirm, plus an estimated 2 credits of build time metered as the build finishes, and the resulting credit balance (captured before builds were included in the price)
The confirmation screen, before anything is provisioned. The module fee is reserved when you confirm and charged when the deployment succeeds. (This screenshot predates included builds, so it still shows a build-time line.)

Four credit balances

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.

Free awards

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.

Event credits

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.

Subscription credits

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.

Bought credits

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.

The credit history table in RAD, with separate Awards, Top-up and Subscription columns against each transaction, including lab escrow commitments, above the awards and purchases balances
Every transaction is itemised against the balance it moved, and each balance is tracked separately rather than as one pot.

Solutions cost less than the sum of their parts

A solution deploys several applications as one dependency-ordered unit, and the module fees are discounted by its size.

Bundle discount

  • 3 to 4 applications 15% off
  • 5 to 6 applications 20% off
  • 7 or more applications 25% off

How a solution is billed

  • Module fees per member, discounted
  • Build cost included
  • Reservation one sum, before build
  • Applications per solution two to eight

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.

RAD's solution confirmation screen for SSO Foundation: three modules across three waves bound for a new project created automatically, each with its services listed, then a cost breakdown of 2 and 3 credits for the project and shared services and 61, 61 and 88 credits for Keycloak, Passbolt and Infisical, totalling 213 credits, 199 reserved on confirm and 14 metered as each build finishes (captured before builds were included in the price)
Three modules listed at 75, 75 and 110 credits, with the RAD-managed project discount and the 15% bundle discount already taken off each fee. The project and shared services RAD adds are included. The balance you would be left with is shown before anything is provisioned.

If RAD creates the Google Cloud project

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 deploy form for Excalidraw CloudRun with its 45-credit estimate itemised, and the GCP Project on RAD option disabled with a note that 10 more purchased credits are required for a sandbox project, or that a project id of your own can be entered to use awarded credits (captured before builds were included in the price)
The floor is enforced in the form, not discovered at the end: the option stays disabled, the shortfall is named in credits, and bringing your own project remains open.

Paying for credits

Two payment providers, chosen so that where you are does not decide whether you can buy.

Stripe

  • Cards Yes
  • Subscriptions Yes
  • One-off credit purchases Yes

Flutterwave

  • Cards Yes
  • Bank transfer Yes
  • USSD Yes
  • Mobile money Yes

What RAD sees

  • Your card details Never
  • Checkout Provider-hosted
  • Credited Provider confirmed
RAD's Buy Credits form: Stripe and Flutterwave offered side by side, a payment currency set to NGN, and an amount of 100,000 NGN converting to 752 credits, about 75 USD, at 10 credits per USD
Both rails, and the amount priced in your own currency before you commit — here 100,000 NGN, converted at ten credits to the dollar.

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.

Assisted deployment, and the wrong fit

Two things worth saying out loud.

Try it before you pay anything

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.