Relay booking core
Tenant isolation, reservations, inventory, rate plans, audit records, recovery queues, operator identity bindings, and activation receipts are implemented for release validation.
Relay hotel booking and operations
One controlled operating path from room inventory to every approved channel.
Relay is being prepared for hotels that need direct Booking.com, Expedia, and Agoda distribution, a native Windows connection to an approved Yardi or InnSoft Check-Inn interface, visible reconciliation, and guarded pricing.
DirectProvider integrations
OutboundWindows connector
14 daysPricing pilot minimum
Hotel paidPMS and vendor fees
Capability status
Code readiness and vendor permission are separate gates
OAuth login alone does not authorize inventory, reservation, or rate access. Live capability is shown only after provider, property, and production checks have receipts.
Booking.com, Expedia, and Agoda
Direct provider adapters stay disabled until each provider accepts the business, property, technical, security, and certification requirements.
Yardi and InnSoft Check-Inn
The Windows connector uses an outbound-only service boundary. A live adapter requires the vendor-supported interface, hotel authorization, and property-side test environment.
Dynamic pricing
Guardrails cap rate changes, preserve floors and ceilings, and log each recommendation. No unattended automatic pricing starts before the pilot and written approval.
Hotel service packages
Start with the smallest safe operating scope
Every package is a custom quote because room count, PMS contracts, provider accounts, Windows hardware, and support expectations vary by property.
Hotel Systems Readiness
Custom quoteA fixed discovery and evidence package before live system access.
- PMS, OTA, identity, inventory, and rate review
- Provider approval and contract checklist
- Data-flow, security, recovery, and launch plan
Relay Launch Pilot
Custom quoteOne approved property moved through configuration, controlled connection, reconciliation, and staff handoff.
- Approved channel and PMS activation
- Connector install, monitored sync, and rollback checks
- Fourteen-day recommendation-only pricing pilot
Managed Relay Operations
Custom quoteOngoing operational coverage after a property passes its launch checks.
- Connector and channel monitoring
- Reservation, inventory, and rate reconciliation
- Exception review, updates, and documented support windows
Commercial boundary
The hotel pays its property and provider costs
AES does not hide vendor fees inside a software claim or advance unapproved third-party charges.
Hotel-paid costs
PMS licenses, service contracts, interface or certification fees, vendor support, OTA charges, payment-provider fees, property hardware, Windows licensing, networking, email, and domains remain the hotel's responsibility.
AES service costs
Readiness work, implementation, Relay hosting, connector setup, monitoring, operational support, and approved custom work are quoted separately by AES.
No surprise activation
Before a paid vendor step, the hotel receives the known amount or estimate, who charges it, what capability it enables, and whether it is recurring. Work stops at that gate until written approval is recorded.
Operating sequence
A release path staff can inspect
1. Verify the property
Confirm ownership, rooms, rate plans, taxes, policies, staff roles, Windows environment, and the actual PMS version.
2. Obtain provider access
Complete direct OTA and PMS applications using the hotel's real business contracts. Passwords and MFA stay with the account owner.
3. Connect in a test lane
Map identifiers, replay sample changes, reconcile reservations and inventory, prove recovery, and keep live writes disabled.
4. Run a guarded pilot
Enable only approved capabilities, monitor every sync, begin pricing as recommendations, and keep rollback available.
5. Approve production operation
The hotel signs off on acceptance results, vendor costs, support ownership, incident contacts, and any later move to automatic pricing.
Hotel systems inquiry
Tell us about the property, not the passwords
A founder will review the PMS, channel, room-count, and operating context and return the smallest useful first scope.
Do not send passwords, API keys, MFA codes, payment data, guest records, or copies of vendor contracts through this form.