┌────────────────────────┐  ┌────────────────────────┐  ┌────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│  │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│  │░░░░░░░░░░░░░░░░░░░░░░░░│
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│  │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│  │░░░░░░░░░░░░░░░░░░░░░░░░│
│                        │  │                        │  │                        │
│   S U A V E            │  │   S U A V E            │  │   X E M A              │
│   P M S                │  │   C O N C I E R G E    │  │   A G E N T   L A B    │
│                        │  │                        │  │                        │
└────────────────────────┘  └────────────────────────┘  └────────────────────────┘

══════════════════════════════════════════════════════════════════════════════════
  B R U N O   D I   S A N T O
  founder and engineer  ·  hotel operating systems  ·  paris
  linkedin.com/in/disantobruno
══════════════════════════════════════════════════════════════════════════════════

I build the software boutique hotels run their day on — reservations, front desk, folios, payments, guest messaging — plus the tooling I use to build it safely.

• SUAVE PMS — hotel operating system for 8 to 25 room properties. Reservations, front desk, housekeeping, folios, payments, rates, night audit.
• SUAVE Concierge — WhatsApp-first concierge. Guests text the property, the system answers in their language, staff take over on demand.
• XEMA — local agent lab. Bounded execution, repository guards, audit trails, explicit human approval gates.

Production code is private. I don't publish customer data, credentials, provider configuration, or internal architecture to make a profile look busier.

frontend    React · TypeScript · dense operational UI · desktop-first
backend     Postgres · row-level security · RPC boundaries · typed service layers
security    fail-closed auth · least privilege · per-tenant isolation
payments    Stripe · folios · reservation ledgers · refunds and voids
agents      local-first orchestration · bounded subprocesses · approval gates
quality     Vitest · Playwright · CI gates · adversarial review

Software that survives real operations, not demo screenshots.

Five questions, always in this order, before anything ships:

1. What should the user be able to do?
2. What must be true in the data after the action?
3. What can fail, and how does it fail safely?
4. What belongs in the UI, the service layer, the database, the audit log?
5. What evidence proves it works on the real path?

The last one is the one people skip. A green test suite proves the repository's gates pass. It does not prove deployment, delivery, or that a receptionist can close a folio at 2am without losing money.

──────────────────────────────────────────────────────────────────────────────────
  linkedin  ·  suave pms  ·  suave concierge  ·  xema
──────────────────────────────────────────────────────────────────────────────────