Multi-tenant isolation
LiveEvery business row carries tenantId. API queries filter by tenant. Isolation is proven in e2e with a second shop login (owner@other.shop).
Trust center (lite)
Shop data is operational gold. Isolation, least privilege, and clear secret handling are non-negotiable for a long-term SaaS. This page describes current controls and roadmap — not a compliance certificate.
Controls
Live means in the multi-tenant product/demo. Roadmap is not claimed as production-complete.
Every business row carries tenantId. API queries filter by tenant. Isolation is proven in e2e with a second shop login (owner@other.shop).
JWT access tokens; dual-mode cookie + Bearer for app and automated tests. No secrets in client bundles.
Server-side roles (owner, advisor, tech, and related) with least privilege by default. Advanced RBAC deepens on Scale.
Sensitive mutations and repair-order stage changes write audit records for operator and compliance review.
Scoped, passwordless links for estimate decisions — not permanent customer passwords shared across shops.
Application-level tenant filters today; database row-level security hardening is roadmap for high-assurance tenants.
Enterprise packaging path for identity provider federation — not on Starter/Growth day one.
OpenAPI and operational export paths expand; formal DSAR automation jobs are roadmap.
This page describes architecture intent and current scaffold controls — not a SOC 2 attestation. Enterprise compliance packages will be contracted separately.
FAQ
No SOC 2 attestation is claimed on this site. Enterprise compliance packages are contracted separately when ready.
Request the access desk, open as owner@demo.garage, then owner@other.shop with the issued password. Data must not leak across tenants. Isolation is also covered in API e2e.
Local/dev uses Docker Postgres. Cloud path targets GCP-style deploy for production tenants; private GCP is an Enterprise option.