@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
Operate every store from one place.
Organisation, members, roles and credits. The OS is multi-tenant by default. This page is that default made visible.Multi-store4 rolesOrg ledgerStudio perms
The numbers
What a plan opens
- Pro plan
- 1
- Max 5x plan
- 5
- Max 20x plan
- 20
- RBAC roles
- 4
store included
What the workspace is
An organisation holds stores. Members have one of four roles: owner, admin, member, viewer, plus studio permission overrides. Billing and credits sit on the organisation. The chat store picker and the dashboard switchers move between them without losing context.
Free is one sandbox store and zero agent credits. Pro starts at one production store. Studio permissions are separate from org RBAC. There is no cross-store workflow orchestrator.
What Workspace actually holds
- StoresEvery connected Shopify store under the org, with switcher and guardrails.
- MembersOwner, admin, member, viewer. Studio adds its own grants on top.
- CreditsOne org ledger, daily bonus where the plan allows, mid-stream hard cap.
- BillingStripe subscriptions and tax. Not an OAuth connector in the Bridge sense.
What a plan opens
Numbers from PLAN_LIMITS. Not marketing round numbers.
- StoresPro includes one store. Max 5x opens five. Max 20x opens twenty. Custom is negotiated.
- RolesOwner, admin, member, viewer. Studio sections open on their own permissions. A section someone cannot open does not render.
- CreditsIncluded credits match the plan price. Daily bonus per org. Pre-stream estimate and mid-stream hard cap keep a run inside the balance.
- SwitchersOrg switcher and store switcher in the shell. Multi-org store picker in the chat. Same tenant context everywhere.
Who needs Workspace
- AgenciesMany client stores, one login, role-scoped access.
- Multi-brand operatorsSeveral storefronts, one credit pool.
When to use it
- Use it whenWhen you run more than one store, or when more than one person needs scoped access to the same OS.
- Do not use it whenWhen you are alone on a single store and still exploring. Connect the store, use the chat. Come back when the team or the second brand arrives.
Tenant walls
- No silent cross-store runsWorkflows do not fan out across stores as a Features claim.
- RBAC is realViewer cannot approve writes. Studio sections still ask their own permission.
Limitations
What the feature does not do. Knowing beforehand costs less than finding out after.
- Pro is one store. Unlimited stores is not a Pro claim.
- A workflow run targets one store. Cross-store orchestration is not shipped.
- Free includes zero credits. The OS is visible. The agents are not free to run.
- Studio permissions are separate from the four org roles. Two people on the same team can see two different Studios.
Not here
- Cross-store orchestration as a productized Features surface.
The neighbouring features
Same family, same product surface.
How many stores do I get?Workspace
One on Pro, five on Max 5x, twenty on Max 20x. Custom is on request.
Can I hide Studio from someone?Workspace
Yes. Each Studio section has its own permission. A section they cannot open is absent, not greyed out.
Where did Multi-store go?Workspace
Here. Multi-store without roles and credits is half a workspace. This page is the whole thing.
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
A question that is not here?
Ask it, and it joins this page if it comes back.