Campsite and holiday park software, built around exactly how you run
Bookings, arrivals, extras, seasonal pitches and invoicing — one system tailored to exactly how your site runs, that you download as a complete Laravel app you own outright — with AI inside that does real work.
Here's how it works. Tell us how your park runs, and we build you a complete system for it — bookings, arrivals and housekeeping, extras, seasonal pitches, invoicing and guest email, configured to your exact rules. The building blocks are already built and tested, so your system is shaped around your site in days, not a six-month bespoke project. And here's what makes it unlike anything else:
You own it. The system is yours — it exports as standard code you can take anywhere, and your guest and booking data lives in your database, not a vendor's. No per-booking charges, no subscription that holds your season hostage, no losing everything if you leave. Download and self-host it whenever you want.
AI works inside it. The AI in your system runs real business tasks — chasing what's owed, confirming bookings, sending the right message at the right moment — with confirmation required on anything financial or irreversible, and a full audit trail. When the system itself needs changing, your developer or a Stellify partner makes the change in the Studio or the code.
You own it; you choose who runs it. You own the code — standard, modular Laravel that follows Laravel conventions — synced to your own GitHub repository. Hand it to your own developer or a development partner to deploy to your own Laravel Cloud account (or anywhere) — our step-by-step guide walks through it. And when our modules improve, the update is synced to your repository, ready to deploy — keeping a system current is included in Studio plans. How running it works →
What's already built
Every one of these is a finished module — not a line on a roadmap. Each is already running in production with real park data, and each ships with its own automated test suite that proves the rules actually hold: that a seven-night minimum can't be booked for six, that a changeover clean is raised the moment a guest checks out, that a leaving guest's extras can't walk out unbilled. You're getting software that's been proven, then tailored to your site — not a prototype we start writing after you've paid.
| The job | What it does | What you tell us |
|---|---|---|
| Bookings | Availability with clash detection, minimum stays, changeover days and seasonal pricing — plus confirmation emails | Your pitch list, your seasons and dates, your nightly rates, your minimum-stay and changeover rules |
| Pitchup.com sync | Takes Pitchup bookings without double-selling August. Your live availability is pushed to Pitchup, ring-fenced by a cap you set — they can never sell a pitch you don't really have. Their bookings, changes and cancellations land in your diary automatically, and every sync is logged so a broken feed is impossible to miss. Prefer not to hand over an API key on day one? There's a calendar-feed fallback | Your Pitchup account works as-is — just which pitch types to release to them, and how many |
| Arrivals & housekeeping | Today's arrivals and departures, check-in and check-out at the gate, and a cleaning board — checkout automatically flags the pitch for cleaning | Nothing extra — it works from your bookings |
| Extras | Electric hook-ups, firewood, bike hire, dog stays — priced per night or per item, attached to the stay, and turned into an invoice in one click when the guest leaves | Your extras catalogue and prices, and which are charged per night |
| Seasonal pitches | Annual licences with instalment plans, a list of who's fallen behind, and renewals due before the season ends — ready for a mail merge | Your seasonal fee, how many instalments you offer, and how far ahead you chase renewals |
| Invoicing & debtors | Draft invoices, batch runs, payments, a live debtors list and per-customer statements | Your payment terms and invoice details |
| Guest email | Confirmations, reminders and letters through your own email provider, with every send logged | Your wording and your sender address |
There's more on the shelf when you need it: a waitlist for the fully-booked August weekend, memberships with door access control if you run a gym or leisure block, and an audit trail that records every booking, payment and cancellation across the lot.
It already works together
These aren't six separate products with six logins. The arrivals board reads your bookings. Checkout flags the clean. A departing guest's unpaid extras — the bike hire, the dog — become an invoice on your debtors list in one action, so nothing walks out of the gate unbilled. In our live demo data that exact flow has already happened: a guest checked out, and their £30 of extras is sitting on the billing screen as an issued invoice.
Work that runs without being asked
Everything above happens while someone's in the office. We also build in work that doesn't wait to be asked — it runs on a schedule, or fires off the back of an event. The changeover-morning worklist drawn up before the office opens. Balances chased ahead of arrival day. A seasonal instalment that's fallen behind flagged and the reminder sent. A cancelled peak-week pitch offered straight to the waitlist.
And it knows where to stop: anything irreversible — refunding a deposit, cancelling a booking — waits for a person to say yes, and every action is recorded: what ran, when, for whom, and who authorised it. Drive it yourself in the guided demo, or read why this has to live inside your software →
It's your system to plug into
Every module comes with two ways in: a screen your staff use, and an API. An API is simply a doorway into your system that other software is allowed to use, with no person retyping anything. It's why the same booking engine behind your office screen can sit behind the booking form on your public website — a guest picks their dates and a real booking drops straight into your diary, availability and all. That same doorway lets a mobile app, a spreadsheet, or the AI itself read and create bookings, with access controlled the way you decide.
That's why it's built this way. A booking system that's only a screen is a walled box: the day you want a website booking form or a link to some tool that doesn't exist yet, you're back to a vendor with a feature request. Because every module is driven through its API, your system is open from day one — your website, your app and your future tools all plug into the same system you already own, no rebuild required.
Tell us how your park runs
Tell us how your park runs in your own words and we assemble your system, run the tests, and you own it outright as a complete, working Laravel application. Your developer, or a Stellify partner, hosts and looks after it — and when our modules improve, the update is pulled in Studio and synced to your GitHub repository, ready to deploy — keeping a system current is included in Studio plans.
Your system is built on Laravel — the world's most popular PHP framework, used by companies like Currys, MKM, Apple, Nike, NASA and Pfizer.
Not quite your business? Tell us what you need and we'll say whether we can build it.