A product foundry · Forged in Chicago
Reoforge encodes the messy government compliance-and-subsidy layer that generic software refuses to touch — once, into a shared core — then forges one vertical operating system after another from it.
The operating system for compliance-and-subsidy-heavy small businesses.
The shared core
Compliance + subsidy, encoded once
~40% of every vertical — prebuilt. Multi-tenant auth, the compliance-readiness engine, subsidy rate tables, accounting/AR, documents, billing.
Why now
A generic PMS, a generic daycare app, a generic DME tool — none of them can model the reality a small regulated operator lives in. For these businesses, compliance is existential and the funding runs straight through it. That's the gap nobody else will encode.
Government pays one share, the family pays the other, on region-dimensioned rate tables that change by program and year. Off-the-shelf billing has never heard of an eligible day or a copay split.
Licenses, certifications, and eligibility all expire on their own clocks — and a missed date is a citation, a clawback, or a shut door. Generic tools track none of it.
The money doesn't move until the record is correct, complete, and audit-ready. That gate has to be encoded into the workflow, not bolted on as a spreadsheet afterward.
The foundry
Reoforge isn't a pile of unrelated apps under one logo. It's a foundry: encode the compliance-and-subsidy layer once into a shared core, then forge one vertical operating system after another from it.
The compliance machine is the same across verticals — only the rulebook changes. So roughly 40% of every new product ships on day one, and the team spends its time on the regulations that actually differ.
One stack, all of it. Next.js + Supabase, with RLS tenant isolation. A shared @reo/* spine every vertical is built on.
The shared spine — prebuilt for every vertical
What each vertical adds on top
The one thing generic software won't: that vertical's exact compliance code and its subsidy program — modeled to the letter of the regulation it enforces.
The portfolio
Each product is a full operating system for its vertical — and each one encodes the exact compliance and subsidy its operators are stuck without.
DME
DMEPOS compliance + Medicaid / Medicare billing
“Built by someone who passed the accreditation.”
Childcare
DCFS licensing + CCAP subsidy
“If everything is compliant, the kin is taken care of.”
Housing
HUD / CHA inspections + Section 8 (HAP) subsidy
“Compliance and subsidy for affordable housing.”
Proof, not a pitch deck
The platform thesis isn't a hope. The second vertical was forged mostly from the first: 38 of the first 45 build hours were Reoxis reuse.
Section 8 (HAP) and CCAP are structurally the same machine.
Two different government programs, one shape. Build it once and reuse it across housing and childcare:
3
verticals on one shared core
~40%
of every vertical prebuilt
38 / 45
hours of vertical #2 were reuse
1 stack
Next.js + Supabase + RLS
What's next
Subsidy-heavy and compliance-heavy. If a small operator's funding runs through a government program and a missed inspection can close their doors, it's a candidate for the foundry.
We onboard a small number of founding partners per vertical — operators who live the compliance and want a say in the roadmap.
The name, the philosophy
Forge beats force for what this company is. A forge builds things from raw material — the verticals from the shared core. “Force” just signals power. The forge is the truer metaphor for a product foundry.
The umbrella deliberately carries a different shape from its children — Reoforge over Reoxis, Reokin, Reohaus — so the hierarchy reads at a glance.
The Reoxis founder passed the DME accreditation. Every product is shaped by people who live the compliance — not learned from a pitch deck.
The dual-payer subsidy and the inspection/recert cadence — the exact things generic software won't encode — are the whole point.
Published pricing where incumbents say “contact us for a quote.” Every compliance decision traceable to the regulation it enforces.
Two vertical operating systems are running on the shared core today — with a third on the anvil. Go see them.