Tickets go on sale soon. Find out now if the site holds. Including booking sites someone else built.
A fixed-price check before tickets go on sale: updates, payments, a load test and a tested backup. Watched on the day, then looked after every month by the same engineers.
Checked every five minutes on sale day
Before sales open
Updates and fixes land weeks before the sale. On the day itself, nothing changes.
No surprises on sale day
50+
Live WordPress and WooCommerce sites we have run
5 min
Between uptime checks on the sites we look after
Daily
Off-site backups, with restores we have tested
2018
Building and running live software since
What walks in
What organisers tell us before a sale, and what we do first
“Last time the site fell over when sales opened.”
A load test of the booking pages at the traffic you expect, and the slowest part fixed first.
Seen in: Events & Tourism
“Updates have been skipped since last season.”
Overdue updates tested on a copy of the site first, and landed weeks before sales open.
Seen in: Events & Tourism
“The developer who built the booking plugin is gone.”
We recover hosting, domain, licences and code, and move everything onto accounts in your name.
Seen in: Events & Tourism
“You hear about outages from guests.”
The site and the booking pages checked every five minutes, with an alert to an engineer when a check fails.
Seen in: Events & Tourism
“Some guests never get their e-ticket email.”
Emails sent through a proper mail service, retried on failure, and tested before the sale.
Seen in: Events & Tourism
What you get
Six things before and after the sale, done by engineers who know your site
A pre-sale check at a fixed price
Before sales open, we go through plugins, theme, payments, emails, hosting and the booking flow from ticket to e-ticket. You get a written list of what will break.
A load test of the booking pages
We test the booking pages at the traffic you expect on sale day, and fix what slows down before your guests find it.
Updates tested on a copy first
WordPress, plugin and theme updates go to a copy of the site (staging) first, and land weeks before sales open. Nothing changes on sale day.
Watched on sale day
The site and the booking pages are checked every five minutes. When a check fails, an alert reaches the engineers who know the site.
Backups you can restore
Daily backups kept on another server, and a restore tested before the season starts.
Engineering hours every month
A budget of hours for new ticket types, dates, fixes and small changes, done by the engineers who already know the site.
Who it is for
For organisers whose sale day matters
A good fit
Your sales open on one day.
A slow site that morning costs tickets, so it needs engineers watching it, not a plugin that updates itself.
- You sell tickets or stays on your own site.
- Sales open soon, and you are not sure the site will hold.
- You want the same engineers before, during and after the season.
WordPress · WooCommerce · Laravel · Booking plugins
Not a fit yet
Selling only on a ticket platform?
The platform runs your sale day, not us.
Come back when you sell on your own site.
Losing bookings already?
Some booking flows need fixing before they can be looked after.
Start with a booking quote.
How the first season runs
Access and a backup first, then the check before the sale
-
Step 01
Recover access and back up
Before anything changes, we get the logins in order and take a full copy of the site and its database, somewhere safe.
-
Step 02
Check the site before sales open
Plugins, payments, emails, hosting and the booking flow, plus a load test of the booking pages. Written up: what is broken, fragile and fine.
-
Step 03
Fix what will break
Overdue updates tested on a copy, slow pages and payment gaps fixed. Then nothing changes until the sale is over.
-
Step 04
Watch the sale, then every month
Checks every five minutes with alerts on sale day. Then tested updates, backups and engineering hours every month, with the same engineers.
In production
Booking sites and stores we build and run
FAQ
