Every Unit. Every Dollar.
One Board.
The multifamily ERP where AI lives in the ledger, not on top of it. One platform. One database. One source of truth — for your operations, your owners, and your residents.
An ERP built for the way operators actually work.
For two decades, multifamily operators have had to choose between accounting depth and operator UX. UnitBoard combines both in one codebase, one data model, one subscription — with Claude wired into every workflow.
→ The single platform that scales from 50 doors to 50,000.
Real GL. Multi-entity. Audit-ready.
Full chart of accounts, journal entries, multi-property + multi-entity, B-vs-A reporting, owner distributions. Enterprise-grade books from day one — without an enterprise implementation.
Built for the team that runs the property.
Clean dashboards, mobile-first, drill-through everywhere. Resident portal, owner portal, leasing pipeline, work orders, renewals — every workflow on the same page as the data.
Claude in every workflow. Default behavior.
Codes invoices, drafts resident replies, summarizes the rent roll on demand. Public REST API + webhooks on every plan — your data, your stack, no per-integration tolls.
| Capability | UnitBoard | Yardi | ResMan | AppFolio |
|---|---|---|---|---|
| Single Postgres source of truth | ||||
| Modern operator UX (3-click rule) | Partial | |||
| AI-first (not bolt-on) | Add-on | Add-on | ||
| Public API + webhooks | $25K each | Limited | ||
| Multi-property + multi-entity | Add-on | Add-on | ||
| Native mobile (iOS + Android) | Partial | |||
| LIHTC / HUD compliance | Add-on | |||
| SOC-2-readable controls | ||||
| PricingImplementation cost | $0 | $50K–$500K | $5K–$25K | $400–$5K |
| Per-unit pricing (mid-market) | $1.50/u | $5–$8/u | $2.50–$3.50/u | $3.20/u |
Pricing & feature parity verified against vendor pricing pages and G2/Capterra reviews, April 2026.
Yardi's ledger discipline. ResMan's operator UX.
AI that lives in the ledger.
We didn't reinvent multifamily accounting. We took what works — Yardi's ledger architecture and ResMan's operator-first interface — and put a 2026 stack and AI substrate behind it. Here's what we kept, what we added, and what's shipping next.
Ledger discipline.
Yardi defined enterprise-grade real estate accounting. We kept the rigor, dropped the 1990s UI.
- Real double-entry GL with proper account types (asset / liability / equity / revenue / expense)
- Append-only journal entries — auditable, not editable
- Multi-property, multi-entity accounting on one Postgres
- Balance sheet, P&L, cash flow, AR aging — computed from ledger, not screen-scraped
- Owner distributions math (gross income → expenses → mgmt fee → owner share)
- Vendor directory with default GL coding
Operator-first UX.
ResMan rewired multifamily software around the property manager. We took the philosophy and put it on a modern stack.
- Dashboard-as-homepage — occupancy, AP aging, work-order SLA, NOI at a glance
- 3-click rule on every workflow
- Renewals + rent-recommendation engine as a first-class flow
- Notices with state-aware legal templates
- Resident + owner portals as their own role-bound surfaces
- Mobile-responsive on day one (native iOS / Android in roadmap)
AI substrate + open API.
Neither Yardi nor ResMan was built for the era where a single engineer with Claude can ship what 30-person teams used to.
- Bo — in-app AI assistant with tool-use against the live ledger
- Claude codes invoices, drafts resident replies, writes variance commentary
- Public REST API on every endpoint, OpenAPI 3.1 documented
- Webhooks on every plan — no per-integration tolls
- Built to be a spoke in a multi-product hub, not a closed silo
- Modern stack: Next 16, server components, Postgres + RLS, Tailwind + shadcn
Closing the depth gap with Yardi — quarter by quarter.
Yardi has a 40-year head start in compliance, multi-entity consolidation, construction accounting, commercial leasing, and a thousand other niches. We’re not pretending to match every line item on day one. Here’s the sequence — each milestone targets a specific gap that costs us enterprise prospects today, ranked by how often it comes up in conversations. The architecture is additive: every quarter extends the same Postgres, same chart of accounts, same journal lines. Nothing here forces a re-platform later.
Leasing depth + AI commentary
- Lead-to-lease pipeline (ResMan parity)
- Listings syndication (Zillow / Trulia / Hotpads)
- Floor plans + unit photo galleries
- Recurring transaction templates (utilities, recurring vendor)
- Bo writes the monthly variance memo automatically
- Multi-property roll-up reports
Multi-entity + native mobile
- Multi-entity consolidation (intercompany JEs, rolling P&L)
- Custom report builder (drag-drop columns, save / share)
- Native iOS + Android apps
- RUBS / utility billing
- Fixed assets register + depreciation schedules
- Lease abstraction at scale (Claude over PDF)
Compliance + commercial
- LIHTC / Section 8 compliance module — the big Yardi gap
- Construction accounting (dev tracking, draws, retainage)
- Commercial lease accounting (CAM, ASC 842)
- Owner waterfall distributions + capital calls
- Investment-management deal-level IRR
- Anomaly detection cron over the GL
Roadmap is directional, not contractual. Sequencing follows operator demand and integration partner readiness.
Be your books. Or feed them. Your call.
UnitBoard is a real double-entry general ledger — append-only journal, audit-ready, owner-distribution math built in. So it can be your books. It can also feed the books you already run at HQ.
Greenfield, smaller portfolios, or operators tired of paying $50K-$500K to Yardi.
One database, every workflow posts to the GL in the same transaction. AP invoice → journal entry. Rent payment → journal entry. Owner distribution → journal entry. No nightly sync, no reconciliation jobs, no third tool to keep aligned.
- Real double-entry GL with proper account types
- Append-only journal entries — auditable, not editable
- Multi-property + multi-entity on one Postgres
- P&L, balance sheet, cash flow, AR aging — computed from the ledger
- Owner distributions with management-fee math built in
Already running QuickBooks or Sage at HQ? Keep it. We post outbound.
Operators with existing corporate accounting don't need to migrate to adopt UnitBoard. Run UnitBoard at the property level for ops + AI. Journal postings sync outbound to your books on a schedule. Books reconcile automatically.
Bi-directional for chart of accounts and customers/vendors; one-way (UnitBoard → your GL) for journal entries.
Every PMS exports CSVs. Drop a rent roll, chart of accounts, vendor list, and 12 months of journal entries — Bo auto-maps every column. Direct API connectors land Q1-Q3 2026 sequenced by partnership accessibility (ResMan first, AppFolio second, Yardi last).
Real estate ERP, rebuilt for the AI era.
Not a bolt-on. Not an add-on. AI runs every workflow — invoice coding, resident replies, rent-roll queries, anomaly detection. Bring your own model.
Drop a PDF — Claude codes vendor, amount, property, GL account, posts the journal entry.
Ask Bo: "what is our portfolio NOI for the last 6 months?" — structured answer with tool calls in seconds.
Snappt-style screening on applicant paystubs, bank statements, IDs. Flags edits, font inconsistencies.
Point Claude at a PDF lease — pull start, end, rent, escalations, deposit, addenda automatically.
Continuous scan of the GL for unusual patterns — duplicate invoices, vendor drift, expense spikes.
Inbound resident message — Claude drafts the reply, your team approves and sends.
Ask the books anything.
Natural-language queries against a constrained, read-only ledger function. Tool-use under the hood. Schema and glossary prompt-cached, so answers come back in a second and cost pennies.
- Variance commentary that writes itself
- BYO-LLM — bring your own Anthropic / OpenAI / Gemini key
- Tool-use over typed schemas (no hallucinated columns)
- Hybrid intelligence — bot drafts, human approves
Default model: Anthropic Claude · BYO-LLM (OpenAI, Gemini, Bedrock) via OpenRouter · prompt-cached schema, sub-second responses
$ curl https://unitboard.ai/api/health
{
"ok": true,
"service": "unitboard",
"timestamp": "2026-04-29T19:14:02Z"
}
$ curl https://unitboard.ai/api/properties \
-H "Authorization: Bearer ${REXPROP_TOKEN}"
{
"data": [
{ "id": "...", "name": "The Rosedale",
"city": "Austin", "units": 200,
"occupancy": 0.945 }
]
}Whatever our UI does, your code can do too.
Every screen in UnitBoard is built on the same public REST API your team gets. No private endpoints, no separate “partner tier,” no $25K-per-integration tax that Yardi and AppFolio charge for the exact same thing. Build your own dashboards, wire in payments / maintenance / fraud / credit-reporting vendors directly, automate against your data. Bearer tokens, OpenAPI 3.1 spec, webhooks fire on every state change.
Browse the API16 modules. One unified database. One operating system for the property.
Every surface in the app shares the same data model and the same audit-grade GL underneath. No bolted-on add-ons. No second-system to reconcile.
Single source of truth
One Postgres database. Every lease post, work order, invoice approval writes to the GL in the same transaction. No reconciliation jobs. No duct tape.
Operator dashboard is the homepage
Occupancy, pre-lease, delinquency, AP aging, NOI, work-order SLA — at a glance. Click any tile, drill straight to the underlying lease, invoice, or journal entry.
AP that codes itself
Drop a PDF. Claude extracts vendor, amount, property, and GL code. You approve. Posts to the ledger. Cycle time drops 50%+ on day one.
AI in every workflow, not a sidebar
Natural-language queries on the books. Variance commentary that writes itself. Lease abstraction. Anomaly detection. Cached schema, cheap and fast.
Public API, no integration tolls
Every screen is a thin client of a documented REST API. Plug in payments, maintenance, fraud, credit reporting — pay zero per-integration fees.
Audit-grade by design
Append-only journal. Immutable posted entries. SOC-2-readable controls from day one. Tax, compliance, and reporting are first-class citizens.
Plugs into the tools you already run.
11 live · 13 in active build · the rest available via our public REST API + webhooks on every plan. No per-integration tolls — ever.
UnitBoard is one of the operating systems we’re building for real estate.
RexOS is a suite of vertical operating systems for real estate — every product built on the same foundation: a real ledger, an AI substrate, and a public API. UnitBoard is the multifamily one. Different products serve different parts of the stack — leasing, brokerage, residency, capital markets — and share the same architectural commitments under the hood.
See the wider thesis.
The full vision — every product in the suite, the architectural shared services, and how the pieces fit together. Why one ledger and one AI substrate, applied across verticals, beats stitching together a dozen point tools.
See it live. Then make it yours.
Real GL. Real AI. Real dispatch. Real public API. Every screen is clickable; none of it is a mockup. Free under 50 units — no card required.