Built for clubs and management companies.
foreGolf runs as a single platform serving hundreds of clubs simultaneously, with bulletproof data isolation and the enterprise operations tooling a portfolio operator needs. Individual clubs get the benefits of shared infrastructure; management companies get the parent-child hierarchies they've always wanted.
What's in the box.
Row-level security
Every tenant-scoped table enforces RLS via current_setting('app.current_tenant'). Fails closed if tenant context is unset.
Parent-child hierarchies
Management companies configure portfolios of clubs with rollup reporting, shared templates, and cross-tenant membership if elected.
Per-tenant configuration
Dot-namespaced config keys, tenant-scoped defaults, and runtime override without redeploys.
Feature flags
Flag CRUD with per-tenant overrides, cached evaluation (60s TTL), bulk evaluation for page loads.
API keys
HMAC-signed keys, raw secret returned once at generation, rotation with 24-hour grace period, immediate revocation.
Webhook subscriptions
HMAC-signed deliveries, exponential backoff retry up to five attempts, auto-disable after ten consecutive failures.
Immutable audit log
INSERT-only, queryable by actor / action / resource / date, CSV export for compliance, 7-year retention for financial events.
Tenant provisioning
One-command provisioning: tenant record, default configuration, initial owner user, billing setup, and setup wizard primed.
RBAC + MFA
System roles are immutable, custom roles CRUD with permission ceiling enforcement, MFA available per user, JWT for sessions.
Database-per-tenant
An enterprise escape hatch when regulatory or contractual obligations require full physical isolation.
A closer look.
Multi-tenant done properly
Most "multi-tenant" SaaS in this category is a shared database with a tenant_id column and trust. foreGolf enforces isolation at the database level with row-level security, not application code. A bug in a query cannot leak data across tenants, because the database refuses to return it.
The management-company case
Portfolio operators — Troon, ClubCorp-style operators, private family offices with two or three clubs — get parent-child hierarchies, shared templates, rollup reporting, and consolidated billing. Each property stays its own tenant for operational clarity; the parent sees the portfolio.
Enterprise-grade operations tooling
API keys, webhook subscriptions, audit logs, feature flags, and tenant configuration are all first-class APIs with their own admin UIs. Your integrator, your auditor, and your platform team each see what they need. No one is digging through a database console.
One platform.
Every department.
See it in action.
Request a walkthrough tailored to your club — we'll show you the multi-tenant platform module end to end.