---
title: "Deploy helix-foundry"
description: "AI-assisted data workspace for connected ontology and analytics."
category: "Analytics"
url: https://railway.com/deploy/helix-foundry
---

# Deploy helix-foundry

AI-assisted data workspace for connected ontology and analytics.

**[Deploy helix-foundry on Railway](https://railway.com/template/helix-foundry)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/helix-foundry/manifest.json

- **Creator:** kmaki's Projects
- **Category:** Analytics

## Template content

### helix

- **Image:** xiaosong233/helixdb-railway:latest

### app

- **Image:** xiaosong233/helix-foundry-railway:latest
- **Start command:** `sh -c 'node --import tsx services/executor/src/server.ts & exec node --import tsx apps/api/src/server.ts'`
- **Public domain:** Yes

## Documentation

# Deploy and Host Helix Foundry on Railway

Helix Foundry is an AI-assisted data workspace for connecting business sources, discovering a shared ontology, and exploring relationships through an interactive graph and analytics interface. It combines a browser UI, HelixDB graph storage, DuckDB execution, and persistent workspace data so teams can turn fragmented operational data into an understandable, queryable model.

## About Hosting Helix Foundry on Railway

Railway runs the web application and its private HelixDB dependency as Docker image services. The app receives a public HTTPS domain, while HelixDB stays on Railway private networking. Attached volumes preserve application workspaces and graph data across redeploys.

## Tech Stack

- Node.js 24 and TypeScript
- Fastify web/API server
- HelixDB graph database
- DuckDB execution engine
- Docker Hub images with Railway private networking
- Railway persistent volumes and generated HTTPS domain

## Why Deploy Helix Foundry on Railway

Railway provides a fast Docker-based deployment path, managed HTTPS routing, private service-to-service networking, persistent volumes, and simple environment-variable configuration. This keeps the UI reachable in a browser while the graph database remains private and protected behind the app service.

## Common Use Cases

- Explore connected customer, product, billing, and support data
- Build an ontology from multiple files, databases, and APIs
- Ask AI-assisted questions over an operational data workspace
- Prototype graph-powered analytics without managing servers
- Host a private internal data exploration tool

## Deployment Notes

The `app` service listens on container port 3001 and is the only public HTTP service. Its start command launches the internal DuckDB executor on port 3002 alongside the API so both processes share `/data`. The `helix` service listens privately on port 8080 and persists `/var/lib/helix`. Railway generates encryption and internal keys for each template deployment. Helix Foundry has no sign-in; use the generated public URL and configure an AI provider in the browser. Local Ollama is not bundled in this Railway template; choose a hosted provider in onboarding.

## Dependencies for Helix Foundry on Railway

Helix Foundry depends on a private HelixDB service for metadata, workspace state, and graph storage. The app references the dependency through Railway private networking and keeps user data on its attached volume.

### Deployment Dependencies

| Service | Image | Port | Volume |
|---------|-------|------|--------|
| app | xiaosong233/helix-foundry-railway:latest | 3001 | /data |
| helix | xiaosong233/helixdb-railway:latest | 8080 | /var/lib/helix |


## Similar templates

- [Formbricks | Open-Source Typeform & Qualtrics Alternative](https://railway.com/deploy/formbricks-surveys) — Surveys, NPS and in-app feedback on your own Postgres, Hub and Cube
- [Typesense PHP](https://railway.com/deploy/typesense-php) — official PHP client against Railway
- [Typesense vs Meilisearch](https://railway.com/deploy/typesense-vs-meilisearch) — self-hosted Typesense vs Meilisearch

Open this page in a browser: https://railway.com/deploy/helix-foundry