Nothing leaves the property
Guest records, folios and documents stay on your server. There is no telemetry and no phone-home.
Deployment
Lobbix on your own server
Some properties cannot put guest data in someone else's cloud — a regulator, a group policy, or an internet connection that drops every afternoon. Lobbix installs and runs entirely inside your own infrastructure.
- No internet required
- Your hardware
- One command
Front desk
What you get
The whole system, on your side of the wall
Runs with the cable unplugged
Front desk, housekeeping, billing and reporting work with no route to the internet at all.
Licence checked locally
Your licence is verified on the machine by signature. Nothing contacts us to let you in tomorrow morning.
Installs from one package
No PHP, no Node, no database to set up by hand. The installer brings its own container runtime if the server has none.
Backup and restore
A single verified archive, restorable onto different hardware — which is what a disaster recovery actually is.
Offline upgrades
A new release arrives as a file. Apply it on the server; it migrates and rolls back on its own if it cannot finish.
How it goes in
From a bare server to a working front desk
Copy the package
One archive onto the server, by USB or your own network. Nothing is downloaded during the install.
Run the installer
sudo ./lobbix-installer install, then the licence code we issued you. There is no .env to edit.
Check the room
The installer verifies every service, the message queue and the database itself, then books and cancels a test reservation to prove the system works before handing it over.
Frequently asked questions
Does it really work with no internet?
Yes. The install, the licence check, the upgrades and every day of normal use happen with no route off the machine. That is the case the product is built and tested against, not an afterthought.
What does the server need?
A 64-bit Linux server — Ubuntu 22.04 or 24.04, Debian 12, Rocky, AlmaLinux or RHEL 9 — with 8 GB of memory and room for your data. If it has no container runtime, the package installs one.
Who keeps it running?
You do, and the installer is built for that: one command for status, one for a health check that explains what is wrong in words, one for a backup. No shell scripts to inherit.
What happens when the server dies?
Install Lobbix on the replacement, carry across the backup and its key, and restore. The restored system is the system you had, on different hardware.
Can we move to the cloud later, or back?
It is the same product either way. Talk to us before you plan the move so the data comes across in one piece.
How is it licensed?
A licence file we issue for your property, unlocked by a code. It states what you bought — editions and how many properties — and it is verified on your machine, offline.
Talk to us about an on-premise install
Tell us about the property and the constraint you are working under, and we will tell you plainly whether this fits.