Hospitality · 720-hour cycle
kaedax builds hospitality software — property management systems, channel managers, housekeeping consoles, dynamic-pricing engines — in a fixed 30-day (720-hour) cycle. PCI-DSS-aware card-payment flows, GDPR/DPDP-compliant guest-data handling, and no-double-booking reservation integrity are in the spec from day one, not bolted on before audit.
Occupancy tonight
91%
+6% vs last Sat
RevPAR
$184
+$22 wow
Channel conflicts
0
lock active
Rooms pending clean
4
of 48
[ §01 ] the problems we're hired for
Channel managers that sync OTA inventory over eventual-consistent queues create race conditions that land two guests in the same room. We build reservation engines with optimistic locking and idempotent OTA webhooks — double-booking becomes a CI gate, not a 1 a.m. call to the front desk.
Hotels that store even a masked PAN outside a certified vault are in scope for PCI-DSS v4.0, which became mandatory in March 2025. We build tokenized payment flows from the start — raw card data never touches your servers, and your SAQ shrinks to the smallest possible scope.
Revenue managers at independent hotels manually adjust rates by refreshing OTA dashboards — a practice that leaves 15–30% of room-night revenue on the table vs. rule-based automation. We build pricing engines with configurable rules, compset feeds, and override controls that plug into your PMS, not replace it.
A room flagged 'clean' by a distracted attendant with a paper checklist becomes a TripAdvisor moment. We build mobile housekeeping flows with room-by-room task checklists, photo inspection, and real-time status sync to the front-desk console — not a separate app the team ignores.
[ §02 ] what ships
The shapes of hospitality work that fit a 720-hour cycle. Every build ships with runbooks, monitoring, and 30–60 days of post-launch on-call.
Availability calendars with locking, folio management, check-in/check-out flows, OTA channel sync with idempotent webhook handling.
Two-way ARI sync to Booking.com, Expedia, Airbnb, and direct-booking engine with rate-parity enforcement and conflict alerting.
Rule-based rate automation with compset feeds, occupancy triggers, override controls, and revenue-impact reporting.
Mobile room-assignment flows, checklist-based inspection, photo capture, real-time status board for front desk.
[ §03 ] proof
Our hospitality posture is built on adjacent regulated work — see all case studies across fintech, healthtech, insurance, and AI products. The engineering disciplines transfer; the scope call establishes the specifics.
We expected a prototype. We got a production console with audit trails our compliance team was actually happy with. Three days early.
[ §04 ] questions
Off-the-shelf PMS solutions start around $15,000 for basic front-desk ops, but custom builds with channel management and dynamic pricing typically run $60,000–$200,000 over 4–8 months with traditional agencies. kaedax prices per fixed 720-hour cycle, shared on the scope call — one cycle ships a focused PMS surface with channel sync and housekeeping console included.
Optimistic locking on the reservation record means two OTA webhooks arriving simultaneously resolve to one confirmed booking and one politely declined — handled at the database layer, not in application logic. Idempotency keys on every OTA write mean retries don't create phantom reservations.
Yes, and PCI-DSS v4.0 has been mandatory since March 2025. We build tokenized payment flows — cards are captured directly by a certified vault (Stripe or equivalent), never touching your server, collapsing your assessment scope to SAQ A or A-EP. The audit trail for every transaction is signed and append-only.
Guest data is purpose-limited at ingestion: only what's needed for the stay, encrypted at rest, access-logged per role, and deletable on request. Consent state is a first-class field in the data model — not a checkbox in a settings screen added before a compliance audit.
Yes — channel manager adapters with two-way ARI (availability, rates, inventory) sync are a deliverable, not an afterthought. We build contract tests around each OTA's API quirks so their schema changes surface in CI before they surface as misbookings.
For one focused surface — reservations with channel sync, housekeeping ops, and a guest-data-safe payment flow — yes. A full multi-property enterprise PMS with revenue management, loyalty, and F&B integration spans multiple cycles, and we map that on the scope call.
A 15-minute scope call with a kaedax founder and the engineer who'd lead your build. We either fit your hospitality product into 720 hours, or we tell you why not — same call.
▷ other verticals