Accounts and security
Email and password with verification, GitHub and Google, two-factor and passkeys, session management, rate limits.
Director
Build once. Serve anywhere — web, PWA, desktop, mobile, self-hosted.
What Director is
Section titled “What Director is”Director is a Bun-native SaaS starter — the Svelte/Bun answer to next-forge, Makerkit and ShipFast. Auth, organizations, teams, workspaces, billing, an admin surface and a document pipeline with metered AI jobs are built once and served as a website, a mobile site or installable PWA, a desktop app, a mobile app, or self-hosted on your own server.
It has one architectural rule: a single source of truth over HTTP. Every surface — the SvelteKit app, the Tauri desktop and mobile shells, the Astro sites, scripts and the Python service — is a thin client of one API (Hono + oRPC on Bun) with the same auth, the same procedures and the same OpenAPI document. Only the API talks to Postgres.
Organizations, teams, workspaces
The organization is the tenant and billing entity; workspaces are the product container. Roles are defined once and enforced in the API; every mutation is audited.
Billing and admin
Stripe with the organization as the customer and seats that follow members. A platform admin surface for users, tenants, feature flags and system health.
Documents and AI jobs
Presigned uploads with a per-workspace storage quota, a Postgres job queue that extracts, summarizes and indexes them, semantic search over pgvector, OCR for images, work metered in credits against the plan.
Anywhere
One SvelteKit codebase for Node, Cloudflare Workers or a static SPA; Tauri 2 shells with no IPC; Docker Compose with Caddy and Tailscale for your own box.
Where to go
Section titled “Where to go”QuickstartBun, Docker and a handful of commands to a running API and app.
ConfigurationEvery environment variable, what it switches on, and what happens when it is empty.
GuidesAuthentication, organizations, billing, admin, documents and jobs, the frontend platform, serve anywhere, operations.
API: RPC and RESTHow the typed client and the REST endpoints relate — every procedure, its errors and its paging, and where the OpenAPI document lives.
ArchitectureThe diagram, the repository map and the hard rules.
CommandsThe root scripts: dev, check, test, build, database, auth schema, admin bootstrap, demo data, rename and the licence audit.