Self-host
Your workspace, on infrastructure you control.
The complete PlanGlade core stays public, provider-neutral, and usable without a hosted PlanGlade account.
Before you begin
Self-hosting is a technical setup.
PlanGlade is an early preview. Use unique secrets, terminate TLS, keep tested backups, and review the security guide before exposing it to the internet.
- 01
Clone and configure
Generate a local release configuration with unique secrets. Do not commit the resulting environment file.
- 02
Build and start
Use Docker Compose to build the frontend and backend, then start the single-origin application.
- 03
Create the first owner
Open the setup route, use the one-time setup token, and create the first workspace owner.
- 04
Protect and back up
Back up both the SQLite data and attachment volume, then rehearse a restore before relying on the installation.
Local release path
One origin, two runtime responsibilities.
The frontend serves the product interface. The API-only backend owns authentication, SQLite, migrations, and attachments.
git clone https://github.com/kalelooz/planglade
cd planglade
npm run setup:local
docker compose -f compose.yml config
docker compose -f compose.yml build
docker compose -f compose.yml up -dWhat stays yours
A public core without a provider lock.
The documented self-host path uses standard local components. Optional OAuth and email delivery do not replace the local baseline.
- Identity
- NextAuth with local email and password enabled by default.
- Data
- SQLite with checked-in migrations and documented upgrade procedures.
- Files
- Local attachment storage on a dedicated Docker volume.
- Recovery
- Backup, restore, and production migration guides live in the public repository.
Use the maintained guide
Read the current prerequisites and security notes before installing.
The repository documentation is the source of truth for setup commands, environment variables, upgrades, and backups.