Demo Docs Pricing Start Get free accessFree access
COMERS · SELF-HOSTED

Run Comers Core in your own infrastructure

Keep the operational Core and its data in infrastructure your organization controls, while selected Comers platform and AI services remain available through controlled connections.

// 01 · DEPLOYMENT CHOICE

One Core. Two ways to run it.

Managed and self-hosted are two deployment choices around the same Comers Core — not two different products.

Managed

Comers operates the environment.

COMERS MANAGED ENVIRONMENT
Comers Core
Self-hosted

Core runs in infrastructure controlled by your organization.

YOUR ENVIRONMENT
Comers Core
SAME CORE OrdersProductsSupplyWarehouseShippingMessagesIntegrations

Deployment changes. The operating model does not.

// 02 · DATA LOCATION

Keep operational data where you want it to live.

When Core runs in your environment, the operational data it handles — orders, products, supply, inventory, messages and shipments — can remain inside infrastructure your organization controls.

Your ecommerce operation does not have to move wholesale into somebody else’s runtime environment.

YOUR ENVIRONMENT
Comers Core · OPERATIONAL DATA
Orders
Products
Supply
Inventory
Messages
Shipments
Operational history

DATA CIRCULATES INSIDE THE BOUNDARY

// 03 · CONNECTED ARCHITECTURE

Self-hosted does not mean disconnected.

Core can stay with you while selected shared Comers services remain connected — so self-hosted never has to become a permanently isolated fork.

CUSTOMER ENVIRONMENT
Comers Core
RUNS HERE
Operational services
LIVES HERE
Operational data
COMERS SERVICES · SELECTED
ACCESS
Identity / access
Sign-in and access capabilities provided by Comers.
PLATFORM
Platform services
Selected shared capabilities of the Comers platform.
AI
Comers AI capabilities
AI capabilities connected where enabled for your deployment.

Conceptual view. Which services connect, and how, depends on the deployment.

Keep the boundary. Keep the ecosystem.

// 04 · SAME PRODUCT

Self-hosted is a deployment model, not a second product.

The same operational domains, working as one connected context — wherever Core runs.

COMERS CORE
managed · self-hosted
01
Orders
02
Supply
03
Products
04
Listings
05
Warehouse
06
Shipping
07
Messages
08
Support
09
Returns
10
Integrations

Your infrastructure should not require a different Comers.

// 05 · MORE CONTROL

Fit Core into the infrastructure standards you already operate.

01
RUNTIME ENVIRONMENT

Core runs inside infrastructure controlled by your organization.

02
DATA LOCATION

Operational data handled by Core can remain inside that environment.

03
NETWORKING

Fit the deployment into your own networking and access model.

04
OPERATIONS

Use your organization’s infrastructure, monitoring, backup and operational practices where applicable.

05
ARCHITECTURE

Integrate Comers into a broader enterprise architecture instead of forcing everything into one vendor-hosted environment.

// 06 · WHEN SELF-HOSTED MAKES SENSE

For organizations that need more control over the operating environment.

If none of these describe you, managed Comers is likely the simpler choice.

01
You already operate infrastructure

Your technical team already owns production systems and operational standards.

02
Data location matters

You need tighter control over where operational commerce data is stored.

03
Comers must fit your architecture

You want the operational platform to become part of an existing system landscape.

04
You have your own operational standards

Networking, backups, observability and access are already governed by internal practices.

// 07 · OPERATING MODEL

More control also means more responsibility.

Self-hosted is not maintenance-free. Running Core in your environment moves part of the operational work to your team.

CONCEPTUAL VIEW
MANAGED
COMERS
Environment + Core operation
SELF-HOSTED
CUSTOMER
EnvironmentInfrastructureLocal operations
COMERS
ProductPlatform servicesUpdates / agreed services

The exact responsibility model depends on the deployment and commercial agreement.

// 08 · YOUR DEPLOYMENT MODEL

Choose the operating model that fits your organization.

Neither is the better one in general. Self-hosted is for organizations that actually need it.

COMERS-OPERATED
Managed
  • Lower infrastructure ownership
  • Comers-operated environment
Comers Core IN BOTH
YOUR ENVIRONMENT
Self-hosted
  • Infrastructure controlled by your organization
  • More operational control
  • More customer-side infrastructure responsibility

FAQ

Questions about self-hosted Comers

Is self-hosted a different edition of Comers Core?

No. Self-hosted is a deployment model for Comers Core, not a separate reduced product. Exact functionality can still depend on plan, version and connected services.

Where does operational data live?

Core runs inside infrastructure controlled by your organization, allowing operational data handled by Core to remain inside that environment.

Can self-hosted operate completely disconnected from Comers?

Do not assume so. Selected platform, identity or AI capabilities may require controlled connectivity to Comers services, depending on the deployment.

Can we use managed Comers instead?

Yes. Comers Core is designed to support both managed and self-hosted deployment models.

Does self-hosted automatically provide regulatory compliance?

No. Compliance depends on the complete deployment, configuration, organizational processes and the requirements that apply to you.

SELF-HOSTED COMERS

Keep Core where you want operational control.

If your organization needs its own environment for ecommerce operations and data, let’s talk about the right Comers deployment model.