Environments

Production and the sandbox: hosts, portals, what each environment holds, test data and what differs between them.

Kentro runs two environments: production, where tenants run their business, and the sandbox, Kentro's staging environment, for building and testing. Both run the same APIs, but they share no tenants, keys or data.

Hosts

WhatProductionSandbox
Kentro OS (API keys, permission groups, storefronts)https://kentro.apphttps://kentro.cc
Channel APIhttps://apis.kentro.live/channel/v1https://apis.kentro.dev/channel/v1
Store APIhttps://apis.kentro.live/store/v1https://apis.kentro.dev/store/v1
Authentication (bearer tokens, buyer sign-in)https://apis.kentro.live/authhttps://apis.kentro.dev/auth
Kentro Pixel collector and browser SDKhttps://pixel.kentro.livehttps://pixel.kentro.dev
Kentro Pixel management APIhttps://apis.kentro.live/pixel/v1https://apis.kentro.dev/pixel/v1

Kentro MCP connection details are on Kentro MCP.

A reachability check needs no credentials:

curl -s https://apis.kentro.dev/channel/v1/ping

The answer:

{ "ok": true, "service": "channel-api" }

What each environment holds

ProductionSandbox
Tenants and dataLive tenants with their real orders, invoices and paymentsTest tenants and the data their users create
API keysCreated in Kentro OS at https://kentro.appCreated in Kentro OS at https://kentro.cc
ReleasesThe current releaseThe same release train, one step ahead of production
  • Nothing is copied between environments. A production key is refused in the sandbox, and a sandbox key in production.
  • New API behavior reaches the sandbox first, which makes a sandbox run the place to catch a change before production sees it.

Test data

  • Create test documents through the API or in Kentro OS at https://kentro.cc: a sales channel, a few products, customers and orders cover most integrations.
  • X-Dry-Run: true on a Channel API write runs it in full, answers what it would have produced with X-Dry-Run: applied, and rolls everything back. It works in both environments, so it can validate payloads against production data without storing anything. See Channel API: Requests and responses.
  • X-Import-Mode: historical loads past documents without confirmation emails, packing slips, accounting exports or EDI documents.
  • A storefront answers the Store API only once it is published, in the sandbox as in production. Checkout runs through the payment provider the sandbox storefront is connected to: confirm it is a test account before placing orders.
  • Kentro Pixel properties created with environment: staging or development get pk_test_ public keys; production properties get pk_live_ keys. See the Pixel quickstart.
  • Questions about sandbox access go to [email protected].

What differs

  • Hosts: .dev instead of .live, and kentro.cc instead of kentro.app.
  • Credentials: each environment has its own keys, permission groups and tokens.
  • Release timing: the sandbox runs one step ahead of production.
  • Data: sandbox tenants hold test data only; no production record appears there.

🚧

Moving to production

Nothing carries over. Create the production API key and its permission group in the production tenant at https://kentro.app, switch every host, and walk the Go-live checklist.


Did this page help you?