Aura Solo
Available nowOne independent provider or a small personal practice
A low-administration practitioner workflow: a booking page, client records, reminders and a clean upgrade path to Salon.
Operations platform for beauty & wellness
One core.Four product lines.
Aura Lattice turns multilingual demand into reliable bookings, tenant-owned operations and governed automation — one shared platform, activated country by country.
- Aura Sololive
- Aura Salonlive
- Aura Medicalstaged
- Aura Academystaged
In production now as the Victoria Beauty pilot, Thailand — the first deployment profile, not the market boundary.
Bookings today—
Median reply—
No-show rate—
sample tenanttenant-scoped
01 Product lines
Buy the job you have. Add the next one when you need it.
Product lines are versioned bundles over shared tenancy, booking, communications, billing and audit primitives — not four separate apps. Aura Solo and Aura Salon are in the commercial runtime today; Aura Medical and Aura Academy are staged, each behind its own readiness and release gate.
Aura Salon
Available nowOwners, teams and multi-location operators
Staff, branches, resources, inventory, POS, finance and reporting with explicit tenant and branch ownership across every record.
Aura Medical
StagedClinics running controlled clinical operations
A separate clinical bounded context — encounter, intake, consent, protocol sign-off and restricted export — behind an intended-use and regional compliance gate.
Aura Academy
StagedTeams building internal skill and quality
Course versions, cohorts, progress and certificates, connected to Salon and Medical permissions. Starts as an internal add-on before any standalone LMS.
02 Demand to operations
The loop, kept in one data model
Public site, messaging and booking are not add-ons bolted onto a calendar. They share one data model, so a question in any language ends as a confirmed slot with an owner.
Capture
Domain-aware tenant sites and Telegram / web-widget bots meet demand in the visitor’s language, tied to the live catalog.
Book
Structured requests resolve against real availability, branch scope, deposits and cancellation policy — idempotent and version-checked.
Operate
Managers work the schedule, clients, services, inventory, POS and reports from one tenant-scoped console.
Follow up
Reminders, aftercare and review requests run as governed automation — drafted for a person to approve, never sent blind.
03 What stays yours
Tenant-owned, not tenant-trapped
Data placement, site hosting and communication providers are independent decisions. Failure never falls back to another tenant or an Aura-owned account.
Full tenant export
Services, clients, bookings, messages and media leave with you in a portable form, on demand — not a support ticket.
Database placement
Choose the region and hosting model for the tenant database as a first-class setting, with explicit cost and recovery ownership.
Site hosting
Publish the tenant site on your own domain and hosting, or on an Aura subdomain — the two are decoupled.
Your provider accounts
Connect your own WhatsApp, Telegram, email and payment providers. Billing goes to you, not through an Aura markup.
Clean offboarding
Migration, rollback and deletion responsibilities are stated before activation, not discovered at the exit.
04 Governed automation
AI that a regulator and an owner can both live with
Automation is a set of governed building blocks, not an ungoverned chatbot. The canonical contract lives in tenant settings and every exposed field is enforced.
Approvals before client contact
Suggested replies, review responses and aftercare cards require human approval before anything reaches a client.
Scoped data and field ACLs
Models see only the tenant and branch data a use case allows. Clinical summarization is local-only and fail-closed, with no generic provider fallback.
Budgets, logs and a kill switch
Every tool call is metered and audited. A disabled governance level is a hard block on client-facing replies.
05 International by design
One platform, regional policy profiles
The core carries no per-country branches. Language, currency, tax, channels, data residency and compliance live in versioned regional profiles and policy adapters, activated when local evidence is ready.
Aura Lattice global coreShared tenancy, booking, communications, billing, audit
- SEA / Thailand pilot
- Latin America
- Middle East / GCC
- USA
- Canada
- Europe / UK
- Australia / NZ
- CIS country profiles
- Europe / UK
GDPR / UK GDPR, health-data classification, transfers, VAT, country hosting options.
- USA / Canada
HIPAA where applicable with a BAA, state and provincial privacy, local payments and contracting.
- Latin America
Spanish and Portuguese content, WhatsApp, local acquiring and tax, Brazil LGPD.
- CIS profiles
Russian plus local languages, local payments and POS, Telegram and WhatsApp, per-country data profiles.
06 Capabilities
Grouped the way an operator actually works
Available now in Aura Solo and Aura Salon:
Front desk & booking
- Public booking with availability tokens, deposits and cancellation windows
- Custom calendar: day / week / month / agenda, drag reschedule, conflict checks
- Waitlist, reminders and signed self-service manage links
- Omnichannel inbox: Telegram, web widget, WhatsApp, email
Clients, catalog & marketing
- CRM with identities, consents, activities, loyalty and a client profile view
- Tenant-owned service categories with localized descriptions and media
- Multilingual catalog, team profiles, gallery and reviews
- Campaigns, promotions, gift certificates and client entitlements
Team, finance & operations
- Branches, resources, masters, schedules and cross-branch capability rules
- POS, transactions, inventory ledger and reporting
- Role, membership and entitlement-based access with audit logs
- Honest loading, empty, error and permission states on every screen
07 Managed activation
Launched in days, by people who have done it
Implementation is a paid, managed step — not a self-serve import you are left to figure out.
- 01
Import
Services, prices, staff, branches and client history come in from your current tool or spreadsheets.
- 02
Configure
Locales, channels, policy profile, deposits, roles and the tenant site are set up against your operation.
- 03
Go live
Bookings, bots and reminders switch on with measurable activation steps and a named contact.
08 Flagship tenant
Victoria Beauty — one tenant, in the open
Victoria Beauty runs on Aura Lattice in Thailand across RU / EN / TH. We show it as a live operating environment, and we are precise about what a pilot does and does not prove.
What the pilot proves
A real multilingual operation running the core loop — booking, client, visit, aftercare, repeat booking — on tenant-scoped data with governed automation.
What it does not prove
Independent paid retention, repeatable sales, or global product-market fit. Those need separate evidence, country by country.
tenant/victoria-beauty LivePrimary site
vbkpg.comAura subdomain
vbkpg.auralattice.comLocales
ru · en · thIsolation
tenant + branch scoped09 Who it fits
Built for a specific, high-friction operator
ScaleOne to ten premium locations, 5–50 service providers.
DemandBookings arrive by web, Instagram, WhatsApp, Telegram, LINE and phone.
LanguagesMultiple operating languages and a material tourist or expat client share.
PainOwner-visible leakage from slow replies, no-shows and fragmented client history.
IntentWilling to pay for implementation and a branded experience, not only a free calendar.
Not a fitA single free-calendar solo user with one language and no implementation need.
10 Pricing
Per product line, composable
You pay for the product lines you run plus a paid, managed activation. Locations, providers and your regional profile set the number. There is no free marketplace tier that resells your clients.
- Aura Solo and Aura Salon are the two commercial lines today; add a line as an entitlement change, not a migration.
- Implementation is a fixed, scoped engagement — import, configuration and go-live.
- Your own payment, WhatsApp and Telegram provider accounts are billed to you directly, with no Aura markup.
11 Questions
Straight answers
Do we own our data?
Yes. The tenant owns its records and can export the full dataset on demand. Database placement and site hosting are your decisions, and there is no silent fallback to a shared Aura account.
Can we start with one product line and add another later?
Yes. Product lines compose over one tenant and one data model. Aura Solo and Aura Salon are available now; adding a line is an entitlement change, not a migration.
When are Aura Medical and Aura Academy available?
They are staged. Aura Medical needs an intended-use decision, regional compliance and clinical-audit evidence per country. Aura Academy begins as an internal add-on to Salon and Medical before any standalone offering.
Which countries can we run in today?
The first deployment profile is Thailand, via the Victoria Beauty pilot. Other country profiles activate when local payments, language, support and legal evidence are complete — the target map covers Latin America, SEA, the GCC, the US, Canada, Europe/UK, Australia/NZ and CIS profiles.
How does automation stay safe?
AI and bots run inside per-tenant budgets, approval gates and scoped data. Client-facing replies require human approval, clinical summarization is local-only and fail-closed, and a disabled governance level hard-blocks outbound automation.
How does pricing work?
Pricing is per product line and composable, with implementation as a paid, managed activation. Book a demo for a quote against your locations, providers and country profile.
See it against your own operation
A working demo on real workflows — booking, masters, branches, catalog, messages — not a slideshow. Bring your languages, channels and locations.