What you can rely on, and what happens when something breaks
A golf platform earns trust on the Saturday morning when the tee sheet has to work, the pro shop has to take payment, and nobody has time for an outage. Reliability is a commitment we publish and stand behind, not a marketing adjective. Here is the uptime we commit to, how the platform is built to hold it, and exactly how we communicate when something does go wrong.
Reliability in club software is two things: how rarely the system is down, and how honestly you are told when it is. Plenty of vendors are vague about both. We publish a formal uptime commitment in our Service Level Agreement, back it with service credits, and run a public status page so a problem is something you can see and track rather than something you have to phone in to discover.
The platform commits to 99.95% monthly uptime for all paid plans. Underneath that number is a stack built for it: a modular architecture on PostgreSQL and Redis, real-time error tracking and uptime monitoring with automated anomaly alerts, and tenant isolation so one club's load or incident does not become another's. The performance targets sit alongside the availability target: page loads under one second at the 95th percentile and API responses under 200 milliseconds.
When there is an incident, communication is the product. Active incidents show on a public status page and, where they affect the application, a banner inside the platform itself. Security incidents are classified, contained, and communicated within 72 hours per GDPR, with affected clubs notified directly. We would rather tell you early and plainly than manage the optics.
The outcome for your club
99.95% uptime commitment
A formal monthly uptime target for all paid plans, written into the Service Level Agreement and backed by service credits when we miss it.
Service credits, not excuses
If monthly uptime falls below the threshold, eligible plans receive service credits on a published schedule. The commitment has teeth.
Public status page
Real-time service status is published openly, so an incident is visible and trackable rather than something you have to call to confirm.
Real-time monitoring & alerts
Error tracking, uptime monitoring, and automated anomaly alerts mean problems are usually detected and worked before most clubs notice them.
Tenant isolation
Every club's data and load is isolated, so one tenant's incident or traffic spike does not cascade into another club's Saturday morning.
Honest incident communication
Active incidents show on the status page and, where relevant, in an in-app banner. Security incidents are communicated within 72 hours per GDPR.
What's included
Common questions
What uptime does Links Meridian commit to?
Links Meridian commits to 99.95% monthly uptime for all paid plans. The commitment is written into our Service Level Agreement, calculated as total minutes in the month minus downtime, and backed by service credits when we fall short.
What happens if you miss the uptime target?
Eligible plans receive service credits on a published schedule when monthly uptime falls below the committed threshold. The exact tiers are set out in the Service Level Agreement, and credits are requested within 30 days of the incident.
How do you communicate during an outage?
Real-time service status is published on a public status page, and during active application incidents a banner appears inside the platform itself. You can see and track an incident rather than having to phone in to find out what is happening.
How is the platform built to stay reliable?
The platform runs a modular architecture on PostgreSQL and Redis with real-time error tracking, uptime monitoring, and automated anomaly alerts. Tenant isolation keeps one club's load or incident from affecting another. Performance targets are sub-second page loads at the 95th percentile and sub-200-millisecond API responses.
What about security incidents specifically?
Security incidents are classified, contained, and communicated within 72 hours in line with GDPR requirements. Affected clubs are notified directly with the details of the incident, an impact assessment, and the remediation steps. See our security page for the full posture.
Run your club on a platform that publishes its promises
99.95% uptime, a public status page, and honest incident communication. Free 30-day trial, your data imported as part of onboarding.