Frequently asked questions

How does Mockoon mock API creation works?

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.

Does Mockoon need elevated rights to run?

No, Mockoon can be run in most environments by regular non-privileged users.

Does Mockoon work behind a company firewall?

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,, 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.

Does Mockoon require an active internet connection?

No, you don't need an internet connection to use Mockoon. Everything runs locally.

Do you need an account to create mock APIs?

No, you don't need to sign up or create an account to use Mockoon.

Does Mockoon offer a CLI?

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.

Is Mockoon compatible with OpenAPI?

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.

Is Mockoon free and/or open source?

Mockoon is 100% free AND open source (MIT license).

Where are my data stored?

Mockoon application data and settings are stored in your operating system user data folder:
  • Windows: c:/Users/xxx/AppData/Roaming/mockoon/storage
  • Linux: ~/.config/mockoon/storage
  • macOS: ~/Library/Application Support/mockoon/storage

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.

Mockoon's 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.

Learn more about Mockoon's data storage

Is the application collecting usage data?

Yes. Since version 1.15.0, we use a custom telemetry system collecting anonymous and basic usage data like number of users, number of sessions, session duration, country, operating system, application version, and number of environments. You can opt out of this telemetry system in the application settings.

We also use a basic Google Analytics setup that collects the usual data like sessions, OS, screen size, etc. It is also collecting some events happening in the application. A typical event includes the following JSON {category: 'delete', action: 'environment'}, {category: 'server', action: 'start' }, etc.
The application will prompt you to accept or refuse this data collection at the first launch. You can always enable or disable Google Analytics in the application settings.
We plan to remove Google Analytics in the future and only keep our privacy-friendly telemetry system.

None of your mock API data like route names, headers, bodies are collected.

No data or telemetry is collected when using the CLI.