FLATWHITE AI · HOSPITALITY AUTOMATION & INTELLIGENCE

Thoughtful. Down to the details.

A reference architecture for individually developed hotel solutions. With source provenance, scoped permissions and control before critical actions.

ARCHITECTURE WITH RESPONSIBILITY

Make connections.
Keep control.

A possible architecture for your hotel. From permitted access to a traceable action, every step has a purpose, a boundary and a responsible role.

Reference architecture for potential client solutions. The website demo uses fictional data only and is not connected to hotel software.

01Authorised sourcesAPI · webhook · approved export

Connect only sources explicitly approved by the hotel and the provider.

Reads
Defined reservation fields, operational events and approved documents.
Writes
No source-system changes at this stage.
Control
Customer approval, minimal API scopes, test access and a documented data boundary.
02Adapters & data qualityValidate · normalise · reconcile

Turn different formats into a consistent, understandable hotel data model.

Reads
Permitted source events with provenance, timestamps, time zones and currencies.
Writes
Validated internal events and quality flags; no arbitrary KPI definitions.
Control
Schema checks, source provenance, duplicate detection and visible data gaps.
03Permissions & trust boundaryRoles · tenants · data minimisation

Check who may see and use each piece of data before further processing.

Reads
Roles, permitted purposes, tenant membership and necessary consent information.
Writes
A narrowly scoped view of the context permitted for the current role.
Control
Deny access when permission is missing. Front office cannot retrieve unrelated HR or finance documents.
04Knowledge, metrics & skillsRAG · citations · reusable skills

Prepare tasks using approved knowledge and clearly defined metrics.

Reads
Only current, approved document versions visible to the role, plus validated data.
Writes
Sourced drafts and structured proposals instead of unsupported commitments.
Control
ACL-filtered retrieval, citation IDs, document and prompt versions, quality evaluation and handover for conflicting sources.
05Controlled workflowsPermitted tools · states · duplicate prevention

Break an agreed plan into individual, reviewable steps.

Reads
Authorised task context, state and permitted skill definitions.
Writes
Task drafts and requests only to explicitly allowlisted tools.
Control
Tool allowlists, bounded timeouts, limited retries and idempotency keys prevent unintended repeat execution.
06Human approvalReview · approve · hand over

The responsible person decides on consequential actions.

Reads
Action preview, sources, open questions and the required approving role.
Writes
Only after valid authorisation: an approved message, permitted note or confirmed task.
Control
Record the approving role and decision. No independent rate changes, payments or binding commitments.
07Operations & traceabilityAudit · monitoring · evaluation

Make outcomes and failures visible and provide a reliable fallback.

Reads
Technical state events, source references and minimised quality metrics.
Writes
PII-minimised audit events, failure notifications and defined deletion requests.
Control
No guest content in technical logs. Agree retention, monitoring, recovery and ownership before operation.

ILLUSTRATIVE GUEST REQUEST · NO LIVE DATA

Email → permission check → approved hotel policies → reply draft → approval → authorised channel → audit

Spa availability is missing? The draft says so. Approval is rejected? Nothing is sent. An event arrives twice? It does not create a second action.

Knowledge with provenance

Answers reference approved documents, versions and review dates. If a source is missing or policies conflict, the workflow asks for human confirmation.

Permissions before model context

Access is checked before retrieval. Tenants and roles remain separate; an external integration partner receives only the necessary, agreed scope.

Actions with defined boundaries

Tools and actions are explicitly allowlisted. A draft is not permission to send. Consequential guest, rate and financial decisions require the responsible person.

Failures made visible

Timeouts, stale data and unavailable APIs stop the affected action. Limited retries, unique event IDs and idempotency prevent duplicate tasks or messages.

Operations that can be reviewed

Testing and evaluation begin in a sandbox. Staging and production remain separate. Logs contain technical references rather than guest content; retention and deletion are defined.

Deployment after assessment

EU cloud, private deployment and on-premises options are assessed for the actual project. Providers, remote access, contracts and international transfers need review.

The actual design depends on interfaces, permissions, data quality and contractual requirements. Security and privacy measures are assessed for each project; no blanket certification or EU-only processing is claimed.

KNOWLEDGE WITH PROVENANCE

Your rules.
Sources matter.

Answers come from approved hotel information. When a current source is missing, the question goes to your team.

Explore the architecture
FICTIONAL HOTEL DOCUMENTS
01Arrival & hotel policiesFront office / v3

Approved arrival and stay information. The front desk reviews any special commitments.

Approval
Front office (example role)
Reviewed
16.11.2026 (demo date)
Expiry
Defined in the project

citation: demo-policy-1 · v3
role-scoped retrieval · no guest data

02Spa & wellnessSpa management / v2

Approved service information. Availability and appointments require current confirmation.

Approval
Spa management (example role)
Reviewed
16.11.2026 (demo date)
Expiry
Defined in the project

citation: demo-policy-2 · v2
role-scoped retrieval · no guest data

03Service & handoversOperations / v4

Ownership, standards and escalation routes. Only the appropriate hotel roles receive access.

Approval
Operations (example role)
Reviewed
16.11.2026 (demo date)
Expiry
Defined in the project

citation: demo-policy-3 · v4
role-scoped retrieval · no guest data

Current version. Appropriate role. Traceable approval.

LET’S TALK ABOUT YOUR HOTEL

Where does your
time go?

Tell us about the task that keeps your team busy every day.

YOUR
PROJECT