One dashboard for every Magento store you run
storeXstore connects to Magento and Adobe Commerce over the REST API and gives your whole team one place to work. Every product in the suite talks to the same store, the same customers and the same permissions.
Free to start. You pay only for AI usage.
Connect the store you already have
No migration, no replatform, no lock-in. Point storeXstore at your instance and keep everything where it is.
Magento and Adobe Commerce
Talks to your instance over the standard REST API with a bearer token, against the store view you choose.
Credentials encrypted at rest
Store credentials are encrypted with AES-256 before they are written, and decrypted only to make a call on your behalf.
As many stores as you run
Each store is an isolated tenant. Every record hangs off a store, and every query is scoped to one — there is no cross-store view by design.
Your brand, your domain
Pages publish to your own storefront. Customers stay on your domain and never see ours.
Built for teams that share a store
The person who writes the product copy is rarely the person who approves the invoice.
Seven roles, per store
Permissions are granted per store, not per account, so somebody can own one store and hold a narrow role on another at the same time.
Scoped, not shared, logins
Give an agency access to the one store they work on. Nothing else on your account becomes visible to them.
Written in four languages
The whole interface ships in English and in simplified, traditional and Hong Kong Chinese — not machine-translated at render time.
Built for a real catalog, not a demo one
Most tools are fine until a tenant crosses a few thousand rows. That is the point at which ours were designed to start.
Nothing loads everything
Every growable list — products, pages, orders, clients, invoices — is paged from the server. The browser never receives a whole catalog in order to filter it.
Search runs in the database
Typeaheads query the server with a bounded result set and cancel their own in-flight requests, so a slow answer can never overwrite a newer one.
Cursors, not page numbers
Paging is keyset-based, so it stays correct while records are being created underneath you and stays fast however deep you go.
The unglamorous parts, done properly
The work you only notice when somebody skipped it.
AES-256 at rest
Every stored credential and API key is encrypted before it touches the database.
Role-based access control
Every route establishes who you are and which store you may touch before it reads a single record.
Tenant isolation, enforced by tests
A guard test fails the build if a new store route is added without proving the caller belongs to that store.
Rate limiting by tier
Sign-in, general API, sensitive operations and AI calls each have their own budget, so one runaway script cannot starve the rest.
Cached, with expiry
Permission and lookup reads are cached at the edge and every cache key carries a lifetime, so nothing can go stale indefinitely.
Pooled connections
Database access runs through a pooler, so traffic spikes queue instead of exhausting the connection limit.
Or let somebody else run the Magento
storeXstore works with any Magento or Adobe Commerce instance, wherever it is hosted. If you would rather not operate one yourself, Stoily runs managed Magento with published pricing — point-of-sale, B2B and marketplace included — and storeXstore sits straight on top.