Otto sits alongside your stack — it doesn't replace it.
Property managers and billing companies already run on a constellation of systems — PMS for leases and rent, accounting for payables, submeters for reads, banks for payments. Otto integrates with the systems you already use, so the cycle stays connected to the rest of your operation.
Live today: Neptune · Stripe · Otto API · CSV/XLSX · PDF OCR. PMS connectors and meter platforms coming soon.
PMS integrations
Otto syncs property, unit, lease, and resident data with the PMS that already holds it. Two-way sync where it makes sense; one-way pulls where the PMS is the source of truth. None of the direct PMS connectors are live yet — every customer today onboards via CSV/XLSX, which is fast and reliable. Direct connectors land in the next release window.
Otto Pay rails
Otto Pay is powered by Stripe Connect — your property becomes the merchant of record, and funds settle direct to your bank. PayNearMe joins as the cash retail network when it ships.
Reads & vendor data
Neptune is live for submeter data. CSV/XLSX and PDF (via OCR) handle every other shape today. Direct connectors to NextCenturyMeters, Tapwatch, and Hex Reads — plus Urjanet for automated vendor bill retrieval — land in the next release window.
Accounting handoffs + the public API
Otto reconciles back to your accounting system at the property-cost level — and once the API ships, you can build whatever the standard connectors don't cover.
Otto is PMS-agnostic by design.
Most utility billing tools assume one operator runs one PMS. Billing companies don't work that way — every client may run something different. Otto's data model is property-first; the PMS connector is the layer underneath, configurable per client.
Each property in your portfolio can sync from a different PMS — Buildium for client A, AppFolio for client B, CSV for client C.
Otto doesn't ask your clients to switch software. We meet their stack where it is and surface the data Otto needs.
For PMS platforms with no API or that aren't yet integrated, the spreadsheet path is fully supported — not a fallback.
Don't see your system? Tell us.
Integration prioritization is shaped almost entirely by Founder Partner footprint. If your client portfolio runs on a PMS we haven't built yet, that's exactly the input that moves it up the queue. Tell us what you use — and what your clients use — and we'll be specific about timeline.
The cycle, connected to your stack.
30-minute demo. We'll talk through your current systems and map exactly what would sync where — Buildium today, the rest as we land them.
Integrations are part of Otto Billing — no separate per-unit cost.