84 facilities · 5 funds · 113,733 events
What you can use today.
The Evidence Spine is a working production system — 414,794 lines of production code on a Python/FastAPI · React/TypeScript · PostgreSQL/Neon · Redis · Vercel serverless · GitHub Actions stack, with NUMERIC(24,9) precision throughout and Newton-Raphson EIR computation to 10−10 tolerance. Every figure below is pulled from the live demo environment, not a deck.
The seven pillars
Seven pillars, from origination to audit — 22 compute engines behind 17 modules, on one identifier.
Each pillar is a stage of the facility lifecycle. Behind the 17 modules a controller sees sit 22 deterministic compute engines, exposed through 593 API endpoints across 65 domains. Every module hangs off the same persistent facility identifier; every event flows through the same Evidence Spine. Click any pillar to see what executes on the platform today.
Facility economics
- Life-of-loan (EIR, FASB 91)
- Life-of-loan reconstruction
- Missed accruals
- Borrowing base
- Participations
- Debt securities
- Valuation (ASC 820)
Fund & investor
- Fund routing
- Partnership allocation
- Carry accrual
- Investor performance
- Investor drilldown
- NAV per share
- Monthly return
- IRR
Reporting & risk
- Dual reporting (US GAAP / IFRS)
- Performance attribution
- Risk metrics
- Volatility
- Projection
Evidence
- Daily position Merkle
- Extraction comparator
All 22 engines, as registered in the platform on September 5, 2026.
Pipeline intake, term sheet capture, structured negotiation tracking, and the morning briefing surface that anchors every operating day.
Deal Origination
Pipeline ingestion, term-sheet capture, structured underwriting, IC memo generation. Each pipeline event hashes onto the Evidence Spine.
Morning Briefing
Daily operations control surface — KPI cards, exception queues, cash positions, attestation gaps, deal flow.
Six representative views
What auditors and CTOs evaluate first.
The platform contains 230 operational pages — the six below are the ones institutional reviewers consistently open first because they are the highest-evidence surfaces.
Five-Layer Reconciliation
- Layers
- 5
- Variance
- $0.00
- Records
- 144 of 145 at $0.00 (1 intentional break)
Source systems (servicing) must match target systems (accounting) to the penny. The engine runs five reconciliation layers from position-level ($5.00 tolerance) to fund-level ($0.00 tolerance). Any break triggers a mandatory cure workflow.
Zero-Variance Architecture
Attestation Completeness Matrix
- Events tracked
- 113,733
- Required roles
- 5 per event
- Coverage cadence
- Daily
Every material event requires five-role attestation: Operator, Agent, Administrator, Borrower, Fund Manager. The matrix tracks coverage daily across the full portfolio and flags gaps before they reach audit.
PCAOB AS 1105
Daily Position Accounting
- Compliance
- FASB 91 / ASC 310-20
- Net investment check
- < $0.01
- Granularity
- Daily
Every facility carries a daily position record: principal balance, carrying value, accrued interest (EIR), OID amortization, deferred fee accretion. Each row includes a net investment check that must balance to the penny. Max delta across 41,200 records: $0.0000000240.
FASB 91 / ASC 310-20
Borrowing Base Waterfall
- Steps
- 5
- Advance rate
- 85%
- Coverage
- 1.34×
A five-step waterfall computes the borrowing base: gross collateral pool, eligibility screening, concentration limit deductions, advance rate application, net borrowing base. Utilization and coverage ratios update in real time.
Credit Facility Compliance
Multi-Basis Accounting
- Expected
- GAAP / FASB 91
- Contractual
- Credit agreement
- Legal
- Default basis
Three concurrent accounting bases — Expected (GAAP/FASB 91), Contractual (credit agreement terms), Legal (default provisions) — all derived from one event stream. Book variances surface instantly for compliance and risk review.
Three Books of Record
Compliance Rules Framework
- Active rules
- 10
- Domains
- 5
- QC assertions per deploy
- 28
Deterministic compliance rules across 5 domains (Credit, Concentration, Reporting, Regulatory, Operational), each executing as automated SQL tests or manual attestations with full batch tracking and trending.
5 Compliance Domains
Complementarity
Designed to integrate with the systems already in place.
Enveriti is complementary infrastructure — confirming and hydrating credit data firmwide. It supplies verified journal entries to fund accounting platforms (e.g., Geneva, Investran, eFront), reconciled positions to administrators, and cryptographic attestations to agent banks. Existing systems continue doing what they do; Enveriti supplies the evidence layer beneath them.
Enveriti supplies
Verified journal entries
to Fund accounting platforms
Standard CSV / XML GL export — no custom API integration required
Enveriti supplies
Reconciled positions
to Fund administrators
Per-facility carrying values, accrued income, and reserves with full provenance
Enveriti supplies
Cryptographic attestations
to Agent banks & auditors
Hash-chain provenance per event under PCAOB AS 1105 evidence sufficiency
Computational precision · XIRR vs. EIR
Why textbook IRR fails complex private credit instruments.
The Effective Interest Rate is a non-linear equation with no closed-form solution. Standard XIRR implementations diverge or oscillate on PIK capitalizations, partial prepays, fee amendments, and amortization restructurings — every common pattern in private credit. The Enveriti EIR engine uses a convergence-bounded Newton-Raphson solver: bracketed root-finding with a hard iteration ceiling that never diverges and produces deterministic, reproducible, audit-grade rates on every lifecycle event.
XIRR (spreadsheet standard)
- Tolerance: ~10−7
- Day-count convention: not supported
- Does not recalculate on partial prepays or PIK capitalizations
- Divergence on complex instruments produces audit findings
EIR · Convergence-bounded Newton-Raphson
- Tolerance: ≤10−10 (hard iteration ceiling, never diverges)
- Day-count conventions: 30/360, ACT/365, ACT/360
- Recalculates deterministically on every lifecycle event — PIK, partial prepays, amendments
- FASB 91 / ASC 310-20 compliant for loan origination fee amortization
Deployment posture
Where the data lives. What an evaluation does not touch.
The current platform runs on FastAPI with PostgreSQL — the data model is Canton-ready, with every table, event, and attestation carrying the structural fields a Canton deployment requires. Activating Canton ledger transaction IDs and signatures from participant nodes is a configuration step, not a rebuild. An evaluation engagement uses a self-contained demo environment with synthetic facilities and counterparties; no customer data is required, and no customer systems are touched.
See the standards Enveriti enforces.
Standards & evidence →How Enveriti is priced
A fee that falls with scale, not one that rises with headcount.
A flat annual platform fee, plus a small assets-linked component that steps down as assets grow — so the cost per dollar administered falls with scale rather than rising with headcount. The structure is deliberate: most private credit operating budgets are labor, and labor scales with complexity. Enveriti’s flat fee is set well below what a comparable administrator charges annually, and the fee as a whole is designed to sit inside the reconciliation, close, and audit-support cost it displaces.
The assets-linked component never exceeds 1.5 basis points and steps down from there to 0.3 bps at scale. Pricing is quoted per engagement; a worked example against your facility count and assets under administration is part of every first conversation.
Request a worked example →