Skip to content
GudiSystem
Architecture

The engineering, no makeup.

For those who want to see under the hood. Real multi-tenancy in the database, outbound integration with no public exposure and security as architecture, not as a marketing page.

Architecture

Multi-tenant by default

Isolation

Per hotel, at the data layer

Real time

Event-driven

Integration

Open standards, outbound

Security

Private access · 2FA

Compliance

Privacy by default

Multi-tenancy

Isolation in the database, not in the application.

Each hotel is a tenant isolated at the data layer itself. Isolation is guaranteed by the infrastructure, not by application code: one hotel never sees another's data, by construction, not by a rule someone can forget.

Isolation per tenant

Hotel AIsolated data
Hotel BIsolated data
Hotel CIsolated data

Each hotel lives in its own data space. Guaranteed by the infrastructure, not by a rule someone can forget.

Ports and adapters

Your PMSAdapter
OTAs and channelsAdapter
PaymentsAdapter
Hotel servicesAdapter

Each external system enters through a dedicated adapter. Swapping a provider means swapping the adapter; the core does not change.

Integrations

Ports and adapters. Plug in what you need.

Each external system (PMS, OTAs, channel managers, payments) enters through an interface with a clear contract and a dedicated adapter. Booking ingestion is idempotent and outbound: the system pulls, nothing is exposed to the internet. Swapping a provider means swapping the adapter; the core does not change.

  • Connector to your PMS as the system of record
  • OTAs over open standards, idempotent ingestion
  • Channel manager over polling, no public webhook
  • Pluggable payment hub, with Brazilian tax
Security & data privacy

Security is architecture, not a badge in the footer.

Hospitality is one of the sectors most targeted by digital fraud. We treat guest data as the critical asset it is: private access, strong authentication and the smallest possible exposed surface.

Two-factor authentication

2FA compatible with the market's authenticator apps. Mandatory for owner and admin.

Private, restricted access

The operational console sits behind private, device-authenticated access. Zero public web port for hotel data.

Privacy by default

Per-hotel isolation, encrypted secrets, least privilege and idempotent ingestion. Automated tests on every release.

Want the full technical detail?

The technical documentation (architecture, security and integration) is delivered on request, subject to approval. No black box for whoever is going to integrate.