PROJECT / DEVELOPER TOOL

Loftlancer

Web dashboard and pnpm/Turbo monorepo for storing and organizing environment variables across organizations, projects, and environments. Values are encrypted at rest, with an audit timeline and notifications.

Role

Solo · product engineering

Status

Open source · Live app

Year

2025–2026

Stack

Next.js · React · TypeScript · tRPC · Drizzle ORM · Better Auth · Turborepo

Loftlancer — Environment and secrets manager for organizations, projects, and environments.

At a glance

Role
Solo builder — monorepo, UI, encryption, auth
Duration
2025–2026
Team
Solo
Stack
Next.js · TypeScript · Turbo monorepo · Better Auth · PostgreSQL

01 — The problem

Environment variables and secrets scatter across repos, machines, and deploy targets — engineers need a single place to manage values per project and environment without exposing secrets in plain text.

02 — My contribution

Built the pnpm/Turbo monorepo and web dashboard: encrypted secret storage, per-environment views, audit timeline, notifications, and GitHub OAuth via Better Auth.

03 — The hard parts

  • Encryption at rest — AES-256-GCM with a dedicated crypto package so the web app never stores raw secrets in the database.
  • Monorepo boundaries — shared api, actions, auth, db, crypto, notifications, and env packages consumed by the apps.
  • Developer UX — tabs for dev / staging / production and masked values in the UI for day-to-day rotation workflows.

04 — Key features

  • Project-scoped variable groups and environment tabs
  • Encrypted values, audit timeline, and notifications
  • Better Auth + GitHub OAuth for the management surface
  • Org roles (Owner, Manager, Member) via a canonical actions layer

05 — Key decisions

  • Prioritized clarity for engineers over generic CRUD — the UI emphasizes per-environment context.
  • Stacked on Next.js, tRPC, Drizzle, and Vercel for a familiar full-stack shape with a small operational footprint.

06 — Result

Working open-source repository and live app that demonstrate secure configuration management — no claimed production team adoption.

07 — What I’d do next

Next steps for a team rollout would be rotation reminders and CI integrations that pull secrets without logging values.