Helix Foundry Ontology and Knowledge Graph from Your Data
Deploys Helix Foundry 0.1, HelixDB's open-source app for turning company data into one graph with an ontology, cited answers and an MCP endpoint. Runs behind a password prompt and includes the Acme Corp sample. A community template, not affiliated with HelixDB.
What you get
- A Caddy gateway that asks for a generated password before anything reaches the app
- Foundry web app, API, MCP server and ontology agent, with HelixDB (graph database) and MySQL on volumes
- SeaweedFS as an S3-compatible store for synced tables, snapshots and documents
- An optional Postgres service with Acme Corp sample data, so 'Use the sample' works once an AI key is added
- Images pinned by tag and digest; secrets generated at deploy
Good for
- Building an ontology over PostgreSQL, MySQL, Stripe, GitHub, Notion or Slack data plus documents
- Asking questions across tables and documents with sources for each claim
- Giving Claude Code, Cursor or your own agents an MCP server over a company graph
- Trying ontology-driven analytics on made-up data before connecting real systems
Services in this template
- Site · from
baranberkay96/helix-foundry-railway - HelixDB · image
ghcr.io/helixdb/helixdb:v0.0.14@sha256:1470a3bce07866367f1d2a5b250ec9c3244d62356ac27d537023ef5492a8f62a - Acme DB · from
baranberkay96/helix-foundry-railway - Foundry · from
baranberkay96/helix-foundry-railway - MySQL · image
mysql:8.0.46@sha256:7dcddc01f13bab2f15cde676d44d01f61fc9f99fe7785e86196dfc07d358ae2b - Storage · from
baranberkay96/helix-foundry-railway - Gateway · from
baranberkay96/helix-foundry-railway
Questions people ask
How do I log in?
Open the Gateway URL and sign in with BASIC_AUTH_USERNAME (default admin) and BASIC_AUTH_PASSWORD, both under Gateway variables. Then pick an AI provider in Settings > AI models, or set ANTHROPIC_API_KEY or OPENAI_API_KEY on the Foundry service beforehand.
What drives the cost?
Seven services run: gateway, site, Foundry, HelixDB, storage, MySQL and the sample database. Foundry needs about 1 to 2 GB while drafting or loading, per the template notes, so Hobby or Pro is recommended. Synced data counts as egress because Foundry reaches the store through its public URL. Model calls are billed by your AI provider.
Is data kept across redeploys, and how do I upgrade?
Yes, Foundry, HelixDB, storage and MySQL use volumes. Keep FOUNDRY_CONNECTOR_KEY safe: without it stored connector credentials cannot be read. Images are pinned in service variables; upgrade the three Foundry images together, back up the volumes first, because migrations only go forward.
Is there a limit on scaling?
Keep every service at one replica, because workers, HelixDB and the store keep state in-process or on volumes. Scale vertically instead.
What licence applies?
Helix Foundry, HelixDB and SeaweedFS are Apache-2.0. MySQL is GPL-2.0 with the Universal FOSS Exception. The MCP and HTTP Ask routes skip the password prompt and need a bearer token; set FOUNDRY_AGENT_ENDPOINTS to off to keep them behind the password.
Full template README
Deploy and Host Helix Foundry with Railway
Helix Foundry is HelixDB's open-source (Apache-2.0) app for turning company data into one graph: connect databases, tools and documents, let an agent draft an ontology over them, load it into HelixDB, then explore it and ask questions with cited answers. This community template runs Foundry's 0.1 release images with a password-protected URL and the Acme Corp sample.
About Hosting Helix Foundry
Upstream ships Foundry as software for your own computer: no sign-in, one owner, seven containers sharing a network namespace, and a site that answers only localhost:3000. This template rebuilds that stack for Railway's private network. A gateway asks for a generated password before anything reaches the app and presents each request to it as localhost. Foundry and its ontology agent share one container and volume, as they share a pod upstream. HelixDB, MySQL and an S3-compatible store (SeaweedFS) run as their own services with volumes. Secrets are generated at deploy. The Acme Corp sample database is wired in, so "Use the sample" works once you add an AI key.
Common Use Cases
- Build an ontology over PostgreSQL, MySQL, Stripe, GitHub, Linear, Notion, Slack or Google Workspace data, plus PDFs and notes, and explore it as one graph
- Ask questions across tables and documents and get answers with charts, the queries run and a source for every claim
- Give Claude Code, Cursor or your own agents an MCP server over your company graph
- Trace every value back to the row or document quote it came from, and review values documents disagree on
- Try ontology-driven analytics on a made-up company before connecting real data
Dependencies for Helix Foundry Hosting
- Helix Foundry images by HelixDB:
foundry-site0.1.3,foundry0.1.2,ontology-agent0.1.1 - HelixDB v0.0.14 (graph database), MySQL 8.0 (Foundry's store), SeaweedFS 4.47 (S3-compatible store)
- PostgreSQL 18 with the Acme Corp sample data (optional demo source)
- An AI provider: a Claude or OpenAI key, or Azure OpenAI, Amazon Bedrock, Ollama or any OpenAI-compatible server, entered in the app
Deployment Dependencies
- Source and local guide: https://github.com/HelixDB/helix-foundry
- Foundry docs: https://docs.helix-db.com/foundry
- HelixDB: https://github.com/HelixDB/helix-db
- SeaweedFS: https://github.com/seaweedfs/seaweedfs
- Claude API keys: https://console.anthropic.com
Implementation Details
| Service | Role | Public |
|---|---|---|
| Gateway | Caddy: password prompt, then the app; MCP and HTTP Ask with a bearer token | yes |
| Site | Foundry's web app (Next.js) | no |
| Foundry | API, MCP, sync/draft/load/ask workers and the ontology agent; volume /work |
no |
| HelixDB | Graph database every ontology loads into; volume | no |
| Storage | SeaweedFS S3 API for synced tables, snapshots and documents; volume | yes (S3, signed requests only) |
| MySQL | Foundry's database; volume | no |
| Acme DB | PostgreSQL with Acme Corp's made-up sample tables | no |
Storage has a public domain because your browser uploads documents straight to it, to URLs Foundry signs. Every S3 request needs Foundry's signature. HelixDB checks no key: never give it a domain or TCP proxy.
First login
- Deploy. Nothing is required; optionally paste a Claude key into
ANTHROPIC_API_KEY(or an OpenAI key intoOPENAI_API_KEY) on Foundry. - Wait until all services are healthy. The first deploy builds five thin images on top of the published ones, which takes a few minutes.
- Open the Gateway's URL. Sign in with
BASIC_AUTH_USERNAME(defaultadmin) andBASIC_AUTH_PASSWORD, both on Gateway → Variables. - Foundry opens in My workspace. Without a key, open Settings › AI models and pick a provider. Keys entered there are stored sealed, never in a variable.
- Click Use the sample. It connects Acme Corp's database (accounts, contacts, subscriptions, invoices, tickets, usage), uploads its contracts and call notes, creates a ready-made ontology, loads it into HelixDB and asks a first question.
Your own data
Add a connector or upload documents, state a goal, and let the agent draft. A first draft can take 10 to 20 minutes on a hosted model. Review it, make it current and load it. Connectors may reach other services in this Railway project by their private names ({service}.railway.internal). Foundry seals every credential you give it with FOUNDRY_CONNECTOR_KEY on Foundry. Never change that key, and keep a copy: without it, the stored credentials cannot be read.
Connect your agent (MCP)
With FOUNDRY_AGENT_ENDPOINTS=on (the default), https://{your-domain}/mcp is Foundry's MCP server and https://{your-domain}/v1/ontologies/{id}/ask its HTTP Ask. Both skip the password prompt and require Authorization: Bearer {token}, where the token is FOUNDRY_LOCAL_TOKEN on Foundry. It acts as the owner of everything, so keep it in your client's environment. For example: claude mcp add --transport http helix https://{your-domain}/mcp --header "Authorization: Bearer $FOUNDRY_LOCAL_TOKEN". The in-app Set up with your agent prompt describes the Docker install and does not apply here. Set the variable to off to keep these routes behind the password.
Custom domain
Add it to Gateway, then set HELIX_LOCAL__SITE_ORIGIN on Foundry to https://{your-domain}. Also add the domain to STORAGE_ALLOWED_ORIGINS on Storage, or uploads fail.
Scaling and limits
Keep every service at one replica: Foundry's workers, HelixDB and the store keep state in-process or on their volumes. Scale vertically. Foundry needs about 1 to 2 GB while drafting or loading, so Hobby or Pro is recommended. On Free (0.5 GB) or Trial (1 GB), large drafts and loads can be stopped for lack of memory. FOUNDRY_WORK_MAX_GB (default 2) caps the snapshots one draft or load unpacks into the 5 GB Hobby volume. Foundry's own spend caps on your keys apply: $20 per load job, $100 a month for loads, $30 a month for questions.
Upgrades
Each image is pinned by tag and digest in a service variable: FOUNDRY_SITE_IMAGE on Site, FOUNDRY_IMAGE and FOUNDRY_AGENT_IMAGE on Foundry, HelixDB's image source, FOUNDRY_STORAGE_IMAGE on Storage. Upgrade the three Foundry images together to the set upstream's local/compose.yaml names, after reading its changes. Foundry migrates MySQL at start, and migrations only go forward, so back up the volumes first. The Site checks at build that the sample host it rewrites is still where it expects.
Costs
Estimated at Railway usage prices: about $12/month idle and $30/month with regular syncs and questions. Foundry reaches the store through its public URL, so synced data counts as egress. Model calls are billed by your AI provider.
Why Deploy Helix Foundry on Railway?
Railway runs the whole Foundry stack, from the web app and agent to the graph database, store and sample, in one project with HTTPS, volumes, private networking and logs. You get a shareable, password-protected Foundry instead of one bound to localhost, plus an MCP endpoint for your agents. This is a community template, not affiliated with or endorsed by HelixDB. Helix Foundry and HelixDB are HelixDB's open-source projects under the Apache-2.0 licence.
View Helix Foundry Ontology and Knowledge Graph from Your Data on railway.com
Similar templates
| Template | Category | DeploymentsDeploys |
|---|---|---|
| 9Router Self-hosted AI router for Claude, Gemini, Cursor & OpenAI tools. | AI/ML | 9,734 |
| flowise-railway Flowise - low-code LLM apps builder | AI/ML | 8,512 |
| LibreChat Open-source ChatGPT clone: multi-model, agents, search, multi-user auth | AI/ML | 6,762 |
| Hermes Agent by Nous Research Template for Hermes Agent by Nous Research | AI/ML | 6,413 |
| OpenClaw [Homebrew support] The AI that actually does things | AI/ML | 5,167 |
| Hermes Agent Self Host Hermes Agent. Autonomous AI agent w/ self-improving, tools & more | AI/ML | 4,092 |