Governed by design, from the database up
Access, approvals and activation are decided on the server and in the database. The interface shows what the platform allows; it never decides it.
Canonical business objects
Each business object has one owner, a lifecycle, validation rules and effective dating. Modules reference it; nothing keeps a private copy.
Tenant isolation in the database
Row-level security and server-validated access context decide what a session may read or write — not the user interface.
Duties, approvals and audit
Segregation of duties, four-eyes approval for sensitive acts and an audit record for each one. Privileged roles require step-up authentication.
Governed activation
Productive acts are switched on per tenant through one activation authority. It is off by default and fails closed when context is missing.
Separate environments
Development, quality assurance and production are separate landscapes. Every release is accepted in quality assurance with named roles before it reaches production.
Hosted in Europe
The platform runs on Microsoft Azure and a managed PostgreSQL database in European regions.
Architecture, security & governance
Canonical business objects, role- and duty-based access, four-eyes approvals, audit trails and tenant isolation enforced in the database.
- Tenant isolation through row-level security
- Step-up authentication for privileged roles
- Productive acts gated and fail-closed
Enterprise intelligence
A governed KPI catalogue with semantic definitions, built from canonical hotel facts instead of spreadsheet copies.
- One semantic definition per KPI
- Group reporting from hotel facts
- USALI-aligned departmental view