01
Node 22+ OAuth SQLite · Postgres · MySQL
Modest prerequisites
Node 22+, one database — SQLite by default with zero setup, or Postgres or MySQL — and a Google OAuth client. No exotic infrastructure.
Self-hosting
Our cloud, or your server. One price sheet.
Our cloud is simply an installation where we are the operator. Yours runs the same software, at the same price — with an offline option for the strictest environments.
Illustration of a terminal running the interactive setup command: it writes the environment, generates the encryption key, provisions local HTTPS, then offers the first-run choice between the install wizard and a demo agency.
The database stores only references to files; the files themselves live in storage the operator chooses, and a client can require its own dedicated bucket with a key the operator holds.
What it takes to run
Deployment runway01 → 02 → 03 → 04
02
$ npm run setup
One interactive setup command
It writes the environment, generates the encryption key, provisions local HTTPS, and hands you a first-run choice: brand your own agency in the install wizard, or seed a full demo agency.
03
SQLitePostgresMySQL
Three databases, first-class
SQLite, Postgres, and MySQL run the same schema and queries, exercised against all three in CI — pick the one your team already operates.
04
02:00 Verified
backup.sql + storage/
Backups that are boring
A dialect-aware dump command backs the database up on your schedule, and files live in storage you already know how to back up.
Ships today
The honest print
Self-hosting is not a reduced edition. The distinction is operational: what ships today, what is planned, and what requires a Network deployment.
The complete platform
Every pipeline, workspace surface, database adapter, and review gate is the same software hosted or self-hosted.
Single sign-on + audit export
Planned capabilities, stated plainly rather than presented as if they already ship.
Offline + air-gapped
Available for strict environments as a premium Network deployment.
Quick answers
All questions- Is self-hosting really the same price?
- Yes — the same rate card either way. Most vendors price self-hosting as an enterprise upsell; charging the same removes the argument about where the box lives.
- What do we give up by self-hosting?
- Operations become yours: updates, backups, and uptime. The software, the pipelines, and the price stay identical.
- Can we move between hosted and self-hosted later?
- It's the same software and schema in both places; your database exports with standard dumps, and your files already live in storage you chose.
- Which databases are supported?
- SQLite, PostgreSQL, and MySQL are first-class targets. The same schema and query suite is exercised against all three.
- Can it run fully offline?
- Yes, as a Network-tier deployment for strict environments. Model access, storage, updates, and operations then remain within the infrastructure you control.
01
02
03
04
05
Self-hosting
What it takes to run
01
One interactive setup command
02
Three databases, first-class
03
Backups that are boring
Self-hosting is not a reduced edition. The distinction is operational: what ships today, what is planned, and what requires a Network deployment.
Prove it on one client
Start free. Pay only for clients you serve.
The 30-day Studio trial runs the real thing — no card, and dormant clients never bill.
No AI keys. No card. Nothing reaches a client without review.