Every service commerce needs.
Extend without limit.
A comprehensive set of services ships out of the box, each owning its data and scaling on its own. Add your own the same way, authored by AI, by hand, or both, and they join the same gateway and event backbone with no re-platform.
This comprehensive set of services ships out of the box. New services slot onto the same gateway and event backbone, authored by AI, by hand, or both, with no re-platform.
One gateway
A single REST surface under /api fronts every service, shared by all five storefronts, the admin and external integrations.
A comprehensive service suite
Catalog, pricing, inventory, cart, order, payment, customer, search, CMS and media, reviews, engagement and commerce-core all ship out of the box, each owning its data. Add your own the same way.
Event backbone
State changes flow through Kafka via a transactional outbox and relay, with no dual writes. Any read model rebuilds by replay.
Checkout saga
A distributed saga across order and inventory reserves stock, compensates on shortage, and only then persists the order.
Multi-store routing
Every request carries X-Base-Site-Uid. The backend resolves the base store and catalog version and scopes catalog, pricing and content.
Two deployment shapes
Run the modular monolith (one deployable) or the fully composable build (service-per-deployable). One platform, either shape.
The service suite is just the start
The platform is built to grow, not to be replaced. Add new capabilities and whole services three ways, each joining the same gateway, events, admin and observability.
Authored by AI
Describe the capability and AI agents build the service end to end, with its tests and documentation, the way the platform itself was built.
Built by hand
Your engineers add services the conventional way, against clear contracts and the same event backbone. No lock-in, no magic.
Hybrid
Let AI scaffold and your team refine, or the reverse. Direction stays with humans, breadth comes from AI.
Two shapes, one platform
The same API and data model ship in two forms. Migrate between them with the strangler pattern, so storefronts never break.
Modular monolith
One deployable and one schema. The fastest way to run the whole platform, ideal for a single team that wants every capability without operating a fleet of services.
Fully composable
Service per deployable, schema per service, integrated over events. Teams own and scale capabilities independently, and any read model rebuilds by replay.