The property intelligence platform
Serious infrastructure underneath. Every claim marked.
This page is the platform as it is, not as a brochure would like it. Each capability says whether it runs in production today, needs a person, is proposed for the property vertical, or depends on your system of record.
How it is built.
Stack: Next.js, TypeScript, Supabase, Vercel, OpenAI, Twilio, Google and Microsoft workspace APIs. No low-code glue in the production path.
What exists, what is proposed.
Leasing
| Capability | What it does | Status |
|---|---|---|
| Inquiry capture on web, text, email and WhatsApp | Every inquiry lands in one record with its source, the questions asked and the answers given. | Runs today |
| Answers in under a minute, around the clock | The assistant answers from your listings and your own knowledge base, identifies itself as automated, and hands over to a person on request. | Runs today |
| Qualification with a readable reason | Move-in date, unit type, budget and documents gathered; each inquiry rated 0 to 100 with the rule that produced it. | Runs today |
| Viewings booked into a real calendar, reminded, rebooked | Google, Microsoft or iCloud calendars. Reminders, reschedules, no-show recovery. | Runs today |
| Viewing slots per unit and group viewings | Booking capacity is per business today, not per unit. Group viewings with personal invite links exist for events and would be lifted into leasing. | Proposed for property |
| Rental application with private documents | Intake plus private, signed-URL uploads. Documents are never public and never used for training. A person decides the application. | Proposed for property |
| Follow-up until a viewing is held or the prospect says no | Consent recorded, send windows respected, unsubscribe honoured on every channel. | Runs today |
| Campaigns traced to inquiries and viewings | Meta and Google spend, cost per inquiry, source on every lead and appointment. | Runs today |
Residents and maintenance
| Capability | What it does | Status |
|---|---|---|
| Resident questions answered from your policies | The same assistant, on the building's own number and email, grounded in your documents. | Runs today |
| Maintenance intake with photos and urgency | Unit, issue, photos and urgency collected. Flood, gas, fire, no heat recognised first and paged to your on-call contact in the same turn. | Proposed for property |
| Named approval before any contractor is contacted | A person on your team approves, asks for more, or declines. The decision is written to the audit log with their name. | Your team decides |
| Work orders with a confirmation link and a chase | The vendor receives the job sheet; no reply within the window brings it back to your desk. The resident is kept informed. | Proposed for property |
| Renewal drafts 90 and 60 days out, sent after review | Needs a tenancy record. Nothing stores a lease today. | Proposed for property |
| Rent collection, arrears, occupancy | These live in your property management system. ORACA reads them where an API or export allows and never estimates them. | With your system of record |
Operations and reporting
| Capability | What it does | Status |
|---|---|---|
| The morning screen: what needs a decision today | Sorted by what it costs to ignore. Six of seven card types run on real rows. | Runs today |
| Inquiry to viewing funnel, response times, open requests | Every rate prints its denominator. A figure without data renders as not enough data yet, never as zero. | Runs today |
| Portfolio roll-up with property-level permissions | The group view exists for the agency console. Property-level roles for leasing teams and owners are new. | Proposed for property |
| Build and lease-up desk: stages, waiting-on, stalled alerts | Runs today for a design practice. Vocabulary comes from config, so a development is a project with different stage names. | Runs today |
| Sync with Yardi, AppFolio, Buildium, Rent Manager, Entrata | By open API where one exists (Buildium), by partner programme where required (Yardi, AppFolio, Rent Manager, Entrata), by structured handoff where there is no API (Propra). | With your system of record |
Trust and access
| Capability | What it does | Status |
|---|---|---|
| A separate database per client | Row-level security on every table and a three-query leak sweep on every change. | Runs today |
| Personal data encrypted at rest | Names, emails, phones and addresses are encrypted in the database. | Runs today |
| Every automated decision in an append-only log | What was decided, for whom, and why. Exportable on request. | Runs today |
| Outbound fails closed without consent | No recorded consent, nothing sends. Stop means stop on every channel. | Runs today |
| A compliance check on every outgoing reply | A deterministic check refuses to send a reply that breaks a rule you set, whatever the model wrote. | Runs today |
| People decide on people | The system organises an application; your team decides it against criteria reviewed for human rights compliance. Qualification rules exclude protected grounds. | Your team decides |
| Certifications | ORACA describes its controls and does not claim SOC 2, ISO 27001 or other audited certifications. Data residency is confirmed per deployment. | With your system of record |
Systems of record, and how ORACA connects to each.
| System | Access model | What ORACA can do |
|---|---|---|
| Buildium | Open REST API, per-account keys. Units, leads, tasks and work orders are documented. | Direct integration, no commercial agreement needed |
| Yardi Voyager and Breeze | Standard Interface Partnership Program with hundreds of certified interfaces. Access by agreement. | Partner programme, or through an interface the client already licenses |
| AppFolio | AppFolio Stack marketplace. API access through partnership. | Partner programme. Export and inbound email until then |
| Rent Manager | Integrations Program with 200 or more providers. REST API for approved partners. | Partner application |
| Entrata | Partner API by agreement. | Partner application |
| Propra | No public API found. | Structured handoff: summary email and export, no live sync |
| Google and Microsoft calendars, Gmail and Outlook | OAuth, in production for ORACA clients today. | Runs today |
| Twilio text and voice, WhatsApp through Meta | In production for ORACA clients today. | Runs today |
| Meta and Google campaigns | Spend and lead sync in production today. | Runs today |
Why the layer is worth having even when you already run one of these: a system of record is built to hold the truth, not to answer a message at 9:40 pm, chase a vendor on Thursday or tell you on Tuesday what needs you. ORACA does that work and writes the outcome back to the record you keep.
Phased, beside your systems, never a rip-out.
- 1Discovery and portfolio assessment
Your properties, channels, systems and the hours that disappear into interruptions. A written map of what runs on day one and what needs building.
- 2Pilot on one property: the leasing desk
Live in 21 days or the setup fee is refunded. Inquiries, qualification, viewings, follow-up, the morning screen. Measured from a declared start date.
- 3Resident and maintenance desk
Once named approval roles are in place. Intake, triage, approvals, work orders, resolution reporting.
- 4Portfolio and integration
Roll-up with property-level permissions, and sync with the system of record by whichever route it allows.
Pilot outcomes are counted from rows, never modelled: inquiries captured, median first reply, viewings booked and held, requests approved and resolved, time from report to approval. A figure without data behind it renders as not enough data yet.
See the product rather than read about it.