Open Source · Composable · B2B Ecommerce

VELOX Developer Hub

VELOX connects your ERP, PIM and CRM directly to your webshop, without adding another system to maintain. Publish your existing product data online without duplication or extra overhead.

# Run the full VELOX stack locally

$git clone gitlab.com/velox-shop/velox-demo

$docker compose up

catalog, cart, checkout, search … up

storefrontlocalhost:3000

backofficelocalhost:3001

MCP endpoint:8460/…/v1/mcp

Native images, PostgreSQL-backed, OAuth 2.1 —read the quickstart →

Developer Hub

Get started with VELOX right now

Checkout the documentation or the source below or get your VELOX up and running in minutes. Quick start now.

Independent services

Each domain, from catalog and price to cart, order and search, is its own service with its own database and clear boundaries. An orchestration layer handles aggregation across them.

Integration without a fight

Connecting a CRM, marketing automation or an ERP is straightforward rather than a fight against the platform. Services are independently deployable and testable, with GitOps pipelines on Argo CD.

Built for a ten-year life

Java 25 and Spring Boot 4, compiled to GraalVM native images for fast startup and low memory. No Node.js on the critical backend path, and no build-up of technical debt.

Source Code

The full VELOX source is public on GitLab under the MIT licence. Read it, audit it, fork it.

View the repository →

Documentation

Project documentation is publicly available, including the API reference and integration guides.

Read the documentation →

Technology Stack

What VELOX is built on, and where the current improvement focus lies.

See the stack →

Service Versions

Supported services, current versions and lifecycle status for each release.

Check versions →

Interested to contribute?

Contributors are highly encouraged to join our cause.
Please contact us via the form below to get started.

Contact Us

Microservice Architecture

Principles
Single purpose - Each service should focus on single function and do it well.
Lose coupling - Direct strict dependencies between services should be avoided.
High cohesion - Each service should be standalone and self contained.

Learn more ➝

Architecture

Microservice Architecture

VELOX Architecture Diagram

Source: VELOX Documentation Project

Open the documentation →

Companies building on VELOX

zitadel logo by caos agmagnolia international ltd. logocaos ag logoconsus management consulting gmbh logo
quatico solutions ag logo