Underwrite the exposure that's actually on site — not the ACORD that says it's fine.
No promises above the fold. Records.
Live verified records from the graph -- two-party verified, anchored to an immutable ledger, receipt on file. Where we have no authentic source, we name the gap instead of filling it.
Asserted by one party. Verified by a distinct second. Anchored to an immutable ledger.
A certificate resolves from the live jobsite signal -- not a hand-typed PDF that aged the moment it printed.
Every chip resolves to the source. “Check it” is the product.
And where we have no authentic source -- we say so. The gap is part of the tape.
SHARED GRAPH
Underwrite the project on one shared graph.
InsureConniXT is how the specialty insurance operating system serves brokers, carriers, and sureties. One project graph spans construction, insurance, and finance -- ACORD-native, with policy, claim, and coverage on the same record.
See the risk as it actually is.
- Live project performance feeds underwriting -- not a snapshot from bind day.
- Coverage gaps surface at handoffs, not at claim time.
Submission to bind, in one graph.
- One submission flows to your full carrier panel.
- ACORDs and COIs resolve from Cascade, not template chaos.
Settle on what's actually verified.
- Sureties cure on the same payment ledger the GC is funding from.
- Claims data feeds back to underwriting in real time.
Two records, same project
One is alive. One is a photograph.
A certificate of insurance is a snapshot of a moment that has already passed. The project graph is the moment you're standing in. Same project, two records — here is what each one actually knows.
| Live verified project graph | ACORD / COI snapshot on file | |
|---|---|---|
| Reflects coverage as it stands today — not as of the issue date | ✓ | |
| Updates itself when a policy is renewed, cancelled, or amended | ✓ | |
| Verifiable back to the carrier's record | ✓ | as printed |
| Tied to this project's graph — every sub, draw, and lien in one place | ✓ | |
| Tells you the moment something changes | ✓ |
The four moats.
Everything below runs on the same shared graph -- these are the four things that only work because of it. sample project: Tarrytown Lighthouse -- $4.2M civil
One live data stream
Every platform claims a single source of truth -- then hands each stakeholder a different export. Here the owner, GC, carrier, lender, and auditor views all render from ONE immutable record, so a number can never disagree with itself across the table. When the record changes, every lens updates in the same instant; there is nothing to reconcile because nothing ever forked.
When one milestone fires, three industries update.
Everywhere else, construction, insurance, and finance run on separate systems stitched together with email and re-keyed PDFs. Here a verified milestone IS the coverage check and IS the draw trigger -- one event, three industries, zero handoffs. Copying this requires owning all three ledgers at once, which is precisely the point.
Construction: milestone complete
GC marks milestone #7 at 100%
Insurance: coverage check
Carrier auto-verifies coverage applies
Finance: draw trigger
Lender auto-releases the milestone draw
Ops: vendor payout
Payment pipeline schedules vendor ACH
Audit: ledger entry
All four above recorded append-only with the same event ID
Rewind the policy to any moment.
Disputes are arguments about what people knew and when they knew it. Cascade snapshots turn that into an exact query: scrub to any day and see precisely what the underwriter, the lender, or the adjuster saw -- not a reconstruction, the actual rendered state. Litigation-grade hindsight, standard with the platform.
Project
Tarrytown Lighthouse
As of April 12, 2026
% Complete
94%
Budget Spent
$7.6M
Schedule
+2d
resolved: /mace/projects/tarrytown-lighthouse
Drag the handle -- or use left right -- to rewind the dashboard through real Cascade snapshots.
Click any number. See exactly how it was computed.
Every figure on the platform resolves through a named chain -- platform floor, vertical policy, solution default, tenant override -- down to who set each value and when. Click any number and the resolution rail shows its full lineage, anchored to the Confidential Ledger. A number you can interrogate is a number you can trust; a dashboard that cannot explain itself is decoration.
Purpose-built products on the same graph.
Each one is a focused operating surface -- same ledger, same receipts, zero handoffs.
The operating surface for insurance operations -- brokers, underwriters, risk and compliance, and the insured all working the same record. Submissions, ACORD forms, binders, COIs, endorsements and renewals resolve through Cascade, so one edit to a schedule of values or an additional insured propagates to every certificate and policy that references it. No re-keying, no parallel spreadsheets -- and every cert traces to a two-party verified jobsite signal instead of a stale, hand-typed PDF.
Explore →METROFLOW IQMetro and infrastructure orchestration across plants, trucks, trades, permits and weather on one shared graph -- the layer where physical activity becomes underwritable exposure. Live crew counts, completion milestones and safety events flow straight into eligibility, schedules of values and renewal underwriting, so the risk reflects the work as it actually happens. The same operational signal that runs the jobsite is the signal that prices and binds the risk against it.
Explore →The risk is live. Your paperwork isn't.
Margins and losses hide in the gap between the policy on file and the project as it actually is.
- Stale ACORDs
You bound the risk you saw a year ago.
Coverage resolves from the live project graph -- schedule of values, additional insureds, and completed value update as the work does, not at the next renewal scramble.
- Coverage gaps
The gap surfaces at claim time, not handoff.
When a milestone fires, the coverage check fires with it. A lapse or an uncovered exposure is flagged at the handoff -- two parties on the record, anchored to an immutable ledger.
- Surety blind spots
You cure on paper the GC already moved past.
Sureties read the same payment ledger the GC is funding from. Draws, waivers, and completion all resolve to a two-party verified record before anything releases.
A community that compounds the record.
Your carrier × class cell is the living edge of the graph: the feed is the record changing -- a binder issued, a certificate renewed, a verified member joining, a gap closing.
- Fact-deltas
News that is literally the record.
A schedule of values revised, a COI renewed, an additional insured added -- a feed item with a receipt, not a newsletter take.
- Verified standing
Reputation you can audit.
Status is verification position -- asserted, verified, confirmed -- ledger state, not karma.
- The gap ledger
We publish what we don't know.
Every withheld number is a named gap with what unlocks it. Correct us or beat us to the source.
Solutions that settle, not just track.
- Compliance
ACORD-native certs & evidence
Every certificate traces to a two-party verified signal. The auditor's trail is the default, not the scramble.
- Money
Verified draws & surety gates
A draw or a cure releases only against a two-party, ledger-accredited checklist. Fail-safe, not best-effort.
- Market
Evidence-backed underwriting
Submissions that carry verified exposure -- live project performance, cert status, accredited completion.
Founding metros: Dallas–Fort Worth & Las Vegas
Specialty construction insurance first -- live project performance feeding underwriting, certificates resolving from the jobsite signal, sureties on the same ledger as the GC. Design partners meet our founders in person, in your market.