Vaultwarden

# MISSION: Scaffold "Vaultwarden" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **Vaultwarden**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Vaultwarden
- **What It Does**: Lightweight, unofficial Bitwarden-compatible password manager server written in Rust with SQLite, PostgreSQL, and MySQL support.
- **Domain & Category**: Lightweight Self-Hosted Password Vault
- **Production Scale**: Solo / 2-5 people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Vaultwarden replaces the heavy, multi-container official Bitwarden stack with a single fast Rust executable consuming minimal RAM.
- **Live Website Reference**: https://github.com/dani-garcia/vaultwarden
- **Source Repository**: https://github.com/dani-garcia/vaultwarden
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Rust, SQLite, PostgreSQL, MySQL, Docker, Tokio
- **Primary Language(s)**: Rust, Handlebars, TypeScript, Shell, Jinja, HCL
- **License of the reference repo**: AGPL-3.0
- **Backend & APIs**: Rust — Core systems programming language providing memory safety and minimal resource usage; Tokio — Asynchronous runtime powering concurrent Rocket HTTP connections and WebSocket streams
- **Data & persistence**: SQLite — Default embedded database storage using bundled libsqlite3 for zero-config deployments; PostgreSQL — Relational database driver supported via Diesel for high-concurrency clustered setups; MySQL — Alternative relational database backend supported through compile-time Diesel feature gates
- **Infrastructure & deploy**: Docker — Multi-architecture Alpine and Debian container builds with embedded Web Vault static assets
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/dani-garcia/vaultwarden @ eb212e2)
1. **Single-Binary Bitwarden Server Implementation**: Rewrites the multi-service Bitwarden backend in pure Rust, reducing memory consumption from gigabytes to tens of megabytes on self-hosted servers.
2. **Pluggable Multi-Database Persistence via Diesel**: Uses compile-time feature flags in Diesel to generate native queries for SQLite, PostgreSQL, or MySQL without runtime ORM overhead.
3. **OpenDAL Object Storage Abstraction**: Integrates Apache OpenDAL (opendal) to support transparent file attachment storage across local disks and S3-compatible cloud buckets.
4. **Hardware Multi-Factor Authentication via WebAuthn-RS**: Implements FIDO2, WebAuthn, and YubiKey two-step verification using native Rust cryptography without external authentication brokers.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (SQLite, PostgreSQL, MySQL): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.