Propel Developer Docs

The internal home for engineering guides, architecture decisions, and platform reference — private to Propel, and built to grow an LLM assistant over our own docs.

Shift-left as a service
Daily work
🧭 Decisions 🧩 Services ⬡ Patterns 🤝 Team Playbook
Async-first, public-first — decisions get written down Never a silent decline — move the meeting or feed it input Blocked > half a day? Escalate — it's professionalism, not failure all norms →
Explore the docs
Client Offerings →
The five ways we take on, build, and operate infrastructure for clients.
Customers →
Per-customer spaces: their services, decisions, and dependency map. One folder per customer.
Internal →
Propel's own space — internal services, ADRs, and the engineering operating model.
Pattern Library →
Reusable Propel IP with maturity and the tech-adoption matrix across spaces.
Architecture Decisions →
Why we made significant technical decisions — internal log; customer ADRs live in their spaces.
Observability & Logging →
How we monitor infrastructure and protect client logs — uptime, metrics, traces, PII, residency.
Client Offerings · find your path
flowchart TD
    Start([New engagement]) --> Q1{Do you have a cloud
team & accounts?}
    Q1 -->|Not yet| Incubate
    Q1 -->|Yes, with existing infra| Q2{Take it over,
or augment us?}
    Q1 -->|Yes, starting fresh| Q3{Run it after
we build?}
    Q2 -->|Operate it for me| Takeover
    Q2 -->|Augment my team| Embed
    Q3 -->|I'll run it| Launch
    Q3 -->|You run it| LaunchManage

    Launch["1 · Launch"]
    LaunchManage["2 · Launch & Manage"]
    Takeover["3 · Takeover"]
    Incubate["4 · Incubate"]
    Embed["5 · Embed / Co-Build"]

    click Launch href "scenarios/launch.html"
    click LaunchManage href "scenarios/launch-manage.html"
    click Takeover href "scenarios/takeover.html"
    click Incubate href "scenarios/incubate.html"
    click Embed href "scenarios/embed.html"

    style Launch fill:#EDEDFF,stroke:#3B54F7,stroke-width:2px
    style LaunchManage fill:#EDEDFF,stroke:#6247F5,stroke-width:2px
    style Takeover fill:#EDEDFF,stroke:#2E7DE0,stroke-width:2px
    style Incubate fill:#F3EDFF,stroke:#8A54E8,stroke-width:2px
    style Embed fill:#E4E4FF,stroke:#23233A,stroke-width:2px

Click any path in the diagram — or explore the five scenarios below.

1
Launch
We build a best-practice foundation in your accounts, then hand you the keys.
Accounts: YoursWe: BuildAfter: You run it
See how it works →
 2
Launch & Manage
We build it and run it for you, under an SLA, while your devs ship on top.
Accounts: YoursWe: Build + runAfter: Fully managed
See how it works →
 3
Takeover
Already on cloud? We take over operating it, then stabilise and improve.
Accounts: Yours (existing)We: OperateAfter: Managed
See how it works →
 4
Incubate
No cloud team yet? We host and run everything, then graduate it to you.
Accounts: Propel → YoursWe: Host + runAfter: Graduates to you
See how it works →
 5
Embed / Co-Build
We work alongside your team, in your stack, and leave your people stronger.
Accounts: YoursWe: Co-buildAfter: Your team owns it
See how it works →