Documentation
How it works
Written for engineers evaluating the design. Mechanisms, trade-offs, and the parts that did not work the first time.
Long form
Architecture whitepaper
Enforcing tenant isolation below the application — the isolation model, the verification failure that made it real, and the trade-offs that were rejected. Roughly 25 pages; printable to PDF.
Platform overview
IntegraHive is a multi-tenant B2B data-integration platform. Trading partners deliver data over REST, secure file transfer, or direct upload; the platform infers the schema each file actually carries, versions that schema as a contract, stages the records, applies governance policy, quarantines what breaks the contract, and raises anomaly events — with tenant isolation enforced by the database rather than by application code.
Architecture
IntegraHive is a multi-tenant B2B data-integration platform. Partners deliver data over REST, secure file transfer, or direct upload; the platform infers the schema, versions the contract, stages the records, applies governance rules, quarantines what breaks the contract, and raises anomaly events — with tenant isolation enforced by the database rather than by application code.
The governed ingestion pipeline
Every intake channel converges on one pipeline, so behaviour does not fork by how the data arrived. A file uploaded by an operator and a payload posted to a keyed endpoint follow the same seven stages and produce the same audit trail.
Governance and quarantine
Governance is the stage where the platform decides whether what a partner sent is allowed to become what downstream consumers read. It runs **before** acceptance, not as a later sweep, and its two visible outputs are a decision about the dataset's schema and a set of records held in quarantine.
Tenant isolation
In a multi-tenant platform, the question that matters is not "does the query filter by tenant?" but "what happens the one time it doesn't?"
Operational evidence
A control that works and a control you can demonstrate works are different deliverables. This page is about the second one: what the platform treats as evidence, why an exit code is not evidence, why ambiguity is a first-class outcome rather than a rounding error, and where the evidence is currently missing.
Engineering notes
Things that were harder, subtler, or more embarrassing than expected. Written up because the failures are more instructive than the successes.