Bearing wired into your own measurement infrastructure. Audited posture, internal analytical owners, trace chain ending in your audit trail.
Discipline · heavy
For organisations that want the engine inside the stack, not as an external subscription. Light integration footprint. Heavy methodology discipline.
IS
The architectural distinction.
Bearing Licensed is Bearing operating against your named positions, integrated into your measurement infrastructure under your security perimeter, with the trace chain terminating inside your audit trail rather than in BearingA's. The engine is the same engine — same corpus, same statistical floor, same trace architecture, same cannot-be-wrong commitment. What differs is the operational topology and the audit-trail terminus.
This is the architecture institutional buyers select when their internal stack requires the substrate inside the perimeter rather than as an external dependency — banks whose risk-systems posture requires audited internal deployment, asset managers whose investment-committee infrastructure assumes internal analytical ownership, family offices whose private-market exposure analysis requires the engine operating against books the institution does not externalise.
Light integration footprint by design. Three endpoints. A senior engineer wires it in a week. The depth is in the methodology validation and the security perimeter, not the codebase. Heavy methodology discipline by design. BearingA's methodology team partners with the institution's risk-infrastructure team through deployment kickoff, methodology validation, and corpus-extension cycles where the institution's portfolio surfaces gaps in the canonical substrate.
IN SCOPE
Foundation, Practice, Enterprise.
Foundation
Practice
Enterprise
Each tier carries the same engine and the same methodology discipline. The differentiation is in the depth of embedding, the breadth of workflows, and the contractual scope of the corpus-extension and methodology-validation cycles. The cannot-be-wrong commitment travels at all three tiers — what differs is how much of the institution's analytical infrastructure operates against the engine.
CHANNELS
Direct and Partner.
The institution licenses the engine into its own measurement infrastructure.
The engine is deployed by a consultancy or systems partner into their client base.
Both channels operate against the same engine, the same methodology discipline, and the same architectural commitments. The choice is procurement-shape — the institution that prefers direct contractual relationship and internal deployment selects Direct; the institution working through an existing consulting or systems-integration relationship selects Partner. BearingA validates either deployment against the Method before production cutover.
POSTURE
Three endpoints, one week.
Not · in the codebase
POSITION SUBSTRATE
READ DELIVERY
TRACE RESOLUTION