The questions buyers ask, answered straight.
Collected from real evaluations by real technical teams: what works today, what doesn't yet, and what happens when you leave — before you sign anything.
What is AURI, in one line?
A resource-management engine wired to online booking and live KPIs, purpose-built for spa and wellness — for a flat monthly fee, with no commission on bookings. The full walkthrough is on the product page.
Who is behind AURI?
A founder-led engineering team based in Wrocław, Poland. You work directly with the people who build the system — the founder runs the intro calls himself. More on the founder page.
Is AURI a shared SaaS platform?
No — AURI is private SaaS. Every property runs its own single-tenant instance: separate database, separate application, your own domain and branding. That is an architecture decision, not a plan tier. Details on technology & security.
Can guests book from our website and social profiles?
Yes. You get a branded booking page guests use end to end — link it from your website's "Book now" button, your Instagram bio, or a QR code at the desk. Booking takes 60–90 seconds.
Do you store treatment notes, preferences and allergies?
Profiles, visit history, preferences and notes — yes. Health data such as allergies or medical conditions — deliberately no. That data is too sensitive to live in a booking database; if you need an intake questionnaire, we scope it as a separate, dedicated solution.
Does AURI handle staff scheduling and commissions?
Yes — shift schedules and leave per therapist, and commissions calculated per treatment. The exact commission logic is agreed at setup, around how your team actually works and is paid. More on SPA operations.
How much training does the front desk need?
Close to none, by design: reception books through the same flow the guest uses, so there is nothing extra to master. We run staff onboarding at launch.
Does it work on phones?
The guest booking flow is fully responsive. The staff calendar is a dense working interface built for desktop and tablet; the KPI dashboard works well on a phone. If your team needs to run the whole desk from phones, tell us on the call — we would rather be straight about this than surprise you.
We're outside the EU — will AURI fit our market?
That is the point of a dedicated instance: multi-currency pricing, local calendars, languages and payment methods are scoped per property rather than voted on by a thousand tenants. Your instance also runs in the region you choose — EU by default, Doha or Dammam for the Gulf, or the nearest suitable region elsewhere.
What if we need something AURI doesn't have?
We build it, or we say no honestly — inventory, packages, a local messaging channel. Each item is scoped and quoted before we build, so nothing is left half-built and nothing lands on your invoice unannounced.
Where does our data live?
On your own isolated instance — separate database, separate application — in the region you choose. You are the Data Controller; AURI is the Data Processor. The full picture is on technology & security.
Is our data pooled with other properties?
Never. There is no shared database for a bug to leak across — cross-client leakage is impossible by design, not by policy.
How is it secured?
Encrypted in transit and at rest, hashed credentials, role-based access, and an append-only audit log on every access to personal data. The engineering detail lives on the security page.
What about backups and uptime?
Automated daily backups with point-in-time recovery, 24/7 monitoring, and a 99.5% monthly uptime target. When something needs attention, you reach the people who built the system — not a ticket queue.
Can we export our data?
Anytime, in structured formats — during a pilot, under contract, or on the way out. No export fee, no lock-in.
How does pricing work?
One setup fee stands up your instance; one flat monthly fee keeps it hosted, maintained and supported. Never a commission on bookings. Full mechanics on the pricing page.
What does the monthly fee include?
Everything a live system needs: hosting on your dedicated infrastructure, 24/7 monitoring, daily backups, bug fixing, security patching, system updates, and working sessions with the team as the system evolves around your operation.
What costs extra?
Only work outside the agreed scope — a bespoke module, a one-off integration specific to how you operate. It is scoped and quoted before we build it. "No surprises" is the actual policy, not a slogan.
Is there a minimum contract length?
The founding-partner pilot is deliberately non-binding: free setup, one flat monthly fee, and either side can step away. After the pilot, we sit down at the review and agree terms together.
How fast do you respond when something breaks?
Critical issues — the system is unavailable — are handled the same business day. Non-critical issues within two to three business days. We commit to that standard honestly, as a focused team, rather than selling a penalty-backed SLA nobody could personally guarantee at three in the morning.
What happens if we want to leave?
You keep the system. Think of a carmaker: we keep the factory — the source code and the tooling — and you own the car: your instance, your infrastructure, your data. On exit we hand full access to you or whoever you nominate, and the system keeps running, frozen at that date. You give up the servicing, not the car.
Do we lose our data if we leave?
No. Your data is exported and handed back in full, in standard formats, and our copy is destroyed — with a signed certificate.
What if we part ways during a pilot?
The pilot build is free, so there is no handover of the system itself: the pilot environment is switched off, and your data is exported and returned. Nothing owed on either side — that is what makes it low-risk.
Can we get updates again later?
Yes. If you left with a frozen system and want it moved forward again, we agree that separately, on a paid basis. The door stays open.
Asked something we didn't cover? Book my intro call — you'll get the same straight answer, including "no" where the honest answer is no.