What is it?
HolidaiButler was built as a multi-tenant platform right from the very first line of code. Every destination, DMO or leisure organisation runs on the same codebase whilst retaining everything that is unique to it: its own domain, its own branding, its own data and its own users.
Specifications
- Automatic destination recognition on your own domain or subdomain. A single infrastructure, with each brand at its own address.
- Six role levels, ranging from platform administrator to reviewer, strictly separated by destination.
- Customised layout for each type of destination: municipality, leisure area or city.
- Shared codebase with isolated data. A single update reaches all destinations simultaneously, whilst the data remains separate.
- Full configuration for each destination via the Admin Portal, without the need for a developer.
- Commerce features can be enabled or disabled on a per-destination basis.
What makes this different?
Traditional destination platforms set up a separate environment for each client. This means that every update requires a separate roll-out, and each client bears its own maintenance burden. HolidaiButler shares a single codebase across all tenants. An improvement implemented today goes live at every destination today, without any migration risk.
Also for hotels, chains and associations. The same multi-tenant architecture that serves destinations works for hotel chains and trade associations: each hotel or member has its own brand, its own domain and its own data, managed centrally by the organisation. One platform, each member with its own identity.
This is how a destination manager manages the content, locations and sales for their own destination. Demonstrated using a demo account, without any real personal data.
Would you like to see how this works for your destination?
Request a Demo