Per-tenant storefront deployment
Each merchant's storefront runs as its own isolated deployment on their own domain. Nothing in the customer-facing experience indicates a shared platform underneath.
commerce · beta
CoralStore
Multi-tenant commerce with per-tenant storefront deployment: every merchant runs an own-branded shop on a shared commerce engine.
Overview
A commerce platform built around five surfaces: a merchant admin panel, a customer-facing storefront, a platform super-admin, the commerce API itself and the integration layer. The decision that shapes the architecture is deployment topology — data stays in one central PostgreSQL instance with row-level tenant isolation, while each storefront is deployed as its own isolated container bound to the merchant's custom domain. A provisioning service raises a storefront when a store is created, binds the domain and pulls theme configuration and catalogue from the central API. Storefronts hold no state of their own, so the isolation is real without the data fragmenting across instances.
Specifications
- Audience
- commerce
- Platforms
- Web
- Status
- beta
- Built with
- NestJS + Next.js
Capabilities
Central data, row-level isolation
Every table carries a tenant identifier and isolation is enforced at row level within a single PostgreSQL instance, so operations and reporting stay manageable while tenants remain separated.
Automated provisioning
Creating a store triggers a provisioning service that raises the storefront deployment, binds the tenant domain and pulls theme configuration and catalogue from the commerce API. Storefronts are stateless by design.
A commerce engine, not a theme
Products, categories, cart, orders, customers, payments, reviews, pages, themes, settings and statistics are first-class modules of the API rather than features of a storefront template.
Turkish payment and logistics providers
Integrations target the payment and shipping providers merchants in Türkiye actually use, rather than treating local providers as an afterthought to an international default.
An AI layer across the console
Dedicated AI, copilot, retrieval and shopbot modules cover content generation, merchant assistance, catalogue search and customer-facing conversation, served through CoralMeshAI.
Connected to the marketplace channels
DükkanAI keeps the marketplaces a merchant also sells on in sync with the same catalogue, so the owned storefront and the marketplace presence share one source of truth.
Others in this line
Portfolio products serving the same audience.
Engineered independently. Priced transparently.
No per-seat licensing, no vendor lock-in, no unpredictable invoicing. Our teams are available to scope an evaluation for any product in the portfolio.