> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/get-started/concepts/project-modes.md). # Project modes Every project is in one of two modes: * **Production** — calls hit live mobile networks and produce real results. Billed traffic. * **Sandbox** — calls are intercepted by IDlayr and produce simulated results based on the phone number you pass. No carrier traffic, no billing. Mode is set at project creation and is not changed in place. To move from sandbox to production, create a separate production project. This keeps test traffic and live traffic visibly separate in analytics and approvals. ## How sandbox works In sandbox mode, the last digits of the phone number you submit drive the simulated behaviour. This lets you test all response paths — match, no-match, errors, edge cases — without needing real devices or real carrier coverage. For the full per-product MSISDN/IP suffix maps and the platform-specific testing notes, see [Sandbox testing](/get-started/sandbox-testing.md). Each product page also has its own **Testing in sandbox** section with the product-specific table. ## What sandbox does and doesn't simulate **Simulates:** * Successful and failed verifications * Specific error codes (e.g. `mno_not_supported`, `ip_msisdn_mismatch`) * Callback delivery * Timing of state transitions **Does not simulate:** * Real device-to-carrier signal paths. On iOS, the SDK can be configured to allow Wi-Fi in sandbox; on Android, sandbox testing is currently supported on emulators only. * Real-world latency variance. * Actual MNO behaviour. Sandbox responses follow the spec; production responses depend on the carrier's actual behaviour at the time. ## When to use which Use sandbox for development, CI integration tests, and demonstrating flows to internal stakeholders. Move to production only after the use case has gone through approval and you've confirmed coverage for your target audience. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.idlayr.com/get-started/concepts/project-modes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.