Vaultly
A platform for teams to store, share and audit access to credentials such as API keys, passwords, SSH keys and environment files, organized into project vaults.
What I built
- InterfaceA Next.js and TypeScript app with the marketing site, sign-up and sign-in, and the screens for vaults, access requests, the audit log and settings.
- APIA Go API on Chi with RS256 JWT access tokens, refresh tokens rotated on every use, password reset and email verification.
- DataA PostgreSQL schema managed with migrations, queried through type-safe code generated by sqlc.
- InfraDocker images for the API, worker, web app and nginx, with GitHub Actions running linting, unit tests and integration tests.
The problem
Teams need to share sensitive credentials: API keys, passwords, SSH keys, environment files and database logins. Passing them around in chat, email or a spreadsheet is a security risk, and it leaves no record of who saw what. The existing tools are often too complex or too expensive for a small team.
What Vaultly is
Vaultly keeps a team's secrets in project vaults. Access is controlled by role, people can request access and be granted it for a limited time, and every interaction with a secret is written to an audit log. Secrets can also be shared with someone outside the team through a time-limited link.
How it is built
The system has three running parts: a Next.js web app, a Go API, and a Go worker for background jobs. PostgreSQL is the primary store and Redis backs the job queue.
- The browser talks to the Go API over HTTPS and to a WebSocket hub for live updates.
- The API reads and writes PostgreSQL, and puts background jobs on a Redis queue.
- The worker takes jobs off that queue. It shares one codebase with the API.
I write an architecture decision record for each significant choice, and there are 23 so far. They cover questions such as using sqlc instead of an ORM, signing tokens with RS256, encrypting secrets with AES-256-GCM, and making refresh token rotation atomic.
Where it stands
Vaultly is in active development and the repository is private.
- Working today: the authentication foundation in the API (sign-up, sign-in, token refresh with rotation, password reset, email verification), the web app's pages, the container setup and the CI pipeline.
- Designed, still being built: secret storage with encryption at rest, vault membership, the access request workflow, share links and real-time notifications.