Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
Platform · 17 of 18

Many sellers, one server

Host multiple sellers and their stores on a shared WebStore installation with a central console and clear boundaries.

01

A shared engine, separate sellers

A single WebStore server can host several sellers and their stores while the administration console stays central.

02

Boundaries matter

Decide what is shared, such as infrastructure, and what is not, such as catalog ownership and order access.

03

Operational savings

Shared infrastructure reduces the cost of maintaining many small installations, but it raises the importance of permissions.

Multitenancy is a governance choice

The technical ability to host many sellers is only half of the decision. The other half is the operating agreement: who may see which data, who resolves disputes and how a tenant is removed.

Review role definitions with the same care as the catalog model. A shared server makes permission mistakes more visible and more costly.

When a separate installation is better

If a seller requires isolated infrastructure, unusual release timing or a separate security boundary, a dedicated installation may be the simpler answer. Multitenancy is a good fit for standardised storefronts under common governance.

In practice
  • Write the tenant agreement before the first migration.
  • Define data ownership and exit procedures.
  • Review roles and permissions at tenant onboarding.
  • Monitor per tenant usage so one store does not starve the others.

Related capabilities

Primary sources

Reference shelf

Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.

  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • SQL Server Database engine documentation and editions.
  • OData The open data protocol used by the WebStore services layer.
  • NuGet Package distribution used by the .NET client and samples.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • OWASP Application security guidance and cheat sheets.
  • W3C Web standards for markup, accessibility and internationalization.
  • GitHub Source hosting and issue tracking for .NET projects.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
  • Open Source Initiative License review and the open source definition.
Next step

Put this capability against your own catalog

The useful test is a real assortment, a real market and a real order. Bring those to a conversation rather than a generic feature list.