Identity and access
Authenticated sessions, service-side authorization, plan entitlements, and restricted administrative actions.
Security at GridMango
Protection designed around validation work.
GridMango combines identity controls, tenant-aware authorization, encrypted protocol credentials, and operational safeguards to protect customer accounts and validation data.
Controls across the customer data path.
Data boundaries
Row-level policies, least-privilege grants, and account-scoped access separate customer data and privileged operations.
Credential protection
OCPP and OpenADR 3 credentials are encrypted in server-created AES-256-GCM envelopes. Private keys remain server-side.
Operational safeguards
TLS, rate limits, security headers, request validation, usage ceilings, and logs reduce abuse and support investigation.
Security architecture
GridMango is a multi-page web application hosted on Netlify, with server-side functions for privileged operations and Supabase for authentication, database services, and account state. Stripe handles payment data and subscription lifecycle events.
The browser receives only public configuration and short-lived authenticated session credentials. Service-role credentials, Stripe secrets, webhook secrets, encryption keys, and protocol private credentials are restricted to server-side environments.
Identity and access
- Protected tools and account actions require an authenticated session.
- Backend functions revalidate identity and plan access rather than relying on browser controls.
- Administrative operations require explicit role checks and create audit evidence.
- Database row-level security and least-privilege grants enforce account and service boundaries.
Data and credential protection
Traffic is encrypted in transit using TLS. Customer records and saved artifacts are accessed through account-scoped authorization paths. Sensitive OCPP and OpenADR 3 connection secrets are encrypted at the application layer before storage using separate server-held encryption keys.
Public browser keys are not privileged keys.
The Supabase browser key identifies the project and is public by design. Security depends on row-level policies, grants, backend authorization, and rate controls. Privileged service keys are never intentionally exposed to the browser.
Operational safeguards
- Rate limits and bounded usage ceilings protect authenticated and public endpoints from abuse.
- Request validation rejects malformed payloads and constrains file, device, and execution volumes.
- Operational logs and support reference codes help investigate failures without returning internal stack details to users.
- Security headers reduce common browser risks, and dependencies are reviewed as part of platform maintenance.
Billing and transaction integrity
GridMango uses Stripe Checkout rather than collecting complete payment card details directly. Checkout creation uses durable attempts and idempotency controls to reduce duplicate sessions and charges after interrupted requests. Signed webhook events are deduplicated and reconciled to account state.
Shared responsibility
Customers are responsible for protecting their user accounts, managing access within their organization, securing connected test endpoints, rotating credentials when exposure is suspected, and reviewing validation outputs before operational use.
GridMango supports QA, simulation, and validation. It does not replace a customer’s production control system, regulatory process, cybersecurity program, or operational approval procedure.
Incident response and reporting
Suspected security events are investigated, scoped, and remediated using available operational and audit evidence. Please do not include active credentials, production secrets, or sensitive customer datasets in an initial report.
Security contact[email protected]
Submit a report