RAD is in beta. The platform, catalogue and documentation are built and running.
Select from a catalog of ready-made deployment options, and RAD provisions it into a Google Cloud project you control, or into a governed project it creates for you.
Automating deployments. Wiring credentials. Setting org policies. Connecting one application to the next so it starts. It is the same labour-intensive process on every project, and most organisations perform this task more than once. RAD automates and implements all of this in minutes.
Four steps.
Select from the catalogue: 350+ deployment options covering 190+ applications. Most ship in both a Cloud Run and a GKE variant, so the choice is an operating model rather than a different product.
Basic mode asks only for the mandatory variables, and a first deployment is always Basic. The full set opens on update, in a project you own, once your credit balance covers the update's cost.
RAD runs the provisioning job and streams the build logs into the console while it runs. If something fails, you read the same output an engineer would, as it happens.
The build publishes its outputs: addresses, endpoints and connection details. Change the configuration to update the deployment, or delete to tear it down.
The project and the resources are yours. The Terraform state is not: every deployment's backend points at RAD's own Cloud Storage bucket, in RAD's project rather than in yours, and there is no download in the product today.
RAD is not in the request path: resources in a project you own keep running whether or not you sign in again. A RAD-managed project runs on RAD's billing account, and RAD suspends its billing once your purchased balance goes negative. RAD is Google Cloud only, and the module contract is Terraform.
After the retention period, RAD deletes its record of a deployment and the state with it — but only for an account that has gone quiet, holds no purchased credits, and has already had a recorded warning email.
Buying credits, or simply signing in, exempts the account. The deletion removes RAD's bookkeeping and not your resources: they carry on running in your own project, untouched by anything RAD does or stops doing.
Most deployment tools install one thing. RAD's catalogue also carries 60+ pre-composed solutions across twelve categories.
Dolibarr, InvoiceNinja, Kimai, Docuseal, Nextcloud and Homepage deployed into one project. RAD reserves the deployment credits as a single sum, and the applications are provisioned in dependency order, three at a time.
Members without a dependency are queued for immediate deployment. A member that consumes another member's outputs waits for the output to be available.
RAD copies the producer's deployment outputs into the consumer's configuration before it builds it: e.g. Elasticsearch into RAGFlow and Zammad, Ollama and LiteLLM into OpenWebUI.
Teardown walks the deployment graph backwards, because a shared project has to outlive resources deployed within. Getting that ordering wrong turns a clean delete into a set of orphaned failures.
The same catalogue and the same engine serve both.
RAD is subject to your organisation's policies and cannot widen them. You keep every region Google offers, and the infrastructure it creates is standard Terraform. The state file is the exception: it lives in RAD's Cloud Storage, not in your project.
For anyone without a Google Cloud account, or unwilling to use theirs. The four tiers (sandbox, development, production and lab) each live in their own Google Cloud folder with their own policy set. Lab is for trainers and administrators; the other three are self-selectable.
In the sandbox and lab tiers: external IPs are denied, default networks suppressed, serial port access disabled, service-account key creation and upload blocked, public buckets prevented, public Cloud SQL IP addresses refused, resource locations restricted, and enabled services limited to an allowlist.
The development tier keeps the same credential-hygiene floors and relaxes three rules, each with a compensating control: an external IP requires OS Login and a Shielded VM, a public bucket requires uniform bucket-level access, and a public database IP is allowed only with the Cloud SQL Auth Proxy, because IP allowlisting is blocked outright.
The production tier carries development's resource ceilings, each raisable on request: 48 Compute Engine vCPU and 32 Cloud Run vCPU per region, 32 GB of Memorystore Redis per region, 1 TiB of BigQuery scan per day, and no GPUs or Vertex AI accelerators.
These ceilings apply to RAD-managed projects only; in your own project, your quotas are your own.
Every RAD-managed project also carries a monthly Google Cloud spend alert, which raises a notification as spend approaches and exceeds its figure. It notifies; it does not block an API call. Enforcement is a separate mechanism, described on the pricing page.
The eight regions are us-central1, europe-north2, northamerica-south1, me-west1, africa-south1, asia-east1, australia-southeast2 and southamerica-west1, one in each geography, each the cheapest available region there. africa-south1 is the only Google Cloud region on the African continent.
RAD is not the cheapest way to run one small application. It is for people who deploy the same shape of infrastructure repeatedly.
The same infrastructure authored independently by every squad, a security review that never converges, and no single answer to what is deployed, by whom, at what cost. One reviewed catalogue, deployed into projects you already govern, as ordinary Terraform.
Cloud credits reduce the bill, not the engineering effort. Deploy the estate you need as one unit instead of over twelve separate afternoons, into your own Google Cloud project, and hand a diligence reviewer ordinary Terraform rather than a proprietary abstraction.
Thirty real Google Cloud environments on Tuesday morning and none on Friday afternoon. A trainer provisions a cohort in one action into the lab tier: a governed project per participant, in its own Google Cloud folder, for trainers and administrators only.
Publish your own Terraform modules from your own repository into the same catalogue and deploy them to more clients through one consistent interface, or have your software deployed as you publish it, with no fork, no repackage and no licence change.
Cohort provisioning for trainers shipped in August 2026 and is early access.
Published pages you can read before you sign up for anything.
Each one walks a deployment end to end and finishes with something running, rather than a diagram.
One for each of the 345+ application options, plus 175+ shared foundation guides, listing the form's variables.
Aligned to the seven Google Cloud certification tracks: ACE, PCA, PCD, PCDE, PCNE, PDE and PSE.
300 credits when you sign up, and 100 credits each month after that, with no payment method required. Use free credits to deploy into your own Google Cloud project and pay Google directly for what runs there.
RAD takes payment through Stripe and Flutterwave (card, bank transfer, USSD and mobile money) and never handles your card details itself. Credits are granted only after the provider confirms the payment.
RAD is in beta. The platform, catalogue and documentation described here are built and running; features marked as early access are newer.