If you build software, RAD can make it deployable on Google Cloud in one form — as you publish it, with no fork and no licence change. If you deliver cloud work for clients, RAD can publish your own Terraform modules and deploy them through one interface with one audit trail.
Two different readers, two different offers. We have kept them apart rather than blurring them into one pitch.
Open-source or open-core, self-hosted, with a commercial edition or a support business behind it. Your problem is that the first hour of self-hosting is where prospective users give up. Read the vendor half →
A consultancy, an agency or a reseller, with your own Terraform you re-apply for every client. Your problem is that the delivery is repetitive and the trail of who deployed what is scattered. Read the delivery half →
Both halves sit on the same catalogue: 354 deployment options covering 190 applications and platform modules, counted 2026-08-17, deployed into a Google Cloud project the end customer owns.
Not at the top. At the point where somebody who already wants your software has to stand it up.
The visitor read the docs, liked the product and opened the deployment guide. What they hit next is a database, a reverse proxy, TLS, object storage and a service account — none of which is your product, all of which they must get right before they see it.
A one-line container demo answers "what does the UI look like". It does not answer "will this survive in our cloud, under our policies, with our data next to it" — which is the question that precedes a purchase.
The people who push through an eight-step manual install are the people most able to run it themselves for free. The ones who give up are disproportionately the ones who would have paid for support or a hosted plan.
Interest is global; checkout is not. A developer who can evaluate your software may still be unable to complete the payment step that turns them into a user, let alone a customer.
RAD is a deployment path, not a distribution deal. Nothing about your project changes.
No fork, no repackage, no licence change, no vendored copy of your code. RAD deploys the artefacts you already publish, and when you cut a release we update the module against it.
Authoring the module, keeping it working against Google Cloud's moving parts, and answering the deployment questions is our job rather than yours. Your maintainers keep maintaining your software.
It lands in a Google Cloud project they own, as plain Terraform, and it keeps running unchanged if they never sign in to RAD again. The Terraform state sits in RAD's own Cloud Storage rather than theirs, which we say plainly rather than let a user discover it. That matters for your positioning as much as ours: nobody is being locked into a middle layer in order to try your software.
The catalogue carries 62 pre-composed solutions, defining 291 member deployments drawn from 151 distinct applications, counted 2026-08-17. Software that appears inside a solution gets deployed by people who came for the bundle — a team installing a support desk or an analytics stack, who now run your project because it was part of the estate they asked for.
RAD takes payment through Stripe and Flutterwave, and Flutterwave supports card, bank transfer, USSD and mobile money. RAD-managed projects run in one region in each of eight geographies, including africa-south1, the only Google Cloud region on the African continent. If your evaluation funnel currently ends at a checkout page for part of the world, this is the part to look at.
Every catalogue entry has a configuration guide documenting the variables the deploy form asks about. The documentation site carries 523 of them — one for each of the 346 application options, plus 177 shared foundation guides — and a hands-on lab for each of those options that ends in a working deployment rather than a diagram. Counted 2026-08-17.
Four steps, each one earned by the previous one. Nothing here requires an exclusive, and you can stop at any rung.
We author a module for your software and it appears in the catalogue with a guided form, a shown credit cost, live build logs and outputs. You do nothing except tell us we may.
You review the module and confirm it reflects how you intend your software to be run. Defaults, versions and the variables we expose are agreed with you rather than guessed by us.
Your software becomes a member of one or more pre-composed solutions, deployed into the same project alongside the things it usually sits next to. Eight producer-and-consumer pairs in the catalogue are wired automatically from the producer's Terraform outputs, across eight of the 62 solutions; every other connection between members is made by hand after deployment, and a new pair can be defined when one is worth defining.
Joint material: the deployment lab, the configuration guide, and a route from your own documentation to a working installation. Agreed in writing, never assumed.
The offer is specific: we will build a reference deployment of your software and show it to you before you commit to anything.
You already have the Terraform. What you do not have is a way to run it for thirty clients without it becoming thirty slightly different things.
Your repository stays yours. RAD reads it, renders your variables as a guided form, and deploys it through the same engine that runs the rest of the catalogue — the same live build logs, the same outputs, the same update and teardown path.
A junior consultant deploys the pattern your principal engineer designed, without a local toolchain, a set of credentials on a laptop, or an undocumented step somebody remembers. Basic mode asks only the mandatory variables; Advanced exposes the full set for the engineer who wants it.
Who deployed what, into which project, when, and what it cost in credits. Money-bearing actions write audit records. When a client asks what you ran in their environment last March, the answer is a query rather than a memory.
Under their org policies, in any Google Cloud region, as ordinary Terraform they can read and inherit. When the engagement ends, they are not holding something only you can operate — which is usually easier to sell, not harder.
If your modules must be visible to your organisation only rather than to the whole catalogue, raise it with us before you publish. We would rather agree what is possible today than have you discover the shape of it afterwards.
The mechanism, in full. The rates are agreed with you in writing, and you will not find a projected earnings figure anywhere on this site.
Deployments of a partner-published module are charged in credits like any other deployment: a module fee of 40 to 300 credits depending on complexity — the nine options that carry no fee are RAD's own, not a partner's — always shown before the user confirms, plus a build cost metered from how long provisioning actually ran.
A share of what is charged against your modules is attributed to you and reported in the platform, and settled on the terms we agree. Because the module fee is set per module, the thing your share is calculated from is visible to you and to the customer before a single deployment happens.
If you send a client to RAD rather than deploying on their behalf, the relationship is attributed to you and tracked inside the platform against the same credit ledger that records what the client spends — not in a spreadsheet reconciled quarterly.
Referred customers keep their own account, their own project and their own credits. Nothing about the arrangement puts you between them and their infrastructure.
Percentages we have not confirmed with you, and earnings projections of any kind. RAD is pre-launch; a first-year revenue ladder on a partner page would be a number we invented, and you would be right to discount everything else on the page because of it.
Ask us for the current terms and we will send the actual ones, dated.
Worth reading before you invest an afternoon in this.
Modules are sourced from Git repositories, rendered as guided forms, deployed by the same engine, and charged through the same credit ledger. This is how the existing 354 deployment options already work — it is not a feature waiting to be written for you.
The platform and the catalogue are built and running. We are early, we have no customer logos to show you, and we are not going to manufacture any.
You would be the first. We are saying so because you would find out in the first call anyway, and because a partner page that implied otherwise would make every other claim on this site worth checking.
Google Cloud only — if your software's centre of gravity is elsewhere, this is the wrong shelf. Terraform is the contract, so a module has to be expressible as Terraform. Seven of the 354 catalogue options cannot be deployed into a RAD-managed project and need the customer to bring their own. And RAD is not the cheapest way to run one small application; the reader who wants that is not the reader we are useful to.
RAD is in beta. The platform, catalogue and documentation described here are built and running; features marked as early access are newer and we say so where that is true. Catalogue figures counted 2026-08-17.