helix-db

HelixDB is a database that makes it easy to build all the components needed for AI applications in a single platform.

You don't need a separate application DB, relational DB, vector DB, graph DB, or application layers to manage the multiple storage locations. HelixDB gives your agents federated access to company data, for memory, company brains, and applications.

Helix primarily operates with a graph + vector data model, but it also supports KV, documents, and relational data.

Getting Started

1. Install the CLI

The Helix CLI runs and manages local instances and talks to Helix Cloud.

macOS and Linux:

curl -sSL "https://install.helix-db.com" | bash

Windows PowerShell:

irm https://raw.githubusercontent.com/HelixDB/helix-db/main/crates/cli/install.ps1 | iex

Already installed? Update to the latest version with helix update.

2. The quickest path — helix chef

helix chef is an interactive, one-shot bootstrapper. It installs the HelixDB query skills and docs MCP, scaffolds a project, starts a local instance, seeds some example data, and writes a HELIX_CHEF_PROMPT.md. It detects supported agents in this order: Claude Code → OpenAI Codex → OpenCode → Cursor Agent. When one is available, it can hand off and build a working app — frontend and all — from a one-line description of what you want.

helix chef

That's it — no flags. Answer "what do you want to build?" and follow the prompts.

3. Manual local setup

If you would rather wire things up yourself, follow the canonical local quickstart. It uses the exact files and dev instance generated by the current CLI.

Writing queries with the SDKs

Queries are authored with the Rust, TypeScript, Go, or Python DSL and sent straight to a running instance through POST /v2/query — no build or deploy step. The SDKs produce the same JSON AST. The examples below talk to a local instance on http://localhost:6969 (the default helix start dev port). See the Querying Guide for the full builder catalog and query wire format.

Rust

Install the crate (published as helix-db, imported as helix_db):

cargo init && cargo add [email protected] tokio sonic-rs

Define queries as #[query] functions, then run them directly through the client:

…

TypeScript

Install the package (Node.js 20+):

npm init -y && npm install @helix-db/[email protected]

Define your queries as functions, then POST them to the running instance:

…

Python

Install the published PyPI package:

python -m pip install helix-db==0.3.4

Build requests with snake_case builders, then send them with the client:

…

Go

Install the released Go module:

go mod init example.com/my-helix-app
go get github.com/helixdb/helix-db/sdks/[email protected]

Build a request with ordinary Go functions, then execute it with the client:

package main

import (
    "context"
    "fmt"
    "log"

    helix "github.com/helixdb/helix-db/sdks/go"
)

func getUsers() helix.Request {
    return helix.ReadQuery("get_users").
        VarAs("users", helix.G().NWithLabel("User").ValueMap("$id", "name")).
        Returning("users")
}

func main() {
    client, err := helix.NewClient("http://localhost:6969")
    if err != nil {
        log.Fatal(err)
    }

    var response map[string]any
    if err := client.Exec(context.Background(), getUsers(), &response); err != nil {
        log.Fatal(err)
    }
    fmt.Println(response)
}

Version names

• HelixDB v3 is the current product and SDK generation.
• Helix CLI 3.x is the independently released command-line client. Check its exact version with helix --version.
• POST /v2/query is the current HTTP wire endpoint. Its v2 path does not mean HelixDB v2 or CLI v2.

HelixDB Cloud

HelixDB Cloud is an object-storage-backed deployment with integrated vector and full-text search, full ACID transactions, a single writer with auto-scaling reader nodes, and high availability (3+ gateways and DB nodes). The CLI uses a WorkOS session for Cloud control-plane and brokered query operations:

helix auth login
helix workspace list
helix project link <project-id> --workspace <workspace-id>
helix init cloud --database tenant:<tenant-id> --project <project-id> --workspace <workspace-id>
helix query production --file examples/request.json

Cloud queries go through the authenticated backend broker. Application keys returned by tenant or key creation are for direct gateway clients; the CLI displays them once and never stores or uses them.

Commercial Support

HelixDB Cloud

HelixDB is available as a distributed, high-availability, managed service. If you're interested in using Helix's managed service, go to our website to get started or contact us to talk with a founder.

Docs & Community

• Documentation · Querying Guide
• Discord
• X / Twitter

Just Use Helix.