Secure client-operations panel for a web studio
An internal tool that keeps every client’s hosting details encrypted at rest and tracks every change request from intake through testing to delivery.
- Industry
- Web studio operations
- Role
- Designer and developer
- Engagement
- Own product
- Year
- 2026
Client details are withheld under confidentiality.
By the numbers
- AES-256-GCM
- encryption at rest
- 9
- request states
01 — The challenge
The challenge
Running several client websites at once meant scattered credentials and change requests that slipped between “done” and “delivered”. The data was sensitive, so the tool had to be secure by default, not as an afterthought.
02 — The solution
The solution
A dashboard of the numbers that matter — urgent requests, work overdue by seven days or more, completed but not delivered — plus a cross-client queue sorted by priority and age. Each request follows a nine-state workflow with test results and delivery notes. Credentials are encrypted with AES-256-GCM, masked in the interface, and revealed only to admins, with every reveal written to an audit log.
03 — Architecture
Architecture
Next.js App Router with server actions, Prisma, cookie sessions and zod validation. Role guards run on the server, failed logins trigger a lockout, destructive deletes require typing the exact name, and strict security headers (CSP, HSTS, frame denial) are set for every response.
04 — Key features
Key features
-
Encrypted credentials with audited reveal
AES-256-GCM at rest, admin-only reveal, every view logged.
-
Cross-client work queue
Every open request sorted by priority then age, with filters.
-
Request lifecycle
Nine states from new to delivered, with testing and delivery records.