ORACA Hive

One screen for the whole portfolio, read and dated.

Hive is the overview layer of ORACA Property OS: the morning screen for a property company's owners and managers. It reads the same records the desks write, so every figure names its table, its denominator and when it was last read. Blank means absent, never zero. Nothing on it is estimated.

Four bands, by importanceDecide now, Portfolio, Operations, Audit. Each panel says whether it runs today, needs wiring, or needs a table that does not exist yet.

What the screen shows.

Decide now

Three things that need a person this morning: approvals that have waited too long, renewals inside the notice window, an urgent request nobody has acknowledged. Each card names its source and when it was last read.

Approvals read real rows today. Renewals and maintenance need their tables. Partly live

Portfolio

Where the buildings are and how each one is doing: occupancy, vacancies over 30 days, the leasing funnel from inquiry to signed tenancy, renewals due.

The funnel reads real inquiries and viewings today. Occupancy, the map and the building cards need properties and units. Needs a table

Operations

The agents, what each one is responsible for, and what it cost: runs, outcomes, items waiting for a person. Integration health with a stored check time.

The run ledger exists and is read today. Cost per run is not captured yet. Partly live

Audit

Who decided what, when, with what information. Append-only, exportable, a name on every approval.

Runs today. Runs today

Who sees itOwners and executives see the whole portfolio. A property manager sees their buildings. A leasing team sees its own inquiries. A vendor sees one job sheet and nothing else.

The right people, the right property.

Hive lives inside the same system and database as Property OS. Every Hive figure is read from a Property OS record, and every Hive action is the same Property OS action. Nothing is copied between them, so the two can never disagree.

Named logins with property-level scope are built with the first property client. Until then Hive runs for ORACA’s own operators behind the existing operator gate, reading ORACA’s own inquiries, viewings, agent runs and audit log, with every portfolio panel marked as needing its table.

What is real todayCounted from rows, never modelled. The build order is written down and short.

Live, wired next, built next.

PanelReadsToday
Inquiries and viewingsThe inquiry record and the viewing calendarRuns today
Approvals waitingThe outbound review queue; approving never sends on its ownRuns today
Agent runsThe run ledger: observed, decided, acted, blocked, failedRuns today
Audit logAppend-only decisions with a name and a timeRuns today
RenewalsTenancy and renewal review records; notice and cap rules are in codeNeeds wiring
Agent costToken counts per run, priced from a rate tableNeeds wiring
Occupancy, map, buildingsProperties and unitsNeeds a table
MaintenanceRequests, work orders, contractors, a named approverNeeds a table
Rent and arrearsYour system of record, read where it allows, never estimatedYour record

Hive comes with Property OS. See the desks underneath it, the published prices, or book a call.

Book a callORACA Property OSSee pricing