Skip to main content

Vendor Provisioning (Isolated Stacks)

Draft

This page is a stub. It captures the intended structure of the BoxNCase Platform documentation; the details are being written as the platform ships. Questions: [email protected].

Isolation model​

  • External vendors get their own stack: API, worker, PostgreSQL database, media bucket and dashboard. Nothing is shared with other vendors.
  • Internal vendors (BoxNCase-operated brands) run on the main stack, separated by channels, warehouses and permission groups.
  • Storefront hostnames are served from the wildcard storefront host; custom domains can be attached later.

Lifecycle​

  1. Vendor is created in the BoxNCase control plane.
  2. A payable Stripe account is required before an external vendor can launch.
  3. The provisioning worker creates the stack, applies migrations, seeds channels/warehouses and registers platform apps and webhooks.
  4. Readiness checks gate the launch (API reachable, dashboard login, webhooks acknowledged).
  5. The vendor receives dashboard credentials and their API endpoint.

What you get​

  • GraphQL endpoint: https://<vendor-api-host>/graphql/
  • Dashboard: https://<vendor-dashboard-host>/
  • Storefront: https://<vendor>.<storefront-wildcard-domain>/

Outline (to be written)​

  • Sizing and limits per stack
  • Backups and restore
  • Upgrades (Saleor Core version policy)
  • Decommissioning a stack