Helix Foundry for CIOs and Chief Data Officers

Helix Foundry matches the same customers, accounts and records across your databases, tools and documents into one ontology that people and agents share. Every value keeps its source, every answer cites the records it used, and each person or agent sees only what is built from the sources they have been granted.

Book a meeting

One version of each record

  • Matched on keys you already have. Foundry finds the IDs your systems share and says how many rows matched.
  • Nobody agrees on a schema first. Foundry drafts the ontology from the data you connect, and your team reviews and edits it.
  • Unsure matches wait for a person. A record it can't match for sure can go to review instead of being guessed.

Answers you can check

  • Every value keeps its source. A table row, or a quote in a document.
  • Answers cite their sources. Each answer shows the steps the agent took and cites every record, row and quote it used.
  • Conflicts are held, not guessed. When documents disagree on a value, Foundry can hold it for review instead of picking one.
  • Every version is kept. Go back to any version of the ontology.

Current without a rebuild

  • Scheduled syncs. On Helix Cloud, sources sync daily on Free, hourly on Pro and every 15 minutes on Max, reading only what changed.
  • Change data capture. PostgreSQL and MySQL changes sync without rebuilding the ontology.
  • Self-healing. Broken links are repaired in the background, and low-confidence facts go to review.

Governance

  • Nothing visible by default. A member, team or agent key sees nothing until it's granted a source.
  • Access follows the data. Anything built from a source someone can't read is hidden from them.
  • Directory sync. People and groups sync from Microsoft Entra ID or Okta.
  • Ontology as code. Versioned, and editable by hand, by agent or through the API.

FAQ

What is an ontology in Helix Foundry?

A model of your business, such as customers, accounts, subscriptions and the links between them, built from your own systems and loaded into HelixDB as one connected graph. Every value in it keeps where it came from.

Which systems can it bring together?

Databases such as PostgreSQL (including Neon and Supabase) and MySQL (including PlanetScale), files in Amazon S3, uploaded documents and API sources, and tools such as Stripe, PostHog, WorkOS, GitHub, Linear, Slack, Notion, Google Workspace, Granola and Cal.com.

Can we start with one team or one question?

Yes. Start free on Helix Cloud, connect the systems that hold one part of the business, review the ontology Foundry drafts, then connect more.

How do people use it day to day?

They explore the graph, see where each value came from, and ask questions in plain words. Agents use the same ontology through the Helix MCP.

Who owns the ontology and the data?

You do. Helix Foundry and HelixDB are open source under Apache 2.0, and Foundry can run in your own infrastructure, so neither is locked in a proprietary platform.