Environments

Environment Overview

Every Simply360-powered app uses the production environment by default. Staging and Development are optional, separately controlled environment add-ons; they are not automatically available just because a team or integration can use production.

Environment	Simply360 app	API base URL	MCP server URL	Availability
Production	https://hq.simply360.app	https://api.simply360.app	https://api.simply360.app/v1/mcp	The default environment for a Simply360-powered app.
Staging	https://staging.simply360.app	https://api.staging.simply360.app	https://api.staging.simply360.app/v1/mcp	A paid add-on or an included benefit of a specific offer.
Development	https://dev.simply360.app	https://api.dev.simply360.app	https://api.dev.simply360.app/v1/mcp	A separate, limited developer-preview add-on or approved beta grant.

Staging Access

Staging is the customer-facing authoring and acceptance environment for teams that have the Staging add-on. A team can use it to configure and test portable changes with synthetic or curated test data before an approved release is promoted to production.

The add-on is enabled for the team, but access is granted to individual people. After staging enrollment and validation are complete, a Team Admin chooses which Team Admins and Team Users can enter staging. A production membership by itself does not grant staging access.

Development Access

Development is for early work against rapidly changing Simply360 code. It is primarily used by Simply360 engineering, internal QA, test automation, and approved design partners. Development access is separate from Staging: buying or receiving Staging does not also grant Development.

External Development access is limited and normally time-bound. It requires a named owner, use case, expiration, and approval. Use Staging for normal customer acceptance testing unless Simply360 has specifically enabled Development for your app.

Credentials and Data Are Environment-Specific

• Create API keys and OAuth client registrations in the environment where they will be used. A production credential must not be reused against Staging or Development, and credentials from a non-production environment do not authenticate to production.
• Keep separate environment variables or secrets for each environment. Do not select an endpoint by silently falling back from one environment to another.
• Portable configuration uses the same public simplyId values when it is promoted between environments. Environment-local credentials, memberships, bindings, and operational data are not promoted as configuration.
• Use synthetic or explicitly curated data in Staging and Development. Do not assume production records are copied into either environment.

Request Non-Production Access

Use Developer Feedback to ask about the Staging or Development add-on for your Simply360-powered app. Include the team and app name, the environment you need, the Team Admins or Team Users who need access, and what you plan to test. Do not include API keys, OAuth client secrets, access tokens, or production record data.

Configure a Client

Choose one environment and use its API, MCP, Simply Login, and browser endpoints consistently. The TypeScript SDK, CLI, and MCP Server guides show the environment-specific configuration for each client.