The whole product, under Apache 2.0.
No feature held back. Read the code that touches your data, run it on your servers, change it.
- Audit what touches your data
- Every query, every prompt and every permission check is in the repository. Your security team can read it.
- No lock-in
- Your data stays in your warehouse and your definitions stay readable. If you stop using Northstar, nothing is trapped.
- Your infrastructure, your rules
- Run it in your network, choose which AI features are on, and restrict where the pipelines can call.
Quickstart
The full stack starts PostgreSQL, Redis, object storage, the platform and its workers.
You need
- Docker with Compose, on a host dedicated to Northstar
- A Prefect server or Prefect Cloud, for scheduled jobs
- An OpenAI API key, for the AI features
- 1
Get the code
bashgit clone https://github.com/nathan294/northstar.git cd northstar/deploy/docker - 2
Set secrets and public URLs
bashcp .env.example .env # edit .env: secrets, BETTER_AUTH_URL, PREFECT_API_URL, OPENAI_API_KEY - 3
Start the stack
bashdocker compose -f compose.full.yml up -d - 4
Open the app
Go to http://localhost:3000, or to the public URL you set in BETTER_AUTH_URL.
- On first start, the front migrates the database and creates the first super administrator from the SUPERADMIN_USER_* variables.
Ways to deploy
Docker Compose, full
Everything in one stack, with PostgreSQL, Redis and object storage included.
Docker Compose, external
Bring your own PostgreSQL, Redis and S3. Only the web app is published.
Coolify
Both stacks as single files, ready to paste. Only the web app gets a domain.
Helm
A chart for Kubernetes. Ingestions are not supported on Helm yet.
Contribute
Issues and pull requests are welcome on GitHub. Report vulnerabilities privately through a GitHub security advisory, never in a public issue.