Skip to content
haystak
Request a demo
The content-intelligence engine

Secure enterprise search.
Across every source.

haystak indexes files, databases, and cloud content where they already live, then makes the whole corpus searchable for people, for AI agents, and for the BI tools your analysts already use. Every result is trimmed to who is asking.

Indexed in placeRead-onlyPermission-trimmedAI-native
File system SMB · network SQL · NoSQL Box · cloud haystak Agent haystak Engine People · Search AI · MCP Analysts · SQL Indexed in place · read-only · permission-trimmed at every door
Backend-agnostic

One engine. Your choice of backend.

The same haystak engine runs on Elasticsearch, OpenSearch, PostgreSQL, MariaDB, or MongoDB — you're never locked to one store. For production search at scale, Elasticsearch and OpenSearch are the recommended backends. Host it on macOS, Windows, or Linux.

Elasticsearch OpenSearch PostgreSQL MariaDB MongoDB
Doing it different

Your data lives everywhere. We index it in place.

No migration, no upload, no egress. Agents run at the edge — on-prem or in the cloud — authenticate, read, and index. Nothing moves.

Index in place

Native connectors read sources where they are. One backend-agnostic engine unifies files, databases, and cloud into a single corpus.

Read, never write

Source files are never modified. Everything haystak derives — text, metadata, tags — is stored separately and append-only. Originals stay intact.

Any system, any platform

One engine over any of five backends, on macOS, Windows, or Linux. Never locked in — Elasticsearch and OpenSearch recommended for scale.

Core capabilities

A corpus that understands structure, content, and provenance.

Built on a patent-pending storage methodology — identity and origin encoded into every record.

One query, every source

Files, cloud, and databases in one result set — trimmed to each user's grants.

Schema-aware

Databases stay structured — PKs, FKs, and indexes model a relationship graph for cross-source joins.

Content is first-class

Extracted text is a searchable entity — query by what a file says, tag specific passages.

Render at ingest

Thumbnails, page previews, and video poster + scrub sprites — content-addressed.

One ACL. Every surface.

Four ways in. One set of permissions.

People, AI, analysts, and your own apps reach the same corpus through the same RBAC engine — authenticated and fail-closed. No surface is a backdoor.

For people

Search

Full-text and structured search across every indexed source, with results trimmed to roles, groups, and inherited scopes.

  • web portal + search UI
  • cross-source results
  • row-level ACL
For AI

MCP & ML tools

Two ways to put AI on the corpus: MCP tools for agents, and a RAG/ML API for retrieval and enrichment — both permission-trimmed to the caller.

  • MCP · agent-native
  • RAG · embeddings
  • fail-closed
For analysts

SQL endpoint

Speaks the SQL Server wire protocol (TDS). Point Power BI, Excel, or SSMS at the corpus and query it in T-SQL.

  • files & records as tables
  • INFORMATION_SCHEMA · sys.*
  • permission-trimmed at the wire
For developers

REST API

Every capability over HTTP, documented in an OpenAPI spec with a built-in Swagger UI. Wire the engine into anything you build.

  • OpenAPI + Swagger UI
  • search · aggregate · render · ML
  • same auth & scope
See it in action

Real product. Real corpus.

haystak admin console
The haystak admin console - workers, schedules, and processing at a glance.

Short clips of the product running against a synthetic test corpus — people search and analyst queries. Click any one to play.

Security & trust

Made for work you have to account for later.

Access is bounded by scope and enforced by role. The audit trail is append-only, so no one can quietly rewrite it. Identity comes from your own directory — LDAP, Active Directory, Open Directory, or FreeIPA — and every query, view, and write records who did it, when, and under what permission.

  • Scope-level RBAC — access bounded to projects, campaigns, incidents, or any scope you define.
  • Immutable audit — append-only; no update, no delete, a complete and attributable audit history.
  • Directory identity — LDAP / AD / Open Directory / FreeIPA, with local break-glass.
  • Fail-closed — deny by default across REST, search, MCP, and SQL.
  • Provenance & C2PA — every value tagged by origin; Content Credentials validated at ingest.
One engine, many products

The same core, shaped for the work.

Scopes, RBAC, audit, render, ML, and the MCP/SQL surfaces are shared primitives. Products differ in curation and UI — the engine underneath is the same.

haystak Assets Beta

Digital asset management built on the engine: schemaless tagging, content-first search, near-duplicate detection, renditions, and rich-media preview — provenance-aware, your assets where they live. In early access today.

Build your own

Everything is reachable over REST, MCP, and SQL — with key building blocks open-sourced. Backend-agnostic, horizontally scalable, namespace-isolated — build a vertical on the same corpus and primitives.

See it on your data

Secure enterprise search, on your own corpus.

A focused walkthrough — on-prem, read-only, indexed in place, permission-trimmed end to end.