Incident timeline

    Born from amonorepo headache.

    One developer’s fix. Now shared.

    Same repo. Two ways to deploy.

    The usual way

    • Database, then API, then web.
    • Copy env vars. Hope.
    • Wrong order? It won’t boot.

    The Prongo way

    services:
      database: { image: postgres:16 }
      api:
        build: ./apps/api
        depends_on: [database]
      web:
        build: ./apps/web
        depends_on: [api]

    One file. One deploy.

    “Deploying a monorepo shouldn’t feel like assembling furniture without the manual.”

    A real cluster. Run in the evenings.

    1

    developer

    EU

    servers

    0

    cost in beta

    Four rules. Every decision.

    The repo is the unit

    → No wiring services by hand.

    Developers only

    → A wrong click can’t break infrastructure.

    Small on purpose

    → Honest, and I fix what breaks.

    Fair by default

    → No surprise bills. A free tier stays.

    Got thoughts? Say hi.