Record layer
Clients, appointments, services, staff, products, payments and orders held once, so every part of the system reads the same fact.
Platform architecture
How Voltalyze BOS is put together.
A short, honest description of the structure behind the product, for the people who want to understand it before they commit their business to it.
Five layers
- Record layer
- Workflow layer
- Interface layer
- Integration layer
- Control layer
Structure
Five layers, one system
Separating records from workflows from interfaces is what allows the same booking to appear correctly on the front desk screen, on the client's confirmation and in the owner's report.
Workflow layer
The rules that move work along: deposits, reminders, waitlists, stock deduction, commission, approvals and review requests.
Interface layer
The screens each role uses, from the front desk calendar to the owner's reporting, plus the customer-facing website and booking pages.
Integration layer
The connections out: payment provider, domain, messaging and the other services a business already relies on.
Control layer
Roles, permissions, approvals, history and export, so the business decides who can do what and can prove what happened.
Deployment
A configured deployment, not a shared spreadsheet
Each business runs its own Voltalyze BOS deployment, configured to its services, staff, locations and policies. Your configuration is yours, and changing it does not depend on other customers.
- Per-business configuration
- Customer-facing pages served by the same system
- Your own payment connection
- Role-based access within the business
- Data export available
- Supported changes as the business changes
Per business
- Configuration
- Branding
- Domain
- Payment connection
- Users and roles
AI
Where AI sits in the structure
Both AI layers read from the record layer and act through the same permissions as a person. They are not a separate system with their own database or their own rights.
- AI Concierge on the interface layer, facing customers
- BOS Assistant on the interface layer, facing staff
- Both read the same records
- Permissions enforced by the control layer
- Supported actions only
- Sensitive actions stay with a person
Guardrails
- Role permissions
- Supported action list
- Protected actions
- History where available
FAQ
Architecture questions
Is this a template of a generic product?
No. Voltalyze BOS is built for beauty and wellness operations, and each deployment is configured for that business.
Can it be extended for us?
Custom work is possible as a separately scoped service rather than as part of the standard plan.
What happens when the product is updated?
Improvements reach your deployment as part of the service. Your configuration and data are not reset.
Can it integrate with tools we already use?
Supported integrations are confirmed at the demo. Anything outside that list is scoped separately.
Want the technical detail in person?
Book a demo and ask the structural questions directly.