Hyve Core

The intelligence foundation behind every Hyve product.

Hyve Core is the architecture BuildIQ, Legis, and our other products share. It connects domain knowledge, applications, and AI agents, while keeping each organization's information in its own scope and recording where information came from.

One foundation, built once, used by every product.

Scoped knowledge

Each organization's documents and knowledge base live in their own space, with a separate search index per organization, and are searched only on that organization's behalf.

Separation in the database

For construction data, the database itself refuses to show one company's records to another. The rule sits below the application and fails closed: a request that does not name its company sees nothing.

Sign-in and permissions

One sign-in across Hyve's applications, with roles per organization. Products check that a person belongs to an organization before showing its data.

Source and audit history

Construction actions are written to an append-only audit trail, AI tool calls are logged, and every Legis summary records the model, prompt version, and date that produced it.

More than one AI provider

Hyve uses models from more than one provider. Records live in Hyve's own database rather than inside any provider's service.

Agents with human review

AI prepares; people decide. In BuildIQ, AI actions are proposals a person approves, and a take-off never changes a bid until the office applies it.

In design

The first organization gets a good model. The hundredth gets a better one.

Today, every organization that adopts AI starts from zero. Hyve Core is designed so that organizations in the same field can make each other's AI better without handing over their data. Each participant's records stay in its own space; what the network learns from is patterns, never the records themselves.

Your data stays yours

Records, documents, and conversations stay in your organization's own scope, under your control. They are never shown to another participant.

Patterns, not records

What the network shares is learning: model improvements and aggregate signals, combined across participants so that no single organization can be picked out.

Opt in, on your terms

Taking part is a choice each organization makes for itself, and one it can withdraw.

Better as the network grows

Every new participant makes the model better for everyone in the field: what one builder's estimates teach it, the next builder starts with.

The federated model is in design and not available today. We are designing it first for the fields where Hyve already works, construction and legislative research, and we will describe here how it protects each participant's data before it launches. Interested in being an early participant? Talk to us →

See Hyve Core at work in a real product.

We can walk you through how BuildIQ or Legis uses it, or discuss a pilot built on it.