Book a demo
Pricing
Enterprise only

Self-hosted. On-premise.

HDL Commerce* is delivered as a package, with Git and CI/CD flows for the latest updates. You govern, own and operate your stack. Choose to develop with us, or to carry on alone on top of the platform.

Talk to us Division of responsibility

The platform as a package.

What is delivered

The core

  • Container images for every service
  • A Helm chart and a Compose file for setup
  • Databasee schema and migrations
  • Admin, API and job execution
  • Versioned releases with a changelog

Frontend

  • Solaris Boilerplate as source code
  • Storefront, checkout and account
  • CMS blocks and global components
  • Build and deploy steps for your environment
  • End-to-end tests for the purchase flow

Operations & pipelines

  • A Git repo with a release branch on your side
  • Ready-made CI/CD pipelines
  • Health checks, metrics and log formats
  • Backup and restore procedures
  • An upgrade guide per major version

* Self-hosting covers HDL Commerce with the modules in your contract. Services that depend on our own data sources — such as the HDL Search API — are still called as a cloud service.

Git & CI/CD

Updates arrive as code, not as a maintenance window.

01A release is published

A new version is tagged in our upstream repo with a changelog and migration notes.

02A pull request to you

The change lands as a PR in your repo. You see exactly what changes before anything runs.

03CI runs the tests

Unit tests, migrations and end-to-end tests against the purchase flow run in your pipeline, in your staging.

04You deploy

Once you approve, it rolls out to production through your own release process.

.github/workflows/deploy.yml 
// Your pipeline, our steps as building blocks
jobs:
  test:
    steps:
      - uses: hdl-commerce/verify-migrations@v2
      - uses: hdl-commerce/e2e-checkout@v2
  deploy:
    needs: test
    steps:
      - run: helm upgrade hdl ./chart \
          --values ./env/prod.yaml \
          --set image.tag=${{ github.sha }}

Who does what.

Division of responsibility

Area You Us Servers, network and capacity Ja— Databasee operations, backup and restore Ja— Deploying to production Ja— Monitoring and alerting Ja— The platform's code and releases —Ja Upstream security updates —Ja Migration scripts and upgrade guides —Ja Your own code on top of the platform JaOptional Theme development and design JaOptional Second-line support —Ja

The responsibilities are written into the contract. If you would rather we took operations too, the cloud option on the pricing page is the same platform, without the self-hosting commitment.

Option A

Develop with us

Our team works in your repo, in your pipelines

A shared backlog and release planning

We take responsibility for upgrades between majors

An architecture review before major changes

Option B

Develop it yourselves

Your team or your agency builds on top of the platform

Full access to source code, API and hooks

We review your integration design on request

Developer support and access to upstream releases

The model can change over time. Many start with us on the project and take over maintenance themselves after launch.

Environment

Run where you already run.

The platform is container-based and runs on Kubernetes, on virtual machines or in your own data centre. No tie to a particular cloud provider.

Runtime
Kubernetes 1.28+ or Docker hosts with Compose
Database
PostgreSQL 15+ with point-in-time recovery
Cache & queue
A Redis-compatible cache and a queue for background jobs
Sök
OpenSearch or Elasticsearch
Media
S3-compatible object storage
Outbound
HTTPS to payment, shipping and ERP integrations
Environments
At least staging and production, ideally one per developer
values.prod.yaml 
# The services in the package
services:
  api:        { replicas: 3 }
  admin:      { replicas: 2 }
  worker:     { replicas: 4 }   # job execution
  indexer:    { replicas: 2 }
  storefront: { replicas: 3 }

data:
  postgres: 'postgres://…'
  redis:    'rediss://…'
  search:   'https://opensearch…'
  media:    's3://hdl-media'

observability:
  metrics: 'prometheus'
  logs:    'json'
  traces:  'otlp'

Cloud agnostic.

Run wherever you want to run

HDL Commerce is cloud agnostic. We have customers on AWS, Azure, Google Cloud and Kepler Cloud. We host on Kepler Cloud in Falkenberg, with our data centre supplier Glesys.

Kepler Cloud

Our own hosting, in Falkenberg with Glesys. A Swedish data centre and a Swedish supplier.

We host here
AWS

Customers in production on EKS with RDS, ElastiCache and OpenSearch Service.

Customers in production
Azure

Customers in production on AKS with Azure Databasee for PostgreSQL and Blob Storage.

Customers in production
Google Cloud

Customers in production on GKE with Cloud SQL and Cloud Storage.

Customers in production

Your own cloud provider requires an enterprise contract. On other plans we host the platform on Kepler Cloud.

Enterprise only

Self-hosting requires an enterprise contract — because it assumes an operations team on your side, a CI/CD process to plug the releases into, and shared responsibility for upgrades. If what you need is control over data, the cloud option already offers data storage within the EU.

Questions about self-hosting.

Common questions

Do we get the platform's source code?+

You get the package with the services, the database schema, the migrations and the frontend code, plus a repo with a release branch. The terms for further use are governed by the licence in your contract.

What if we skip several versions?+

The migrations run in order, so upgrading is possible, but majors have their own guide. We recommend taking patches continuously and minors at least quarterly.

Can we modify the platform's code?+

Your own additions go on top of the platform through the API, hooks and custom modules, which keeps upstream releases takeable. Changes to the core are handled as a separate agreement.

How does support work?+

We answer for the platform’s code and for second-line support. First line towards your users and operations in your environments sit with you, unless agreed otherwise.

Do all integrations work self-hosted?+

Yes, provided your environment can reach the integrations’ endpoints. Services built on our own data sources are called as a cloud service.

Can we move from cloud to self-hosted later?+

Yes. It is the same platform and the same data schema, so the move is a migration of data and configuration — not a fresh start.

Where do you host the platform yourselves?+

On Kepler Cloud in Falkenberg, with our data centre supplier Glesys. If you want to sit in another cloud that works — AWS, Azure and Google Cloud are used by customers today, on enterprise contracts.

Enterprise

Go through your stack with us.

We look at your environments, your pipelines and your operations organisation, and settle the division of responsibility before anything is signed.