Choose the right home for
your data.
Six ways to bring information into Hapax. The right one comes down to a single question: what do you want Hapax to do with the information?
Start with what you want Hapax to do
The big divide: vaults know your content and search across it; connectors fetch a specific file on demand. Here are all six, and when to reach for each.
Document Vault
Want Hapax to know and search a body of documents.
Hapax reads and indexes the content, so it can search across everything and answer with citations.
In practice: BSA/AML procedures and lending policies, so branch staff can ask compliance questions in plain language.
Cloud Storage Connector
Want Hapax to open or fetch a specific file on request.
Fetches the file you ask for, live from the source. Nothing is indexed, and connecting is free.
In practice: “Pull the latest board deck from the March SharePoint folder”, without indexing every historical file.
Data VaultBeta
Want Hapax to count, sum, trend, or report on structured data.
Ask business questions of your tables in plain language, answered from read-only SQL.
In practice: “What’s our total delinquent loan balance by risk grade this month?”
MCP Connector
Want Hapax to take action in another tool.
Send an email, post to Slack, create a ticket, update a CRM. Agents act in live systems.
In practice: Draft replies in a shared member inbox and queue them for human approval before sending.
File Storage Bucket
Want Hapax to store the files your apps generate.
Infrastructure storage for the exports, attachments, and media produced by Hapax apps.
In practice: A Hapax app generates daily exception reports for compliance officers to download.
AI SearchBeta
Want Hapax to search structured data by meaning.
Find records by concept rather than exact keywords, across a Data Vault table.
In practice: Search past support tickets by meaning to find how a similar issue was resolved.
Data Vault and AI Search are in Beta, enabled per organization; ask your Hapax team to turn them on. The other four are available today.
Most organizations use a combination
These aren’t either/or. A typical setup mixes several, each doing the job it’s best at.
Where your Hapax credits actually go
Hapax bills credits on the volume of content actually processed, not per file, per connection, or per seat-action. Practically, a single 800-page PDF can cost more to index than two hundred short memos.
Size and page count drive cost far more than file count. Connecting anything is always free; you pay only when content is processed or an action runs.
A rough sense of scale
A fraction of a credit
a quick answer or lookup
One to two credits
a document analysis or draft
Tens of credits
indexing a whole corpus
Credits are $1.50 each. See how credits work →
Get the full owner’s manual
Every method in depth: when to use it, how it works, the cost levers, and real examples for your industry, plus a side-by-side comparison. Just tell us where to send it.
Not sure which fits your data?
Tell us what you want Hapax to do, and our team will help you map documents, files, and structured data to the right home, with a clear read on the credits involved.