FA©26

Case study — 2026

Sluice

Role
Founder build · Design · Engineering
Status
Pre-release
In one line
Secrets for running processes. The server never holds plaintext.

Sluice delivers environment variables to running processes without the server ever holding a plaintext secret, and stops those processes the moment a service token is revoked by a signature from a customer-held key.

01 — The problem

Most teams keep production secrets in a dashboard: a hosted settings page or vault that, in the usual setup, can read every value it stores. Anyone who compromises that service, or the people who run it, can read them too.

Revoking access is the other half of the problem. A leaked token usually means rotating keys by hand and hoping every running process picks up the change. Sluice starts from the opposite end: store and route secrets without being able to read them, and make a revoked token stop the processes that use it.

02 — What I built

  • Crypto core

    AES-256-GCM seal and unseal, an HKDF key split, token minting and parsing, signed handshakes and revocation keys.

  • Convex backend

    Orgs, projects, environments, versioned secrets, tokens, sessions and bundle subscriptions.

  • Encrypted admin dashboard

    Unlock gate, secret drawers, coverage view, token list, activity feed and a CLI setup guide, with encryption in the browser.

  • sluice run CLI

    Injects secrets into a child process and supervises it; published as @getsluice/cli with standalone binaries.

  • Workload SDK

    Decides whether a running workload installs, keeps or shuts down its secrets.

  • Release pipeline

    Tagged releases build standalone executables and update a Scoop bucket.

03 — How it runs

The flow — Secret sealed in the browser, then Sealed bundle stored, then sluice run starts the app, then Signed handshake, then Secrets injected, then Token revoked: process stops.
  1. Secret sealed in the browser
  2. Sealed bundle stored
  3. sluice run starts the app
  4. Signed handshake
  5. Secrets injected
  6. Token revoked: process stops

04 — Proof

  • Pre-release
  • Automated tests
  • CI on every push

Honest note

Pre-release. There has been no third-party cryptographic review yet, so treat it as unreviewed security software. Not built yet: token minting and revoking from the dashboard, recovery, teams and an audit-log reader.

05 — Stack

  • TypeScript
  • pnpm + Turborepo
  • Convex
  • React 19 + Vite
  • Next.js 16
  • Tailwind CSS 4
  • @noble/curves + @noble/hashes
  • Bun-compiled CLI
  • Vitest
  • GitHub Actions

Next project

Audio Splitting SaaS and API

Split audio by length or size, through an API, a web app or n8n.