⭐️⭐️⭐️ Open-source, self-hosted alternative to Linear and Plane. Project management and issue tracking where teams and AI agents work side by side to plan and ship products.
Deploy on Kubernetes (Helm)
The Helm chart in charts/itsaplan/ deploys the full stack on any Kubernetes 1.24+ cluster. It runs the published
images from GHCR, with built-in PostgreSQL and RustFS that can each be swapped for an external service.
Prerequisites
- Kubernetes 1.24+
- Helm 3.10+
Install
Create a values file for the deployment:
api:
env:
API_URL: "https://api.example.com"
APP_URL: "https://app.example.com"
S3_BUCKET: "planner-attachments"
secrets:
postgresPassword: "" # openssl rand -base64 32
betterAuthSecret: "" # openssl rand -base64 32
appEncryptionKey: "" # openssl rand -base64 32
s3AccessKeyId: "minioadmin"
s3SecretAccessKey: "minioadmin"
Install the chart:
helm install itsaplan charts/itsaplan -f values.yaml
Install from the OCI registry
Every release publishes the chart to GHCR, so a clone is optional. The chart version is the release
version, and appVersion inside it is the image tag it deploys:
helm install itsaplan oci://ghcr.io/croffasia/charts/itsaplan --version 1.9.0 -f values.yaml
helm show values oci://ghcr.io/croffasia/charts/itsaplan --version 1.9.0 prints the defaults to start a
values file from. Only released versions are published, so pin --version where the deployment has to
stay put: in the values file of a GitOps app spec, or in the install command.
For the Pro edition, pass charts/itsaplan/values-pro.yaml before it. Without a valid license
the Pro images run as the core does; the license key is entered in god mode, under License.
helm install itsaplan charts/itsaplan -f charts/itsaplan/values-pro.yaml -f values.yaml
Each API pod applies the database migrations in its migrate init container before the server starts. With several replicas, one applies them and the others wait on a Postgres advisory lock. Worker and bot pods wait in their own init container until the migrations are applied. The first account registered becomes the instance admin.
What gets deployed
| Resource | Kind | Condition |
|---|---|---|
| API (Elysia) | Deployment + Service | always |
| Web (Next.js) | Deployment + Service | always |
| Worker | Deployment | always |
| Bot (Telegram) | Deployment | bot.enabled (default true) |
| PostgreSQL | StatefulSet + Service + PVC | postgresql.enabled (default true) |
| RustFS | Deployment + Service + PVC | minio.enabled (default true) |
| RustFS bucket init | Job (Helm hook) | minio.enabled |
Ingress, TLS certificates, and a ServiceAccount are available but disabled by default.
Ingress
The chart routes the API in one of the two modes below. API_URL can also be a path on the web's host (see
Where the api lives), but then the proxy has to remove that path before the
request reaches the api. A standard Ingress has no portable way to do that, so the chart does not template this mode.
Separate host
The web and API each get their own hostname. Works with any ingress controller.
ingress:
enabled: true
className: nginx
host: app.example.com
tls:
enabled: true
secretName: app-tls
api:
mode: separate-host
host: api.example.com
tls:
enabled: true
secretName: api-tls
Traefik entrypoint
The API shares the web hostname but is served on a dedicated Traefik entrypoint (a separate port). Requires Traefik and
the IngressRoute CRD.
ingress:
enabled: true
className: traefik
host: app.example.com
tls:
enabled: true
secretName: app-tls
api:
mode: traefik-entrypoint
entryPoint: apisecure
publicPort: 8443
tls:
enabled: true
secretName: app-tls
TLS with cert-manager
certificate:
enabled: true
issuerName: letsencrypt-prod
issuerKind: ClusterIssuer
dnsNames:
- app.example.com
- api.example.com
The generated secret is named <release>-itsaplan-tls. Reference it in
ingress.tls.secretName and ingress.api.tls.secretName.
External database
Disable the built-in PostgreSQL and provide a connection string:
postgresql:
enabled: false
externalDatabase:
url: "postgres://user:[email protected]:5432/itsaplan"
External S3
Disable the built-in RustFS and point to an external S3-compatible store:
minio:
enabled: false
externalS3:
endpoint: "https://s3.us-east-1.amazonaws.com"
api:
env:
S3_BUCKET: "my-bucket"
S3_REGION: "us-east-1"
S3_FORCE_PATH_STYLE: "false"
secrets:
s3AccessKeyId: "AKIA..."
s3SecretAccessKey: "..."
S3_FORCE_PATH_STYLE is false for AWS and Cloudflare R2, true for RustFS.
Secrets in production
The chart creates a Kubernetes Secret with plaintext stringData. For production, store secrets externally (Sealed
Secrets, External Secrets Operator, SOPS, etc.) and inject them via a values override or a secret store CSI driver.
Upgrading
helm upgrade itsaplan charts/itsaplan -f values.yaml
Config and secret changes trigger a rolling restart automatically (the deployments carry a checksum annotation on the ConfigMap and Secret).
Disabling the Telegram bot
bot:
enabled: false
Values reference
The full list of values with defaults is in charts/itsaplan/README.md.
For Docker Compose, see self-hosting.md. For a managed deploy, see coolify.md or railway.md.