Chapter 01 · The situation
Twenty two properties. One IT function that has to feel like enterprise.
Stayokay has been part of the Dutch hospitality landscape since 1929. Twenty two hostels today, spread across the country from Amsterdam to Terschelling, from Maastricht to Egmond. Over a thousand guest beds. A recognisable brand rooted in accessibility. And a guest expectation that has not stayed still: connectivity that carries digital check in, point of sale that responds instantly, back office systems that never make the receptionist apologise. Enterprise expectations, running under a lean cost structure.
The infrastructure that supports twenty two properties has to feel like it belongs to a much larger group. The IT function that owns it does not have to be much larger. The trick is engineering that difference.
Every hostel needs the same operational baseline: network, firewalls, endpoint infrastructure, backup, security posture. Doing that with a dedicated IT team per property would cost more than the hostel margins allow. Doing it centrally, on premise, would mean a data centre and staff Stayokay does not need for anything else. The answer is neither of those. The answer is a central Azure architecture, managed as a discipline, with a small internal team that stays close to the business and a partner that runs the operational layer twenty four hours a day.
What makes the Stayokay infrastructure challenge specific
Every property runs the same operational baseline, but each one has its own physical context. A city hostel in Amsterdam Vondelpark handles a different guest density than a coastal property on Terschelling. The infrastructure has to behave the same regardless. Continuity between them, and consistency inside each, is what the internal team was hired to protect. Sbit’s role is to make that possible without asking the internal team to become the operations team as well.
Chapter 02 · The Azure foundation
One cloud architecture. Every property connected. Every layer accountable.
The infrastructure Stayokay runs on today is Azure at the centre and property equipment as the extension. Not a hybrid environment stitched from legacy systems and cloud add ons. A cloud native architecture designed by Sbit, deployed by Sbit, and maintained by Sbit as one continuous operational discipline. Every property inherits the same baseline. Every service inherits the same security posture. Every change flows through the same governance.
The four operational layers of the Stayokay infrastructure
Central Azure architecture
Identity, applications, group services and financial systems consolidated in one cloud tenant. Governance, cost control, capacity planning and lifecycle management running as one operational discipline. The environment scales up or down against the operational calendar, not against a fixed on premise footprint.
Property connectivity as extension
Every hostel connects into the central architecture through the same secure network baseline. Local hardware — network, firewalls, endpoints — is treated as an extension of the central platform, not as a separate operational island. Twenty two properties, one operating model.
Backup, continuity and disaster recovery
Backup and DR are architected into the platform, not added afterwards. Continuity is measured on the properties that actually rely on it, and restore paths are tested rather than assumed. When something needs to come back online, the time to recovery is a number, not a promise.
Security posture as a platform layer
Endpoint protection, identity controls, threat monitoring and compliance reporting are woven into the Azure baseline itself. New properties inherit the security posture automatically. Audit dossiers are maintained continuously, so NIS2 and GDPR conversations happen from a position of readiness, not preparation.
Together these four layers form the operational foundation Stayokay’s small IT team could not have built and maintained alone. Not because the team lacks skill. The opposite, they are specialised where it matters most, but because architecture at this scope is a different discipline than the strategic work the internal team was hired to do.
Chapter 03 · Monitoring and support
Watching before anyone has to look. Answering when hospitality actually runs.
A cloud architecture is only as good as the operational discipline running underneath it. For Stayokay, that discipline splits into two halves that reinforce each other: continuous monitoring that catches problems before users notice them, and support hours that match how hospitality actually operates.
Monitoring as a proactive layer, not a reactive one
Sbit’s operations team watches the environment continuously across every property. Alerts are calibrated to catch degradation early, not just outages. When a firewall in Rotterdam starts logging unusual traffic patterns at 04:30, the ticket exists before the first guest complaint would have surfaced. When a backup fails silently, the operations team knows within the hour. Most incidents are quiet by the time the internal team hears about them, if they hear about them at all.
Support when the hospitality day is longest
The traditional office IT support model runs from nine to five on weekdays. That model does not work for hospitality. A hostel does not empty out at 17:00, and a Friday evening at check in is when infrastructure is being asked to do its hardest work. Sbit’s support model runs against the operational reality of the properties, which means available in the evenings and weekends, not just when the office is open. That is a direct requirement of how hospitality actually operates, and it is a direct pillar of the engagement.
The internal team stays close to the business
Stayokay’s IT function is deliberately small and deliberately specialised. Their people spend time on strategy, financial systems, integrations with reservation and booking flows, and the parts of the environment that reward business proximity. The parts that reward operational scale: monitoring, patching, incident handling and security operations, sit with Sbit. Both teams see the same information, use the same tools, and speak into the same operational picture.
Change discipline that respects the operation
Every change flows through a defined path. Impact is assessed before, execution is timed to the operational calendar, and validation happens after. New property openings, system upgrades and integrations land without discovery moments in production. This is not exciting. It is precisely what a lean internal team wants from an infrastructure partner.
Chapter 04 · What that delivers
Outcomes across four audiences.
An infrastructure layer engineered this way produces different outcomes for different people looking at it. For Stayokay, all four line up with the reason the engagement exists in the first place.
Four audiences, four outcomes
Guests at every property
Check in that does not stall. Point of sale that responds instantly. Reservation, booking and back office systems that behave the same in every hostel. The parts of the infrastructure that guests never see – until they don’t work – stay invisible, which is the point.
The internal IT function
Peter Verdoold’s team stays close to the business. Strategy, financial systems, integrations – the work that rewards internal knowledge. The operational grind of running twenty two properties sits with Sbit, in the same tools, with the same visibility.
Property managers
No local IT firefighting. No cluster of workarounds. When something breaks, one escalation line handles it. When it is fixed, the fix stays fixed because the change discipline is a platform habit, not a case by case decision.
Finance and the board
Predictable monthly infrastructure costs, scaling per property rather than in step functions. NIS2 board level responsibility supported by documented, auditable platform controls. Continuity engineered in, not bolted on. A capital footprint that stays proportional to the property portfolio.
Chapter 05 · The partnership
The layer around, not the layer instead.
Every long infrastructure partnership eventually gets a shorthand from the client side about what the vendor actually is. Most of that shorthand ends up sounding transactional. Sometimes something more specific comes out, and it tells you what the working relationship actually is.
The line that matters, from the person accountable for finance and IT at Stayokay, is that Sbit is not a replacement for their internal team. Sbit is the layer around it. Available in the evenings, strong where the internal team is thin, and fully integrated into how Stayokay works. That framing does not describe an SLA. It describes a working relationship in which the vendor’s engineers know that a Friday evening infrastructure failure at a busy hostel matters differently than a mid morning one at an office, and staff accordingly.
Stayokay has been running its hostel network for nearly a century. The Azure foundation Sbit runs today is what carries the next chapter of that operation: more digital, more automated, more measured. Same principle underneath. Small internal team, close to the business. Broad operational layer, engineered to make them stronger.