Hotel spa software where the hotel keeps the data, the brand, and 100% of the revenue.
AURI is a single-tenant hotel spa system. Your own Google Cloud project, your own database, your own domain. Subscription pricing — zero booking commissions, ever.
Built by a Polish engineering team focused only on hotel spa operations. Every architectural choice — private deployment per property, triple-resource validation at the database layer, charge-to-room native to four PMS adapters — exists to answer one question: why does a 200-room hotel hand a 10% take rate to a booking platform that competes with it?
Hotel spas leak revenue through three structural problems no booking-platform vendor will fix — because the leak is their business model.
- 01Commission engines skim the P&L.
A 10–20% take rate on a $1.4M spa department is $144K a year leaving the hotel ledger. Auri is subscription-only — never per booking.
- 02Multi-tenant SaaS sits on infrastructure hotels can't audit.
Guest medical histories on shared databases are a non-starter under PDPL, GDPR Art. 9, and any luxury brand standard. Auri ships a dedicated GCP project per property.
- 03Day-spa software breaks at hotel scale.
No room-folio billing, no PMS link, no Hotel Mode, no Arabic RTL — silent failure at the worst time. Auri was built for hotel spas first, not adapted from a hair-salon codebase.
Auri is the direct answer to all three. Private deployment per property. Triple-resource booking validation enforced at the Postgres row-lock level. Charge-to-room native to the PMS adapters hotels already run on.
Multi-segment, multi-region, open ecosystem — single-tenant stays the default.
Multi-segment by 2027: luxury hotels, regional chains, medical spas, day spas, wellness retreats. Multi-region by 2028: GCC, Europe, Southeast Asia, North Africa. Open ecosystem: public REST API, OpenAPI 3.1 spec at /api/docs, adapter contracts for every major PMS in the market.
The constant: private deployment per property stays the default. Hotels own their infrastructure. Auri earns subscription, never commission. The booking platforms compete with the hotels they serve — we refuse to.
Single-tenant managed software — not a classic SaaS
Most hotel software vendors run shared multi-tenant clouds and bill a flat subscription. Auri does the opposite: every property gets its own dedicated Google Cloud project, its own PostgreSQL database, and its own domain. We operate the entire stack. The pricing reflects it — setup fee for implementation plus a monthly subscription for the managed service.
| Dimension | Classic SaaS | Auri |
|---|---|---|
Infrastructure
| Shared multi-tenant cloud across all customers | Dedicated Google Cloud project per property |
Database isolation
| Single shared database, logical separation by tenant_id | Own PostgreSQL instance per property — physical isolation |
Compliance and data residency
| Vendor-wide certifications, region chosen by vendor | Your own DPA, region selected for GDPR / UAE PDPL / KSA PDPL |
Pricing model
| Subscription only — monthly or annual | Hybrid — setup fee for implementation plus monthly subscription |
Customisation
| Standardised for all tenants — limited by shared instance | Property-specific integrations and configuration possible |
Auri is single-tenant managed software for hospitality. Each hotel gets a dedicated cloud environment we fully operate. Closer to Workday Private Cloud than to Salesforce.
Four things competitors structurally cannot offer.
Your guest data never sits next to another hotel's.
Every AURI client gets dedicated, isolated Google Cloud projects — staging and production, fully separated. Competitors say 'isolation' and mean row-level filters in a shared database. AURI means a literal GCP project per client: own database, own domain, own branding, own backups, own keys. Zero risk of a shared-platform outage taking your spa offline. Zero risk of a noisy-neighbour query degrading your booking page on a Friday night. Auditors see one tenant per environment — which is what GDPR Art. 32, UAE PDPL, and ISO 27001 reviewers actually ask for.
Zero double-bookings — enforced in the database, not the UI.
Therapist, room, and equipment validated atomically in one Postgres transaction with FOR UPDATE locks per resource. Most spa software runs sequential checks (therapist OK → room OK → equipment OK → write) and silently races under load — that is where the 'we accidentally double-booked the suite' calls come from. AURI cannot. Load-tested at 1000 req/s on the booking endpoint with zero collisions. Documented at services/core/src/internal/repo/repo_bookings_tx.go — verifiable engineering, not a marketing claim.
Arabic-native — built for the GCC, not translated for it.
Arabic ships full RTL layout (992-line ar.yaml), Hijri calendar treatment scheduling, GCC payment rails (Tap Payments for AED/SAR), and a demo tenant deployed in me-central1 (Doha) so MENA properties pass data-residency review. English, Polish, German default alongside. Translation infrastructure (i18n YAML, hreflang, sitemap, RTL CSS) was built before the first feature shipped — not retrofitted after a Gulf customer asked for it.
Engineered like the systems that move money, not like a side project.
200+ automated tests cover booking lifecycle, payments, PMS adapters, and aggregator analytics. Functions capped at 60 lines. Files capped at 300. NASA-style bounded complexity. Audit logs on every admin mutation by default. Built with the discipline of a senior engineer who has shipped production systems in finance, logistics, and consumer software for ten years — not the velocity of a 50-person startup chasing the next round.
Built by one engineer focused on hotel spa operations
Auri is founded by Maciej Adamski, a Polish engineer with ten years of production systems behind him across finance, logistics, and consumer software. After watching commission platforms and shared-tenant SaaS quietly bleed hotel spa P&Ls, he decided to build the system operations directors would commission themselves if they had a senior engineering team on retainer.
Every architectural decision lives close to the user: triple-resource validation at the database layer, single-tenant deployments per property, audit logs by default, PMS adapters that speak the languages hotels actually run on. No commissions, no shared infrastructure, no per-booking tax.
The founder story covers why Auri exists, how the engineering principles were chosen, and what the next two years look like.
Onboarded vendor on ExploreTech UAE
ExploreTech is a UAE government-backed platform for hospitality technology serving the Gulf market. Auri passed the platform's technical review covering data security, deployment model, and PMS integration coverage — onboarded since March 2026. The listing gives UAE 4-5 star hotel operators a direct, locally-supported route to Auri.
See the ExploreTech profileWired into the PMS hotels already run on
Three adapters production-ready, two in active development. Direct guest lookup, charge-to-room posting, and check-in verification — no spreadsheets, no manual sync.
Mews
Production-readyOpera Cloud
Production-readyPrevio
Production-readyCloudbeds
Phase 2 — integration wiringRoomRaccoon
Beta — code completePublic REST API
Production-readyProduction-ready: Mews, Oracle Opera Cloud, Previo. Phase 2: Cloudbeds (adapter shipped, integration wiring in progress). Beta: RoomRaccoon (adapter code-complete). The public REST API and OpenAPI 3.1 spec at /api/docs let any other PMS or in-house system integrate with Auri on either side.
Watch AURI run on your property — before you sign anything.
30-minute private briefing with the founder. We pre-deploy a tenant on Google Cloud with your logo, colours, and domain — you watch a real guest journey end to end. No slides, no SDR, no commitment.
- Pre-deployed tenant on your branding and domain
- Live capture-rate and RevPATH model on your numbers
- No commitment, no commission, no sales pressure