For multi-location operators · One tenant per location
Twelve restaurants under one roof. Each location runs its own day-to-day on Grid. We see the whole network from one admin.
Chains, franchises, and multi-brand groups need each location to run on its own and the parent to see the whole network from one screen. Grid does both.
One parent. N locations. Real isolation.
Not workspaces, not folders, not permission overlays. Real tenants — each location with its own database scope, its own brand, its own workflows.
Parent admin · HQ
Downtown
Branded · isolated
cus_LcA1…Isolated tenant scopeRiverside
Branded · isolated
cus_LcB2…Isolated tenant scopeAirport
Branded · isolated
cus_LcC3…Isolated tenant scopeWestside
Branded · isolated
cus_LcD4…Isolated tenant scope- +8more tenants
Each location is a real tenant. Not a folder.
Every record at every location carries a tenant ID at the database boundary. Staff at one location can't see another location's data — even if they ask the AI assistant. The isolation is architectural, not policy.
Branded child UI per location.
- Per-location logo, colours, and login URL
- Local domain (e.g. `downtown.yourbrand.com`)
- Customer-facing emails sent from local domain
- Tenant scope enforced at the database boundary
- AI agents inherit the location scope automatically (F900)
One screen for the whole network.
Combined revenue, combined task velocity, combined pipeline, combined inventory. Roll the network up by location, region, brand, or any tag — and drill back down into the location with one click.
Parent-level roll-up reporting.
- Network revenue across every location
- Same-store sales comparisons week-on-week
- Task completion velocity by location
- Inventory levels rolled up by SKU across locations
- AI cost roll-up + per-location cap enforcement
One admin pane controls all of them.
Switch into any location from the command bar. Impersonate any user to debug a support issue. Every action is stamped in the location's audit log — the local manager sees exactly when HQ touched their data and why.
Cmd-K into any location. Impersonate to support.
- Cmd-K (Ctrl-K) opens location search
- Fuzzy match on location name, region, or brand
- Impersonation sessions logged to the location audit log
- Time-boxed by default; manual end at any moment
- Cross-location audit search at the parent
Local autonomy. Parent guardrails.
The parent sets the template — required fields, allowed workflows, brand rules, compliance requirements. Each location customises within those guardrails. Headquarters never has to micromanage; locations never feel handcuffed.
Policy at the parent. Practice at the location.
- Parent defines required fields and approval gates
- Locations customise their own workflows and SOPs
- Brand guardrails enforced (colours, copy templates, logo)
- Compliance fields locked at the parent (food safety, licensing)
- AI tool allow-list configurable per location
Per-location billing. Parent admin fee. No per-seat math.
Each location is its own Stripe customer, so franchise fees, intercompany billing, and divestiture all work cleanly. A failed payment at one location doesn't touch the network. Pause a seasonal location for the off-season without affecting the rest.
Stripe customer per location.
- Independent subscription per location
- Pause / cancel / renew a single location without touching siblings
- Failed payment at one location doesn't affect others
- Per-location AI budget with hard cap
- Bulk invoicing dashboard at the parent
Multi-location pricing
Priced per location, not per seat.
Flat parent admin fee covers the network roll-up, command bar, and audit search. Per-location pricing per tenant covers the local product, branding, and AI cap. Same tier serves chains, franchises, and multi-brand groups.
- Real per-location isolation
- Brand customisation per location
- Per-location AI cap
Questions multi-location operators ask.
Ready to run the whole network from one screen?
No credit card · 14-day trial · Cancel anytime