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
| What | Production | Sandbox |
|---|---|---|
| Kentro OS (API keys, permission groups, storefronts) | https://kentro.app | https://kentro.cc |
| Channel API | https://apis.kentro.live/channel/v1 | https://apis.kentro.dev/channel/v1 |
| Store API | https://apis.kentro.live/store/v1 | https://apis.kentro.dev/store/v1 |
| Authentication (bearer tokens, buyer sign-in) | https://apis.kentro.live/auth | https://apis.kentro.dev/auth |
| Kentro Pixel collector and browser SDK | https://pixel.kentro.live | https://pixel.kentro.dev |
| Kentro Pixel management API | https://apis.kentro.live/pixel/v1 | https://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
| Production | Sandbox | |
|---|---|---|
| Tenants and data | Live tenants with their real orders, invoices and payments | Test tenants and the data their users create |
| API keys | Created in Kentro OS at https://kentro.app | Created in Kentro OS at https://kentro.cc |
| Releases | The current release | The 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: trueon a Channel API write runs it in full, answers what it would have produced withX-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: historicalloads 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: stagingordevelopmentgetpk_test_public keys; production properties getpk_live_keys. See the Pixel quickstart. - Questions about sandbox access go to [email protected].
What differs
- Hosts:
.devinstead of.live, andkentro.ccinstead ofkentro.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.
Updated about 12 hours ago
Did this page help you?

