One database per workspace
Support software where tenant isolation is structural, not a WHERE clause.
Every Quackback workspace gets its own dedicated database and its own isolated Worker. Cross-tenant access is not prevented by a check that somebody could forget — it is absent from the address space.
A database per tenant
A workspace's Worker holds exactly one database binding. It cannot name another tenant's, so there is nothing to leak.
Provisioning you can watch
Creating a workspace starts a recorded, resumable run. Every step is inspectable, and a failed step can be retried on its own.
Built for all-day use
Dense, quiet, keyboard-first, and correct in both light and dark. Colour is reserved for things that actually need attention.