Draft
Incubate
Early-stage and don't have a cloud team yet? We host and run everything for you now, and graduate it to your own accounts when you're ready.
Is this the right fit?
This is for you if:
- You need production-grade infrastructure but don't yet have cloud accounts or a platform team.
- You want to move fast now and take ownership later, cleanly.
- You'd rather not stand up an AWS organisation and hire for it before you have to.
Once you're ready to own it, this becomes Launch & Manage (we keep running it in your accounts) or Launch (full handover).
How it works
flowchart LR
subgraph P["Propel-hosted — for now"]
ACCT[Propel-managed accounts]
LIVE[Your infrastructure repo]
INFRA[Your workloads]
STATE[(State · logs · secrets)]
OBS[Full monitoring + ops]
end
LIVE --> INFRA --> STATE
STATE -.-> OBS
OBS -.we operate.-> INFRA
INFRA ==>|GRADUATION TRIGGER
funding · first compliance need · you hire a lead| GRAD{Graduate}
GRAD -->|move to your org, we keep running it| P2["→ Launch & Manage"]
GRAD -->|move to your org + full handover| P1["→ Launch"]
We host and operate everything in Propel-managed accounts while you're early. Crucially, we build it handover-ready from day one — client-agnostic and portable — so graduation is a move, not a rebuild.
Who owns what
| Area | Before graduation | After graduation |
|---|---|---|
| Account ownership | Propel | You |
| Building & operating | Propel | Propel or You |
| Billing | Propel (passed through) | You |
| Data & risk decisions | You | You |
| Everything else | Propel | Per your chosen next path |
The graduation plan (agreed up front)
Because your infrastructure starts in our accounts, we define graduation at signing:
- Trigger — the event that moves ownership (e.g. a funding round, your first compliance requirement, or hiring a platform lead).
- Target — which path it becomes (Launch & Manage or Launch).
- Mechanics — re-parent accounts into your organisation, move billing to you, and move state, logs, and secrets into your account.
How we handle each piece
- Accounts & landing zone — A full secure foundation, in Propel-managed accounts, built to be portable to you later.
- Access & operations — We run it end-to-end so you don't need a platform team yet.
- Infrastructure as code & deployments — Everything as code, in a repository that travels to you at graduation — no rework.
- Monitoring, logs & security — Full monitoring, on-call, security baseline, and backups, operated by us.
- Cost management — We manage spend and pass through billing with full transparency; billing moves to you at graduation.
- Data handling — This is the one path where your data sits on Propel-managed infrastructure before graduation. It's contractually scoped, time-bound, and covered by Propel's own security program and insurance.
What you get
- Production-grade infrastructure without building a cloud team first.
- Speed now, clean ownership later — no lock-in and no rebuild.
- A pre-agreed, low-drama path to owning it all when the time comes.
At the end
Graduation: your accounts, your billing, your data — moved cleanly on the trigger you chose, into whichever ongoing path suits you.