Skip to content
Use case

Give ops and QA safe database access

Browsers, not credentials.

Truffle for SQL, Stash for Redis, Depot for object storage — browser-based access with action-level permissions.

The problem

QA needs to verify data. Support needs to check a customer’s queue. Ops needs to clean up a broken row. You’ve been handing out master credentials and hoping for the best.

Our answer

Truffle, Stash, and Depot each offer a per-environment web UI with per-user permissions. Download, rename, delete — each is independently toggleable. Signed URLs replace credential handoff.

What you get

Outcomes

How it fits together

The pipeline

  1. 1

    Deploy per environment

    Run one instance per dev/staging/prod with its own permission matrix.

  2. 2

    Wire up auth

    OAuth, LDAP, or internal OIDC. Roles map to the same permissions you already use.

  3. 3

    Give out the URL

    Non-engineers go to `stash.int.company.com` and see exactly what their role allows — nothing more.

  4. 4

    Audit what happens

    Every write is logged. Pair with Flytrap if you want a live tail of the activity.

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.