Production-Ready by Demo Day — RAD for Startup Hubs

TechEquity RAD · For Startup Hubs, Accelerators & Incubators

Production-
Ready
by Demo Day.

Give every company in your portfolio the infrastructure
an engineering team of ten would have built.

Your founders are not short of ideas. They are short of runway, and a startling amount of it goes on infrastructure that no investor will ever ask about — a database, an ingress, a deployment pipeline, an authentication service. RAD deploys all of it into the founder's own Google Cloud project in minutes, so the weeks go to the product instead.

350+ Modules 60+ Ready Stacks Founder Owns Everything $30 Free per Founder

350+

Deployable modules

60+

Composed solutions

~20min

Typical build time

Geographies served

Runway spent on undifferentiated infrastructure is runway spent on nothing.

The Portfolio Problem

Every Company in Your Cohort
Is Solving the Same Problem. Separately.

A hub sees the pattern that no individual founder can: twelve companies in a cohort, each spending its first month building the same infrastructure, each convinced its version is somehow specific to them, and each arriving at demo day with less product than it should have.

Weeks

Typical early-stage time
spent on undifferentiated infra

12×

The same work repeated
across a single cohort

Technical mentor
answering all of it

For the founder

Runway spent proving nothing. An investor evaluates traction and product. Nobody has ever raised a round on the quality of their Terraform, but plenty of teams have run short of time because of it.

For the mentor

The same conversation, twelve times. Technical mentoring capacity is the scarcest thing a hub has, and it is consumed by questions whose answers are identical across the portfolio.

For the hub

Support that does not scale. Adding companies adds technical support demand linearly, so programme growth is capped by the engineering help you can staff.

For the programme

Cohorts that are hard to compare. When every company builds a different foundation, technical progress across the portfolio cannot be meaningfully assessed — or helped.

      Cloud credits do not solve this. Credits reduce the bill, not the work. A
      founder with $100,000 of cloud credit still spends the same three weeks writing the same
      Terraform — the constraint that actually binds an early-stage team is engineering time, and
      credits buy none of it.
    

What a Founder Gets on Day One

A Stack They Own,
Not a Platform They Are Stuck On.

This is the distinction that matters to an investor doing technical diligence eighteen months later. RAD deploys standard Terraform into the founder's own Google Cloud project. There is no proprietary runtime, no proxy in the request path, and nothing to unwind at Series A.

Day 1

300 free credits — $30 of deployments, no payment method required.

Day 1

Deploy the foundation

Database, auth, storage and ingress, into their own project.

Week 1

Ship the product

The differentiated part — which is the only part investors will ask about.

Series A

Hand it over

A real engineering team inherits plain Terraform, not a platform migration.

Why this survives diligence

Their Google Cloud account, their billing. Cloud spend goes directly to Google under the founder's own agreement — including any credits the hub or Google has already granted them.
Terraform state in their own storage. The infrastructure is describable, reviewable and modifiable without RAD.
Nothing breaks if they stop using RAD. A deployment keeps running exactly as it is. There is no runtime dependency to discover later.
No account required to start. A founder without a Google Cloud account yet can deploy into a RAD-managed project with a spending cap, and move to their own account when they have one.

Whole stacks, not single components

74 pre-composed solutions deploy several modules as one dependency-ordered unit, wiring each service to the ones it depends on automatically. A founder gets a working system, not a set of parts and an integration problem.

Bundle discounts

3–4 modules 15% · 5–6 modules 20% · 7 or more 25%. Deploying a whole stack costs less per component than assembling it piece by piece.

What an early-stage company actually needs, already in the catalogue

PostgreSQL Redis Keycloak — auth Elasticsearch Gitea — source & CI Matomo — analytics n8n — automation Directus — headless CMS Ghost — marketing site Ollama + OpenWebUI LiteLLM — model gateway RAGFlow Zammad — support desk Documenso — e-signing Plane — issue tracking Appsmith — internal tools + 166 more

      The AI stack is first-class, not an afterthought. Self-hosted model serving,
      a model gateway, a chat interface and retrieval-augmented generation are all composable
      solutions — so a portfolio company can run its own inference rather than building its unit
      economics on someone else's per-token pricing.
    

What the Hub Gets

A Technical Capability
You Can Offer Every Cohort.

For the hub itself, RAD is a programme asset: a standard technical foundation you provide on day one, mentoring capacity returned to the questions that are actually specific to a company, and a portfolio whose engineering baseline you can see.

Standardise

One foundation across the cohort

Programme asset

Every company starts from the same reviewed catalogue
Mentors advise on architecture, not on Terraform syntax
Technical progress becomes comparable across companies

Support demand stops scaling linearly with cohort size.

Provision

Cohort-wide environments

One action

Provision environments for up to 30 participants from a roster
Each founder owns their own deployment and project
Visibility for the programme lead, isolation between companies

Bootcamps and technical workshops become an afternoon, not a project.

Differentiate

A reason to choose your programme

Recruitment

A concrete technical benefit, alongside capital and mentoring
Founders ship visible product earlier in the programme
Demo day shows working systems rather than prototypes

Something specific to say when a founder asks what you provide.

Built for hubs outside the usual map

Payment access, not just product access

Stripe and Flutterwave are both supported, so founders can pay by card or mobile money. In markets where card penetration is low, the barrier to using a developer platform is usually the checkout, not the technology.

Deploy where your founders are

Eight geographies, including africa-south1 — the only African Google Cloud region — plus the Middle East, South America and Australia. Latency and data residency are a menu choice rather than a compromise.

      This is not a localisation afterthought. A hub in Lagos, Nairobi, Cairo or
      São Paulo faces the same infrastructure problem as one in London, with two extra
      constraints — payment rails and region availability. Both are addressed in the product rather
      than worked around.
    

Partnership & Commercials

A Partnership That Pays
the Hub, Not Just the Platform.

A hub introducing its portfolio to RAD is doing real distribution work, and is compensated for it. There is no fee to become a partner, no exclusivity, and no minimum portfolio size.

Referral partnership

15% commission on the accounts you introduce, for as long as they deploy
Portfolio companies that graduate stay attributed to the hub
No agreement to negotiate before you can start

Module partnership

25% revenue share on modules published by your hub or its companies
A portfolio company's infrastructure pattern becomes a product
You keep the repository; RAD handles catalogue, billing and delivery

Plan	Per month	Credits	Effective rate	Saving	Typical fit
Free	$0	300 + 100/mo	—	—	Every founder, from signup
Starter	$20	210	$0.0952	4.8%	Pre-seed, one product
Pro	$75	825	$0.0909	9.1%	Building toward launch
Business	$250	2,875	$0.0870	13.0%	Post-seed, multiple environments
Scale	$600	7,500	$0.0800	20.0%	Hub buying centrally for a cohort

Ten credits to the dollar. Purchased credits do not expire; awarded credits refresh monthly.

How a hub partnership usually starts

Step 01

One workshop

A session with your current cohort, deploying something real.

Step 02

Partner enablement

Referral attribution set up; your mentors briefed on the catalogue.

Step 03

Part of onboarding

RAD becomes a standard day-one benefit for every incoming company.

Step 04

Publish your patterns

Your own modules in the catalogue, earning a share of what they generate.

Run a cohort workshop

We deliver a hands-on session with your current cohort at no cost to the hub.

sales@techequity.cloud →

Become a partner

15% on referrals, 25% on published modules. No fee, no exclusivity, no minimum.

Discuss partnership →

Send one founder

The fastest evaluation is one of your companies deploying their real stack this week.

radmodules.dev →