Security
Designed for multi-tenant operations.
NearOps keeps organisations, engineers, customers, bookings, and payments separated with tenant-aware architecture and role-based access.
Organisation isolation
Every organisation's data — bookings, customers, engineers, payouts — is logically isolated at the row level.
Role-based access
Admins, engineers, and customers each see only what their role allows. No accidental leakage between teams.
Supabase Auth
Authentication is handled by Supabase Auth with secure session handling and best-practice token rotation.
Stripe-hosted fields
Payment fields are hosted by Stripe. Raw card data never touches NearOps servers.
Customer action tokens
Customer cancel and reschedule links use signed, single-purpose tokens that expire automatically.
Calendar disconnect
Engineers can disconnect Google Calendar at any time. Permissions are explicit and revocable.