The platform,
finished as one product.
Modern hotel software is more capable than ever, but it is often built in separate modules, products, and add-ons. Lintel was designed as a single system, so reservations, revenue, housekeeping, and guest history all work from the same foundation.
Six beliefs about hotel software.
The rules we wrote at the beginning. Every screen, every endpoint, every release is checked against them.
One product, not a marketplace.
No app store, no certified-partner pyramid, no plug-in tax.
Restraint over decoration.
Typography and palette do the work. No drop shadows pretending to be importance.
Every override, in the open.
If the system suggests a rate and a human changes it, the change is named, dated, and reversible.
The data is yours.
Read-only export of the whole record, on demand, in formats your accountants already speak.
Pricing is published.
Per-room, per-month, with everything included. The contract is short enough to read at dinner.
Founders on call.
For the founding cohort, a private line to the team that built it. Response measured in minutes.
Eight screens.
One vocabulary.
Eight surfaces, each finished to the same standard. Learning the second surface takes ten minutes — every shortcut from the first one still works.
- 01Shared component library — the same calendar widget appears in Reservations, Revenue, and Group Bookings.
- 02One auth, one permission system — a single role grants access across every surface.
- 03Cross-surface deeplinks — every entity has a permanent URL that opens it in any surface.
The system
watches its own house.
A continuous loop of sensing, scoring, recommending, and writing back. Not a chatbot. A small, opinionated set of agents that read every event, every minute.
- 01Continuous, not on-demand — the loop runs every 90 seconds across pricing, pickup, parity, guest signals, and operations.
- 02Confidence intervals, always — every recommendation is a range with a posterior, not a number.
- 03One-click write-back — accept a suggestion and it cascades; the audit trail records who said yes.
Every event in the house,
one stream.
Every action — a guest checking in, a rate being changed, a room being cleaned — is published as a typed event into a single, durable, replayable stream.
- 0142 typed event categories covering reservations, rates, guest, payments, ops, and parity probes.
- 02Replayable from any point — rebuild the entire state of the hotel at any timestamp.
- 03Yours, on request — daily exports of the raw stream to your warehouse. No data hostage.
Open at the edges,
finished in the middle.
Lintel speaks fluently to the systems that matter, with first-party connectors maintained by us — and a clean, documented API for everything else.
Open API. Everything talks.
REST and webhooks for every resource — guests, reservations, rates, folios, events. Versioned, documented, rate-limited honestly.
# Subscribe to rate changes POST /v1/webhooks { "events": ["rate.applied"], "url": "https://ops.example.com/hooks" } # → 201 created · whk_b9c4ae
Raw export, on a schedule.
Daily, full-fidelity export of the event stream to your S3, BigQuery, or Snowflake — no SKU, no separate contract.
# Configure warehouse export lintel export --to snowflake \ --cadence daily \ --retain 730 # Snowflake · lintel_events · live # 42 tables · 14,318 rows · last 24h
What we don't call features,
but consider non-negotiable.
Every Lintel tier ships with these. They are not add-ons, premium tiers, or marketplace plugins.
SOC 2, GDPR, PCI-DSS
Independently audited. Encryption at rest and in transit.
99.97% uptime SLA
Multi-region failover. Status page transparent to the minute.
p99 < 400ms · global
Every surface measured against the same budget.
Founders on call
A private Slack with the team that built it. Response in minutes.
The whole platform.
One conversation.
Thirty minutes with a founder — walked through your property, your stack, your particulars. The platform on screen, and the questions you actually want answered.