Connected to what the school already uses
Payments, bank feeds, accounting, e-invoicing, email and SMS — each configured with the school's own accounts, and more than one where a school runs more than one organization.
Nothing here is a re-seller arrangement: the accounts are yours, the keys stay on the server, and turning one off leaves the records it created behind.
For the office
What a secretary, a bursar or a head of year can do with it.
- Card payments — Stripe, with a separate account per organization
- Bank feeds — GoCardless, Ponto and TrueLayer
- Accounting — QuickBooks; e-invoicing — Peppol
- Email — Resend or your own SMTP; SMS — Spryng or Twilio
For whoever has to approve it
Where the data sits, who can read it, and what it connects to.
- Keys are held server-side and never reach the browser
- Each integration is per organization, so two entities keep two sets of credentials
- Webhooks are signature-verified; failures are visible rather than silent
Questions we are asked
- Is there an API?
- The database is PostgreSQL with a REST layer, and your data is exportable at any time. A published public API is on the roadmap rather than shipped.
- Can we self-host?
- The system is built to run on plain Docker against self-hosted Supabase. Talk to us about what that involves.
See it with your own school's data
Sixty days free, no card up front — or open a ready-made demo school and click around it first.