Skip to content
Use case

Ship an internal platform without building plumbing

Replace the year of glue code.

Hand your team a production-grade platform on day one: object storage, queues, auth, observability — all self-hosted, all wired to the same contract.

The problem

Every internal platform team ends up building the same five services: an admin panel, a webhook inspector, a queue runner, a file browser, and a Redis dashboard. Six months in, nothing ships and engineers are burned out on infra.

Our answer

Adopt the suite — a set of polished services that covers the majority of platform plumbing. They share a startup contract, a WebSocket channel set, a queue/storage backend matrix, and an OpenAPI convention, so once you learn one you know the rest.

What you get

Outcomes

How it fits together

The pipeline

  1. 1

    Pick your first four

    Most teams start with Parachute (admin panel), Depot (object-store browser), Stash (Redis GUI), and Flytrap (webhook inspector). Deploy them on the same Kubernetes namespace.

  2. 2

    Wire shared auth

    Every service supports JWT or HMAC. Point them at your OAuth provider, or share a single HS256 secret for internal use.

  3. 3

    Expose one dashboard

    Link each service from a landing page. Users get per-service authentication with the same cookie, same colour, same shortcuts.

  4. 4

    Grow as needed

    Add Dockyard when you need a private registry. Add Slipstream when you start shipping packages. Each one slots into the same ops model.

The stack

Products in this pattern

The products that make the pattern work. Each is a Docker image; each slots into the same contract.

Who uses this

Related industries

Ready when you are

Ship the blocks. Focus on the product.

Docker-ready microservices you can deploy in an afternoon. Learn one, use them all.