For hotel chains and multi-property operators
Pilot Two pilot slots open Q3 2026One number across every property. Five-minute refresh. Read-only by design.
AURI Aggregator pulls live KPIs from every property in your chain — revenue, RevPATH, no-show rate, utilization. Same dashboard for the CFO, the VP, the GM. No more spreadsheet mash-ups. No more PDFs that disagree by three percent.
30-minute call with Maciej. Written proposal within three business days.
Running multiple properties shouldn't feel like running multiple companies.
Three problems every multi-property leadership team knows by heart — and the cost of carrying them another quarter.
Numbers that disagree
Friday's PDF from Property A says $312k. Monday's reconciliation says $324k. The CFO spends two days finding which export ran on stale cache. Multiply by four properties and the monthly close becomes a part-time job no one budgeted.
Reactive, never preventive
A property goes offline at 9am Tuesday — you find out Wednesday. No-show rate doubles for three days — you see it in the monthly report. By then the booking pattern that caused it has already moved on.
No comparison without spreadsheets
You cannot tell at a glance which property is overperforming, which is underutilized, which has a cancellation spike. Comparison means opening four dashboards, exporting CSVs, and squinting at differently-formatted columns.
The consultation answers every seat at the table.
Chain decisions are rarely one signature. Each role asks a different question — Aggregator answers all four in the same demo.
Can I trust the number?
One source of truth. Read-only API. Audit log per change. The dashboard at HQ matches the export at the property. Reconciliation tax goes to zero.
Which property needs attention this week?
Side-by-side compare on the same KPIs. Five alert types — offline, cancellation spike, no-show climb, low utilization, rolling decline. The signal arrives in Slack, not in next month's report.
Can Aggregator break operational data?
No. Aggregator is a separate service in its own cloud project, with read-only HTTPS access over scoped API keys. It cannot write back. Security questionnaire, network diagram and pen-test plan on request.
Will HQ override my workflow?
No. Each property runs its own AURI instance — own database, own subdomain, own brand. Aggregator reads metrics, never edits bookings, services or schedules. The GM's daily tooling does not change.
One dashboard. Live data from every property.
Read-only by design. Five-minute refresh. Zero risk to your operational instances.
Aggregator pulls KPI snapshots from each property every five minutes. It never writes back — only reads. Your operations stay isolated. Your data sovereignty stays intact. The dashboard rolls up the metrics that matter for chain leadership: cross-property revenue, RevPATH (revenue per available therapist hour), yield, repeat-client rate, average lead time, hotel-versus-external mix.
Cross-property KPI rollup
Revenue, bookings, RevPATH, yield, repeat-client rate and average lead time aggregated across all properties. Period selector — week, month, quarter, year.
Five alert types
Property offline. Cancellation rate above threshold. No-show rate above threshold. Single-day low utilization. Rolling utilization decline.
Forecast with confidence rating
Thirty-day revenue projection with strong / moderate / weak confidence label. Recommendations flag dominant services and trend reversals before they become a quarter.
Compare two properties
Pick any two properties in your portfolio. Same KPIs, same period, side by side. Flagship versus new resort in one screen — boardroom-ready.
What the CFO sees on Monday morning.
Same snapshot the VP sees at the same time. Same numbers the GM exports at the property. One source of truth — refreshed every five minutes.
| Property | Revenue | Utilization | No-show | Status |
|---|---|---|---|---|
| Flagship — Warsaw | $72k | 78% | 4.1% | Healthy |
| Resort — Costa Brava | $68k | 71% | 5.8% | Healthy |
| City — Munich | $54k | 64% | 9.2% | No-show alert |
| Beach — Bali | $61k | 58% | 3.9% | Utilization drift |
Sandbox data shown for illustration. Your demo runs against a private four-property sandbox seeded with realistic numbers.
Each property: own database. Own cloud project. Own brand.
Most chain software pools every property into one database with a tenant ID column. One breach exposes the whole chain. AURI does the opposite.
- 01Single-tenant per property
Each property gets its own dedicated GCP project (staging and production separated), its own PostgreSQL database, its own subdomain. If one instance goes offline, the others keep running. If you sell a property, you spin its instance off intact.
- 02Aggregator is read-only
Aggregator pulls metrics over a scoped, read-only HTTPS API. It cannot write bookings, edit schedules or modify guest records. Architectural guarantee — not a permission flag your IT team has to verify.
- 03Audit log per change
Every operational mutation in every property writes to an immutable audit log — user, timestamp, before / after values. The CFO's reconciliation question becomes a query, not a forensic project.
spa.flagship-warsaw.com
own DB · own GCP project
spa.costa-brava.com
own DB · own GCP project
spa.munich.com
own DB · own GCP project
spa.bali-beach.com
own DB · own GCP project
The assets your evaluation needs.
Chain decisions involve three to five stakeholders. We send the artefacts each one expects, on request, before the proposal arrives.
Security one-pager
Architecture diagram, sub-processor list, data-residency map, breach-response plan. Designed for IT and InfoSec review.
Pricing PDF on request
Quote sized to your property count, integration depth and language coverage. Flat subscription per property. No per-booking commissions, ever.
Deployment timeline
Standard chain rollout: four to six weeks per property, three to six months staggered across the portfolio. We send the project plan before signature.
Reference call
On request after first conversation, we connect you with a current pilot operator for a candid call on what working with AURI is actually like.
Two pilot slots open for Q3 2026.
Pilot terms are partnership terms. We invest in your rollout; you invest case-study rights. The point is to ship something both sides want to talk about.
Implementation, included
- Free implementation across two to four properties — discovery, branding, data migration, staff training.
- Dedicated cloud project per property — own database, own backups, own subdomain.
- Direct-to-founder support during pilot — Maciej on Slack and WhatsApp, EU and GCC hours.
- Aggregator dashboard provisioned and tuned to your KPI hierarchy.
Case-study partnership
- Paid monthly subscription per property at standard chain pricing — no discount, no equity.
- Written case study with measured outcomes after 90 days of live operation.
- Logo rights on the AURI website and decks.
- One reference call per quarter with a serious chain prospect.
Pilot slots are not free software. They are the deal where AURI absorbs the rollout risk in exchange for permission to publish what worked.
Apply for a pilot slotWhat chain operators ask before they book the call.
Aggregator polls every five minutes. If a property is unreachable, the card shows offline and an alert fires after thirty minutes of silence. Other properties keep updating. Once the property comes back, the next poll picks up the latest snapshot.
Yes. Aggregator is a separate service in its own cloud project, with read-only HTTPS access to each property over scoped API keys. We send the security questionnaire, network diagram, sub-processor list and pen-test plan on request. The full security posture lives at /security/.
Add the property's URL and API key to the Aggregator configuration. Within one polling cycle, the new property appears in the dashboard, alerts and compare view. No downtime, no migration. Pricing scales linearly with property count — no surprise tier-jump.
Today the chain has single-password access with full visibility for everyone holding it. Per-role and per-property scoping is on the roadmap. We will tell you exactly where it sits before contract — never "coming soon" without a date.
No. Aggregator pulls from AURI specifically. To get a unified chain view, every property needs to be on AURI. We typically stagger migration property by property over three to six months — full plan on the pricing page and finalised on the consultation call.
Thirty minutes with the founder. Your portfolio walked end to end.
We configure a private demo on a sandbox showing four properties with realistic KPIs, walk through the metrics that matter for your portfolio, and answer the questions your CFO will ask before signature — pricing, data residency, sub-processor list, exit clause.
- Written proposal within three business days of the call.
- Security one-pager and sub-processor list sent on request before the call.
- No sales team. The call is with Maciej, the founder.
Talk to Maciej about your chain
Pick a slot or send a note — both routes reach the same inbox.
Two pilot slots open for Q3 2026.