Integrius Search
One governed search API across everything.
Real-time federated search across all your governed data products. Fuzzy matching, relevance scoring, facets, autocomplete. Derived from the data layer, not a separate index to maintain.
If your data is unified, it is already searchable.
What This Is
Search endpoints derived automatically from your governed data products.
A single search API across all your governed data products
Real-time: searches the data layer directly, no index to refresh
Entity-keyed: results are grouped by customer, transaction, account, and other business concepts
Governance-aware: respects RBAC, access scopes, domains, and environments
API-first: no UI opinions, no manual indexing, no tuning rituals
What This Is Not
Integrius Search is an API layer, not a UI. It queries live data through the governed layer. Your applications consume the API.
Not a search UI or end-user application
Not Elastic, Algolia, or OpenSearch
Not a data lake query tool
Not a separate system to manage, scale, or keep in sync
How Integrius Search Works
No configuration. No setup screen. No index definitions. Search is a consequence of unification, not a separate feature.
Connect data sources
Your databases, APIs, and SaaS tools
Map to Standard Fields
Your organization-wide canonical schema
Create data products
Governed, owned, versioned API contracts
Search appears automatically
Derived from the data layer. Nothing to build.
Search Capabilities
Everything in a single governed API call. No stitching. No fan-out to manage.
| Capability | Details |
|---|---|
| Federated search | One API call spans every data product the caller has access to |
| Fuzzy matching | Typos and near-misses still find the right results |
| Relevance scoring | Results ranked by match quality, exact matches first |
| Autocomplete | Matching products, fields, and entity types suggested as you type |
| Faceted results | Counts by product and entity type for drill-down |
| Result highlights | Context snippets showing exactly where and how the query matched |
| Governed by design | Respects RBAC, field-level access, consumer scoping, org isolation |
Built for Governed Environments
Respects data product access scopes (public / shared / restricted)
Environment-aware (dev / test / prod)
Domain ownership enforced
Search results are explainable: you can see exactly where data came from
No shadow access paths created
Who Uses Integrius Search
Executives
- Find answers without knowing systems
- Trust results because they're governed
Data & Platform Teams
- One search surface instead of dozens
- No duplicate indexing infrastructure
Product & Ops Teams
- Search customers, orders, activity across systems
- Zero schema knowledge required
Why Not Elastic or Algolia?
Every search product on the market works the same way: copy your data into an index, then keep that index in sync forever. Integrius Search skips the copy. It searches the governed data layer directly.
| Product | How It Works |
|---|---|
| Elastic / OpenSearch | You build and run a cluster, then build and babysit the indexing pipelines that feed it |
| Algolia | Fast frontend search, but your data is copied into their cloud |
| Coveo / Glean | Enterprise search platforms with their own connectors, their own index, their own governance model |
| Integrius Search | Searches the governed data layer directly. No index to maintain, no copies, governance already enforced |
Pricing
Search is not a feature. It's a product.
€100,000/year add-on on Enterprise and Platform Lite. Included in Platform.
| Tier | Search | Price |
|---|---|---|
| Pilot | Not available | |
| Enterprise | Premium add-on | €100,000/year |
| Platform Lite | Premium add-on | €100,000/year |
| Platform | Included | No extra cost |
Why is it priced like this? Because it replaces a search platform, an indexing pipeline, and the team that maintains both. One API call, complete picture, governed results, live data.
Requires an active Integrius Core deployment.