> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt. For full content including API reference and SDK examples, see https://learning.postman.com/llms-full.txt.
# Simulator commands
Postman Simulator is available on Postman Solo, Team, and Enterprise plans. For more information, see the [pricing page](https://www.postman.com/pricing/).
This topic covers simulator commands for the [Postman CLI](/docs/postman-cli/postman-cli-overview/).
## `postman simulate run`
You can use the `postman simulate run` command to start a [local mock server](/docs/design-apis/mock-apis/local-mock-servers) with a simulation applied to it. This enables you to observe how your service responds to disruptions and performance constraints. With simulations, you can identify and fix issues before deploying to staging or production.
The command runs the simulator configuration file that defines the mock server and selected scenarios for simulating real-world conditions.
Add this command to your CI/CD script to run your service against simulated dependencies. This enables you to catch issues related to latency, errors, and rate limits before changes are deployed. Once running, your service or external tests can send requests to the mock server URL and observe the responses with the simulated conditions applied.
To run a collection with a simulation, use the `--simulate` option with the [`postman collection run` command](/docs/postman-cli/postman-cli-collections/#postman-collection-run).
To create a simulation and apply it to a mock server, see [Simulate real-world conditions in Postman](/docs/design-apis/simulate-conditions).
### Usage
```bash
postman simulate run .sim.yaml
```
The path to the `.sim.yaml` configuration file.
### Example
```bash
postman simulate run postman/simulations/.sim.yaml
```