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.

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

Two components for a deployment, both visible before you confirm, with the arithmetic done — 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 infrastructure and reference options carry no module fee at all. The figure is shown on the confirmation screen before you deploy.

  • The build cost: 60 credits an hour

    Metered from how long the build actually ran, at one credit per minute. Most modules build in well under half an hour, so the build cost is usually the smaller half of the total.

  • A failed build carries no module fee

    If provisioning does not succeed, you are not charged for the module. The build time is still metered, because it consumed build capacity, but you do not pay for infrastructure you did not get.

  • Two worked examples

    A 40-credit module that builds in 12 minutes costs 40 + 12 = 52 credits, or $5.20. A 300-credit module that builds in 28 minutes costs 328 credits, or $32.80. Updating or tearing down later runs another build, metered the same way.

RAD's deployment confirmation screen, listing the Google Cloud services the module will create, a 40-credit module fee, an estimated 13-credit build cost and the resulting credit balance
The confirmation screen, before anything is provisioned.

Three credit balances

Credits are not one pot. Where a credit came from decides when it expires, and RAD spends the soonest-to-expire first.

Free awards

Signup and monthly credits, plus anything granted through a referral. They refresh on the first of the month and do not accumulate: an unspent free balance is replaced, not topped up.

Subscription credits

Granted when a plan payment succeeds, and unused credits currently roll over into the next cycle. Nothing except a successful renewal changes this balance: a failed card does not sweep it.

Bought credits

Credits you purchase as a one-off have no expiry date, and no code path that resets a balance is able to name this one. Subscriptions are discounted. Use this option when you run out of subscription credits.

The credit history table in RAD, with separate Awards, Top-up and Subscription columns against each transaction
Every transaction is itemised against the balance it moved, and the three balances are 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 per member, metered
  • Reservation one sum, before build
  • Applications per solution three to eight

The whole cost is reserved as a single sum before the first member starts building, so you cannot run out mid-deployment. The confirmation screen itemises every member, applies the discount and shows the resulting balance.

RAD's solution confirmation screen for SSO Foundation: three modules across three waves with their services listed, then a credit cost breakdown of 100, 104 and 137 credits with a 15% bundle discount of minus 39, totalling 302
Three modules whose fees are 75, 75 and 110 credits, with the 3–4 member discount taking 39 off that sum. The per-module figures shown add each one's estimated build cost to its fee, which is why they read higher — and the balance you would be left with, 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 RAD deploy form with the managed-project option disabled, explaining that a sandbox project requires 100 purchased credits and that the balance is 81 credits short of the deployment's estimated 131-credit cost
The floor is enforced in the form, not discovered at the end: the option stays disabled, and the shortfall is named in credits.

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, an amount of 100,000 NGN converting to 734 credits 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, no payment method. Deploy something real into your own project and see what it actually costs you.