Enterprise-grade by default.

Identity

Authentication is real, working, session-token based — opaque, database-backed sessions, not client-trusted JWTs. Every authenticated request carries a session token validated on the server for every call.

SSO

Single sign-on via OIDC-based identity providers, so access follows your organization's existing identity provider and offboarding process rather than a separate Spark ERP credential to manage.

MFA

Multi-factor authentication is a first-class part of the login flow — a login can return a challenge token requiring a second factor before a session is issued.

RBAC

Role-based access control extends down to record, field, screen, API, menu, report, print and workflow/approval permission types, plus named ACL templates and time-boxed temporary permissions for exceptions.

Tenant Isolation

Tenant boundaries are resolved from session/identity context on every request and enforced at the connection layer via per-tenant databases and schemas — see the Multi-Tenant Architecture page for the full model.

Encryption

Data in transit is protected with TLS. Sensitive credentials at rest — such as per-tenant storage backend credentials — are encrypted (AES-256-GCM), not stored in plain configuration.

Audit

A single platform-wide audit seam (entity-change events) captures field-level create/update/delete activity and version history across every module, rather than each module keeping its own ad hoc audit table.

Secrets

Secrets and credentials are never stored in application code or plain configuration — integration and storage credentials are encrypted at rest and scoped to the tenant that owns them.

API Security

The REST API is secured by the same session and RBAC model as the UI. Nothing in the product has UI-only access — every entity, page, form and workflow reachable through the UI is governed by the same permission checks through the API.

Infrastructure Security

The application layer is stateless, so it can be patched, scaled and replaced without correctness-bearing state living in any one instance — reducing the blast radius of any single compromised node.

Data Residency

Regional deployment means a tenant's data and compute can be kept in the region it was provisioned in, supporting data residency requirements alongside latency.

Backup

Each tenant database is backed up independently, so recovery for one tenant is isolated from every other tenant.

Disaster Recovery

Stateless compute plus isolated per-tenant databases means disaster recovery is a matter of restoring the affected tenant's data and repointing compute — not disentangling shared state across tenants.