> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/getting-started/environments.md). # Environments SameSystem is a cloud-based SaaS platform, and customers normally operate in the production environment. For customers with more extensive integration requirements, SameSystem also offers the option of having a dedicated staging environment. ### Staging environment A staging environment provides a separate SameSystem environment that can be used for developing and testing integrations without affecting the customer's production environment. Staging environments are typically intended for larger customers with multiple or more complex integrations where having a dedicated environment for integration development, testing, and validation provides significant value. Typical use cases include: * Developing and testing new integrations * Testing changes to existing integrations * Validating API requests and data mappings * Integration and acceptance testing before deploying changes to production * Testing changes involving multiple connected systems The staging environment is separate from production and should not be considered an exact real-time copy of the production environment or its data. ### Availability and pricing Staging environments are offered as an additional service and are not included as standard with a SameSystem subscription. A one-time setup fee applies when establishing the environment, followed by a monthly fee to cover the additional hosting and infrastructure costs. Please contact your SameSystem representative for information about availability and current pricing. ### Do I need a staging environment? For many integrations, a dedicated staging environment is not necessary. Development and testing can often be performed using agreed test data and appropriate integration procedures in dedicated test departments. We generally recommend considering a staging environment when your organization has multiple integrations, complex integration flows, extensive testing requirements, or a need to validate changes independently from production. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.samesystem.dev/getting-started/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.