Fourteen modules. One database. One calendar for everything you sell.
Alisio treats a room, a sauna, an EV parking bay, a lounger and a 90-minute hot tub session the same way: as a resource with a calendar, a cost model and a price. That is why an eighteen-unit property ends up with sixty-plus sellable resources, and no extra capex.
Calendar & Bookings
Drag-and-drop tape, colour-coded statuses, quick create, group bookings with one balance, room allocation, availability blockers, audit log per booking.
Channel Manager
Two-way ARI with Booking.com, Airbnb, Expedia, Hostex and iCal. Unit mapping, retry queue, parity monitoring, per-channel true cost.
Finance, P&L & CashFlow
Multi-account ledger, accrual P&L with CapEx/OpEx split, cash-flow matrix, investor module, bank and terminal reconciliation, e-invoices.
Guest Portal
Token-based personal page: self check-in, document upload, digital signature, balance payment, in-stay services, live chat, post-stay NPS.
CRM, Inbox & AI
Kanban sales pipeline, one inbox for Telegram, e-mail and website chat, knowledge base trained on your property, replies in any language.
Compliance & Trust
Foreign guest registration, city tax book and declaration, DAC7, Peppol e-invoicing, GDPR retention, AI Act transparency log.
Housekeeping & Tasks
Kanban and list boards, tasks bound to units, priorities and deadlines, Telegram assignment, photo proof, cleaning minutes in the P&L.
The AI crew
Thirteen specialists with typed tools, guardrails and KPIs. Autonomy L0–L5 per agent, decision Ledger, auditor, kill switch.
And the rest of the plumbing
- Properties, buildings, categories, unit types, bulk generator up to 200 units
- Dynamic pricing, weekend rates, min-LOS, bulk updates, promo codes
- Payments: links, pre-auth deposits, webhooks, partial refunds
- Reports: occupancy, ADR, RevPAR, ALOS, source mix, per-unit performance
- RBAC: owner, manager, finance, reception, housekeeping, investor, auditor
- Admin: system audit log, retention cleaners, Telegram bridge, morning digest
Architecture, in four layers
The reason the crew can be trusted is not the model. It is what sits underneath it.
Surfaces
Deck for reception, Pulse for the owner, Pocket for line staff, and Thread for the guest in the messenger they already use. There is also an agent endpoint, so external AI assistants can query and book your property directly.
Agent mesh & trust contract
Thirteen agents, typed tools only, autonomy levels, the decision Ledger and an auditor that grades the rest. No agent has raw database access, nothing can execute an arbitrary operation.
Semantic layer, the property ontology
A graph of resources with capabilities, constraints and cost models; a graph of guests resolved to one identity across channels; a graph of money where every euro carries its origin and its destination.
Event backbone
No table holds the truth; the sequence of events does. That gives you free undo, time-travel debugging, "show me the property at 14:03 on Tuesday", and offline-first reception that keeps working when the internet does not.
Pricing is a conversation, not a table
A base per active unit, plus a share of the uplift we can prove against a holdout baseline. No setup fee, no charge for integrations or extra users, no commission on your direct bookings. Tell us your unit count and channel mix and we model it in EUR and CZK.