RAD is in beta. The platform, catalogue and documentation are built and running.
Talent is distributed evenly; access to production infrastructure is not. RAD provisions a governed Google Cloud project and deploys into it — payable by card, bank transfer, USSD or mobile money, wherever you are.
RAD is not the cheapest way to run one small application. It is for those who deploy the same shape of infrastructure repeatedly. A single standalone application may cost around $129 a month in Google Cloud, while ten of those on one shared foundation might cost as little as $18 each.
The same infrastructure written by every team, a review that never converges, and no answer to what is deployed, by whom, or at what cost. We will deploy RAD privately into your organisation, your folder, your billing account, for people only.
Free credits reduce the bill, not the engineering effort. Deploy the estate you need as one unit instead of over multiple days or weeks as single applications, into your own Google Cloud project, or a RAD-managed project optimised for cost and security.
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 GitHub repository into the RAD module catalogue. Choose the public mode to share your application with all users, or to specific users. Deploy your application through the same consistent interface.
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.
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 delete into a set of orphaned failures.
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 application-layer guides that apply across them.
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.