Product
How it's built
Version 15 October 2026. This page describes the technology behind the SquadPilot OS product. It is not the admin infrastructure console inside a club account.
Web application
The marketing site and the signed-in app you use in the browser are served from Vercel.
Data, sign-in, and jobs
The database, authentication, file storage, and server-side functions run on hosted Supabase. Access is isolated per club in the database.
Transactional email is sent through Resend. In development, messages go only to an allow-list of team addresses. Production is where real recipients are emailed.
Payments
SquadPilot's own subscription is charged on our Stripe account. Until go-live, that Stripe account stays in test mode. Each club connects its own GoCardless account for Direct Debit in the cashbook and its own Stripe account for holiday-camp card payments. There is no shared club payment token.
Security practices
Reimbursement and supplier bank details are encrypted before they are stored. Support sessions are time-limited, scoped, and audited. Secrets are not kept in the repository.
We do not claim ISO 27001, SOC 2, Cyber Essentials, or a published uptime percentage.