Live
Has a migration and an endpoint.
The data lives in Postgres and survives the browser, the device and the session. This is the only column that means you can rely on it.
Roadmap
The line, drawn in public.
YellowUnit is in early access, which means part of it runs on a database today and part of it does not. Publishing a roadmap that blurs the two would buy a demo and lose the customer. So here is exactly which is which.
264
Capabilities modeled
173
State machines
861
Transitions defined
35
Migrations shipped
How to read this
Three states, and one objective test.
Deciding what counts as done is where most roadmaps start lying. Ours has a question with a yes or no answer: is there a database table and an endpoint behind it? If not, it does not get to sit in the first column.
In build
The workflow runs, persistence is moving.
The rules, states and screens exist and work. What is still moving is where the data rests. Honest to call it built; dishonest to call it finished.
Modeled
Specified, not yet built.
Written into the frozen model with its states, transitions and authority rules, waiting its turn in the queue. Designed is not the same as available.
Live today
Running on a database, right now.
Nine areas with tables, endpoints and real third-party integrations behind them. If you start today, this is what actually holds your data.
Live
Accounts and sign-in
One-time-code sign-in, Google account linking, and one account that carries every role you hold instead of one login per role.
Live
Invitations
Owner, manager, tenant and vendor invites with a token and a verification code. An invite adds a role to an existing account rather than forcing a duplicate.
Live
Properties
The permanent property record, photos, record updates and address-verified timezone, with relationships that end without deleting anything.
Live
Applications
Versioned rental criteria, versioned submissions, manager and owner review actions, and delivery evidence for the decision that was sent.
Live
Screening
The screening fee charged through Stripe against the listing, staying tied to the application it paid for.
Live
Move-in inspections
The move-in inspection and its checklist, persisted against the unit so the deposit conversation later is a matter of record.
Live
Scheduling
Property appointments and arrival windows, synced with Google Calendar so the plan exists where the work is actually planned.
Live
Work orders
Service awards, the vendor commercial chain, and completion evidence photographed on site and filed against the property.
Live
Payouts
Stripe Connect accounts, onboarding and rent readiness, so money movement carries the same record as the work behind it.
In build
Built, and moving onto the database.
These are not slides. The workflows run, the state machines are defined and the authority rules are enforced — what is still in flight is the persistence layer underneath them. We would rather show you a working prototype and say so than call it live.
In build
Messaging and notifications
Conversations scoped to a property, delivery preferences and digests. The rules that keep a chat from ever standing in for an official notice are already written.
In build
Documents and e-sign
Document versions, immutability once signed, consent to electronic records, and the evidence package behind an executed envelope.
In build
Official notices
Legal delivery, attempts, and the deadlines that nothing is allowed to silently pause. The hardest part of the model, and the one worth getting exactly right.
In build
Rent, charges and deposits
Charge schedules, autopay, late-fee rules that require real authority, held amounts and deposit claims.
In build
Owner statements and accounting
Statement versions, delivery, management compensation, and sync with outside accounting systems.
In build
Subscription and billing
The plan version that already prices this site, plus billable property months, grace, delinquency and responsibility transfer between payers.
In build
Listings and leads
Listing versions, publication periods, prospects, showings and match suggestions feeding the application flow.
In build
Vendor marketplace
Vendor company registration, profile versions, marketplace participation, trusted relationships and opportunity invitations.
In build
Ownership and management transfers
Co-ownership, legal ownership profiles, ownership claims, management relationships and the handoff of a primary representative.
In build
History and evidence export
Filtered history reports, evidence packages of source files, and prepared downloads that expire without ever deleting the record.
In build
Platform administration
Support cases, security incidents, privacy requests, preservation holds and the governance around sensitive capabilities.
Modeled
The part written before it is needed.
Nine areas live and eleven in build do not add up to 264 capabilities. The rest is the reserve: rules written for situations a customer meets rarely, and that have to already exist on the day one of them arrives. They have states, transitions and authority rules in the frozen model, and no screen yet.
Modeled
Record retention and disposition
When a record may be disposed of, who may decide it, and what a preservation hold does to that decision. Written now because retention rules are not something to invent under legal pressure.
Modeled
Continuity and direction
What happens to a workspace when the person holding authority becomes unavailable, and how a designated continuity contact is changed without opening a side door into ownership.
Modeled
Condominium coordination
Common-area notices and forwarding between a syndic contact and the units affected, so a building-wide problem does not arrive as twelve separate tenant reports.
The order
The loop that repeats goes first.
A property does not need every feature on day one. It needs the loop that happens over and over: a unit gets listed, someone applies, someone is screened, someone moves in, something breaks, a vendor fixes it, money moves, and the record keeps all of it.
That loop is the part that is live. Everything else — statements, accounting sync, the marketplace, e-sign — matters, and it is built on the same record rather than bolted beside it. Which is exactly why it is worth waiting for instead of shipping twice.
What early access means
You are early, and it shows.
You will meet a workflow that is still a prototype. We will tell you which one before you hit it, not after.
Your record is not the experiment.
The property, its history and its documents are the part we treat as permanent from day one.
The price is the launch price.
A later plan version applies going forward and never rewrites an invoice you already received.
You can leave with everything.
History reports and evidence packages are part of the product, not a retention lever.
Early access
Come in while it is being built.
Early access shapes what moves up the list. The loop is live today, and one property is enough to start.