HelixDB / helix-foundry

Your company's data, connected into one ontology, on your own computer. 
Helix Foundry is a local-first data workspace built on HelixDB and DuckDB. Connect the tools your company already runs on, such as your database, Stripe, WorkOS, PostHog, files and APIs, and it suggests one connected ontology across them that you can explore and ask questions of. There are no accounts and nothing to host: it runs on your computer, and AI runs locally by default.
## Get started with your coding agent
You need Docker installed and running. The first run downloads several GB, so give it a few minutes.
Paste this prompt into Claude Code, Codex, Cursor or any coding agent that can run terminal commands:
 [code] 
Your agent will ask you to approve `git`, `docker` and network commands as it goes. Approve them one at a time rather than allowing every `docker` command up front; the runbook asks before anything that deletes data.
**What your agent will do**
- Check that Docker is running and that the app's port (3001 by default) is free, and pick another port if it is not.
- Generate local encryption keys in `.env` with `scripts/setup.sh`.
- Build and start the stack with Docker Compose, including a local AI model. On a Mac where Ollama is already running, it uses that instead.
- Wait for the health check to pass, then give you the URL.
**What you do next**
1. Open the URL (http://localhost:3001 by default). There is no account to create.
2. Guided setup takes you through **AI → Data → Ontology**. Choose Local, Claude, OpenAI, Azure OpenAI, Amazon Bedrock, or a custom OpenAI-compatible endpoint. Connect your data, or choose **Continue with sample data**. Then confirm the suggested ontology.
3. Home opens with your key metrics. Ask anything about your data from the box at the top.
You enter Claude or OpenAI keys and database credentials yourself, in the browser. Your agent never needs them.
## Manual quick start
You need Docker with Compose v2 (see requirements).
 [code] 
`setup.sh` writes fresh keys to `.env` if it does not exist yet, then builds and starts the app, a background worker, the DuckDB executor, HelixDB and Ollama. The first run builds the image and downloads HelixDB, Ollama and the `qwen3:4b` model (roughly 2.5 GB), so give it several minutes.
It is ready when the health check answers:
 [code] 
Then open **http://localhost:3001**. The model keeps downloading in the background, and you can start setup before it finishes.
**Port 3001 already in use?** Create `.env` first, then set the port and the matching origin together:
 [code] 
Add the two lines once; if `.env` already has them, change their values instead. Always change both. If only the port changes, pages load but every save fails with `403 Origin is not allowed`.
**Apple Silicon.** Docker cannot use Metal, so local AI is faster with native Ollama. Start Ollama, then run the stack without the bundled model:
 [code] 
This relies on Docker Desktop, which provides `host.docker.internal`. With another Do