Request carries its store
An x-store-slug header identifies the store.
Every product, order and customer row is scoped to its store by PostgreSQL row-level security. A bug or mistake in one brand cannot surface another brand’s data.
Isolation here is not a filter in the interface that a missing check could bypass — it is enforced in the database. Each request carries its store, and the database returns only that store’s rows.
An x-store-slug header identifies the store.
Row-level security returns only that store’s data.
Admin actions land in a per-store audit log.
No — it’s row-level security in Postgres, so it holds even if application code forgets a filter.
Only the stores they’re assigned to; a keymaster view sees all.
Pricing is on request.