Unlike many other mocking tools, Mockoon is a desktop application using a local Node.js server to avoid latency and the hassle of deploying through a remote service. You can read our getting started tutorial for an overview of how Mockoon works.
No, Mockoon can be run in most environments by regular non-privileged users.
Mockoon creates a local mock server running on Node.js and does not require internet access. The server is then made available on all local network adapters (localhost, 127.0.0.1, 192.168.x.x, etc.) on the port you define. If the machine on which Mockoon is running has open ports on the local network, other users will be able to access it.
No, you don't need an internet connection to use Mockoon. Everything runs locally.
No, you don't need to sign up or create an account to use Mockoon.
Yes, Mockoon has an official CLI that allows you to run all your mock APIs in any headless or automated environment: servers, CI, GitHub Actions, Docker containers, etc. A Docker image is also available on Mockoon's Docker Hub.
Yes, Mockoon has an official NPM package that allows you to run all your mock API servers in cloud functions and serverless environments: AWS Lambda, GCP Functions, Firebase Functions, etc.
Yes, Mockoon supports most of the OpenAPI specifications (v2 and v3) both for import and export. You can learn more on Mockoon's OpenAPI documentation page.
Mockoon application data and settings are stored in your operating system user data folder:
If you use the Windows portable version, your data will be stored next to the executable in a
./mockoon-data/storage folder. The
./mockoon-data folder also contains all the files necessary to run the application.
storage folder contains mainly two files: a
settings.json file with your application settings and preferences and an
environments.json file containing all your API mocks data. Starting with v1.16.0, your mock APIs are stored in separated files and can reside anywhere on your hard drive. After the migration to v1.16.0, the
storage folder will contain as many
environment-x.json files as you had mock APIs created in Mockoon. You can then move them elsewhere.
Yes. Since version 1.15.0, the desktop application uses a custom telemetry system collecting anonymous and basic usage data like session duration, country, operating system, application version, and number of environments. You can opt out of this telemetry system in the application settings. Starting with version 1.19.0, the desktop application is not using Google Analytics anymore.
None of your mock API data like route names, headers, bodies are collected.
No data or telemetry is collected when using the CLI.