Platform

One operational layer above the tools you already use.

Hestix connects data, workflows, operating rules and intelligence without asking you to replace tools that already work.

  1. PMS · Channel Manager · Providers
  2. Hestix
  3. Workflows · Control · Intelligence

Hestix and your stack

The PMS stays the PMS.

The PMS keeps doing the PMS job. Hestix uses that data to make the rest work together.

Your PMS and channel manager continue to handle distribution and bookings. Hestix connects the context they make available and puts it to work across other operations, without positioning itself as a universal replacement.

  1. Distribution and bookings

    They stay in the specialist system you already use.

  2. Operational context

    Hestix receives or connects available data through controlled integrations.

  3. The rest of the work

    That context can support access, compliance, operations and financial control.

Orchestration model

From existing systems to action, through Hestix.

Three layers make the platform's role clear: sources remain specialised, Hestix normalises context and applies rules, Knowledge and workflows, then outputs support day-to-day operations.

  1. Sources / providers

    Systems and signals that make context available.

    • PMS / Channel Manager
    • Booking data
    • Guest interactions
    • Smart Access
    • Environmental sensors
    • Operational configurations
  2. Hestix operational layer

    The shared layer connecting information and responsibilities.

    • Business context
    • Normalised data
    • Business rules
    • Knowledge
    • Workflows
    • Deterministic calculations
    • AI interpretation
  3. Outputs / actions

    Operational outcomes with transparent maturity states.

    • Guest operations
    • Access lifecycle
    • Compliance
    • Financial control
    • Alerts and operational insight
    • Environmental monitoring · Beta
Specialist systems stay in place. Hestix creates one operational layer across data, workflows and actions.

Provider-agnostic

The provider can change. The operating model remains.

A Hestix capability is not the same thing as its first implemented provider. The platform is designed to work with different providers without claiming universal compatibility.

Smart AccessTTLock

TTLock is a current provider, not the name or boundary of the capability.

Environmental MonitoringTuya / Smart Life

Tuya / Smart Life currently supports the Beta capability, but does not define the product.

Booking integrationOctorate

Octorate is the first documented PMS integration, not the identity of the booking layer.

Integrations are verified and implemented one at a time: provider-agnostic describes the platform design, not a connector already available for every system.

Cross-platform intelligence

AI runs across the platform. It does not replace the rules.

Knowledge can provide context; AI can interpret results that have already been calculated and assist workflows and conversations. Business rules and verifiable calculations remain separate from generative interpretation.

  1. Data
  2. Hestix logic
  3. Deterministic result
  4. AI interpretation

Knowledge and context

They give AI approved or available information for the task at hand.

Rules and calculations

They produce verifiable states and numbers without delegating them to a generative model.

Interpretation and assistance

They help people, workflows and conversations use what Hestix already knows.

Hestix calculates the numbers. AI helps you understand them.

Capability map

What is here today. What is still evolving.

Public states distinguish available capabilities, areas being consolidated, demonstrable betas and future development.

Available
  • AI Guest Assistant
  • Generic AI / Knowledge
  • Knowledge Manager
  • Booking / PMS Integration
  • Dashboard
  • Local Guide
  • Alloggiati Web
  • Smart Access
  • Financial Control
  • Property Manager
Evolving
  • Guest CRM
  • OTB / Pace
Beta
  • Environmental Monitoring
In development
  • Revenue Management

The capability map describes the platform; only the published solutions below currently have dedicated pages.

AI and Knowledge

You do not need a booking to talk to Hestix.

Knowledge and the AI runtime can support a conversation even when it does not begin with a booking or an already recognised guest. Hospitality context is used when available; this foundation is not a promise of a universal chatbot.

Organisational context

Each business keeps its own context.

Each business keeps its own context, configurations, responsibilities and Knowledge, so properties and operations can share one environment without losing their individual operating context.

Controlled integrations

Hestix lives through the connections that matter.

Hestix does not live in place of integrations: it works through controlled connections with the systems that matter. Provider-agnostic means the architecture does not depend on a single vendor, not automatic compatibility with any provider.

These are representative examples of systems actually connected. The authoritative catalogue, with the scope and status of each integration, is the directory.See the integration directory
  • OctorateCurrent provider for booking / PMS context.
  • TTLockCurrent provider for Smart Access.
  • Tuya / Smart LifeCurrent provider for Environmental Monitoring Beta.

Published solutions

Seven vertical views of the same platform.

Solution Pages explore specific operating domains. They are not isolated products: they share the Hestix layer and the context that runs through it.

Property Manager

Commissions, settlements and operator balances for property managers working on behalf of owners.

Explore Property Manager

Hestix in your stack

Want to see how Hestix fits into your operational stack?

We start with the tools and workflows you already use, then identify where a shared operational layer can create value.

Request demo access