Skip to content

Part of PACsys

PACsys Network

One live view of every property you operate. PACsys Network is the multi-property layer of PACsys — it sits above the installations in your buildings and gives owners, support teams and on-call engineers the same real-time picture, from a browser or a phone, wherever they are.

  • ~300 properties in production
  • Fleet rollouts & remote diagnostics
  • Per-property data isolation
  • Outbound-only, no inbound firewall rules
Request a demo

~300

Properties in production

50+

HMS & PMS integrated

Under 250 ms

Event to screen

Zero

Check-ins lost to a dropped link

The portal

Every room, on one screen

Occupancy, housekeeping, device health and the day’s activity — for one property or for all of them. Built for the people running the building, not for a data team.

Interface preview — property names and figures are illustrative.

Capabilities

What the cloud layer adds

Every property on one screen

Room state, occupancy, housekeeping queue and device health for every property you operate, in one place. Switch between properties without switching systems.

Pushed, never polled

Changes arrive over a live connection the moment they happen on the floor. No refresh button, no stale tile, no dashboard that is quietly three minutes behind.

Survives a bad link

A property with unreliable internet does not lose data. Events queue on site and ship when the connection returns, in order. Across roughly 300 properties in production we have never lost a check-in to a dropped network.

Fleet firmware rollouts

Pick a version, pick the properties, and the sites update themselves. Staggered, gated and reversible — so a bad release is contained to the pilot group instead of the whole estate.

Diagnostics from a phone

An engineer standing at the rack can enumerate ports, restart the on-site service under a watchdog, sweep every controller on the bus with live per-device results, and read a serial number straight off the wire — from their phone.

Per-property data isolation

Each property keeps its own database. The cloud layer rolls up; it does not pool. A portal user signed in for one property cannot read another’s rows even on an endpoint that forgot to filter.

Granular permissions

Four built-in roles plus custom roles you define, over a catalogue of twenty-two permissions. Every endpoint declares what it requires — the check is in the code path, not in the navigation menu.

Complete audit trail

Every check-in, every command, every administrative override is recorded with actor, target, payload and timestamp. Reconstructing what happened after an incident is a query, not an investigation.

Notifications that reach people

Alerts reach a supervisor’s phone whether or not the browser tab is open. An overdue room does not wait for someone to look at a screen.

How it works

From the floor to your screen

The path an event takes is deliberately boring. Every hop has somewhere to put the data if the next hop is unavailable, which is why a bad night on a hotel’s internet connection is not an incident for us.

01

The room

A guest checks in, a door opens, a controller drops off the bus. The on-site service sees it happen on the wire.

02

The property

The event is written to a durable queue in the property’s own database before anything leaves the building. Nothing depends on the internet being up at that moment.

03

The agent

A small service on the property server drains the queue, ships events outbound over HTTPS, reports its own health, and applies updates when you assign them.

04

Your dashboard

The event lands in the multi-property view and is pushed to every open browser and phone. Typically under a quarter of a second from the floor to the screen.

Deployment

Your server or ours

Some chains want the database inside the building. Others do not want a server in the building at all. Both are supported shapes with the same feature set — the decision is yours and it can change later.

On-site

Default

Controller service, database and sync agent all run on the property’s own server. Nothing crosses the internet except the outbound sync to the cloud dashboard. The choice for properties with a capable IT function or a regulatory reason to keep data in the building.

Hosted

Cloud

The database and sync agent run in our infrastructure; only the controller service stays at the property, reaching out over standard HTTPS. No inbound firewall rules, no VPN, no server for the hotel to maintain. Feature parity with the on-site shape.

Nothing punches into the hotel. The property reaches out to us, never the other way round. There is no inbound firewall rule to justify to a hotel’s IT department and no VPN concentrator to maintain.

Operating at fleet scale

What running 300 properties actually taught us

These are not design intentions. They are the practices that survived contact with a live estate — and the reason the next hundred properties are cheaper to run than the first hundred were.

Events buffer on site

Activity is written to a durable queue inside the property’s own database before it is sent anywhere. The link can drop, the agent can restart, the server can reboot — the queue survives all three and drains in order when the connection returns.

Schema updates without a DBA

The on-site agent installs and versions its own database objects at startup. Rolling out a schema change across the estate does not require the customer’s database administrator to do anything.

Staged rollouts

Versions are assigned per property, so a release reaches a pilot group first. When a bad build has shipped, this is what has kept the blast radius to a handful of sites rather than the whole fleet.

Reversible deployments

Server releases are snapshotted before they are swapped in. A rollback is one command and a few seconds of downtime, which means we can deploy fixes quickly instead of carefully.

Headroom

The current architecture is sized for well beyond where the estate sits today, and the parts that would need to be split under heavier load are already separated in the codebase — so growing is a configuration change rather than a rewrite. We would rather tell you where the ceiling is than claim there isn’t one.

Full architecture and security detail is on the platform page.

Properties in production
~300
HMS & PMS integrated
50+
Event to screen
Under 250 ms
Check-ins lost to a dropped link
Zero

See it with your own properties on it

Tell us how many properties you run and what is installed in them. We will show you the multi-property view, walk through a rollout, and be straight about what onboarding involves.

Request a demo sales@tes.ind.in