---
title: Operating modes
description: To prevent unwanted changes to the configuration, IG is by default in production mode after installation. Production mode has the following characteristics:
component: pinggateway
version: 2023.11
page_id: pinggateway:configure:operating-modes
canonical_url: https://docs.pingidentity.com/pinggateway/2026/configure/operating-modes.html
llms_txt: https://docs.pingidentity.com/pinggateway/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-09-19T08:48:14Z
superseded_by: https://docs.pingidentity.com/pinggateway/2026/configure/operating-modes.html
section_ids:
  production_mode_immutable_mode: Production mode (immutable mode)
  development_mode_mutable_mode: Development mode (mutable mode)
  switch_from_production_mode_to_development_mode: Switch from production mode to development mode
  immutable: Switch from development mode to production mode
---

# Operating modes

## Production mode (immutable mode)

To prevent unwanted changes to the configuration, IG is by default in production mode after installation. Production mode has the following characteristics:

* The `/routes` endpoint isn't exposed or accessible.

* Studio is effectively disabled. You can't manage, list, or even read routes through Common REST.

* By default, other endpoints, such as `/share` and `api/info` are exposed to the loopback address only.

  To change the default protection for specific endpoints, configure an ApiProtectionFilter in `admin.json` and add it to the IG configuration.

## Development mode (mutable mode)

In development mode, by default all endpoints are open and accessible.

You can create, edit, and deploy routes through IG Studio, and manage routes through Common REST, without authentication or authorization.

Use development mode to evaluate or demo IG, or to develop configurations on a single instance. This mode isn't suitable for production.

For information about Restrict access to Studio in development mode, refer to [Restrict access to Studio](../studio-guide/restrict-access.html).

## Switch from production mode to development mode

Switch from production mode to development mode in one of the following ways, applied in order of precedence:

1. Add the following configuration to `admin.json`, and restart IG:

   ```json
   {
     "mode": "DEVELOPMENT",
     "connectors": [
       { "port" : 8080 }
     ]
   }
   ```

2. Define an environment variable for the configuration token `ig.run.mode`, and then start IG in the same terminal.

   If `mode` is not defined in `admin.json`, the following example starts an instance of IG in development mode:

   * Linux

   * Windows

   ```bash
   $ IG_RUN_MODE=development /path/to/identity-gateway/bin/start.sh
   ```

   ```windows
   C:\IG_RUN_MODE=development
   C:\path\to\identity-gateway-2023.11.2\bin\start.bat %appdata%\OpenIG
   ```

3. Define a system property for the configuration token `ig.run.mode` when you start IG.

   If `mode` is not defined in `admin.json`, or an `IG_RUN_MODE` environment variable is not set, the following file starts an instance of IG with the system property `ig.run.mode` to force development mode:

   * Linux

   * Windows

   ```
   $HOME/.openig/env.sh
   ```

   ```
   %appdata%\OpenIG\env.sh
   ```

   ```bash
   export JAVA_OPTS='-Dig.run.mode=development'
   ```

## Switch from development mode to production mode

Switch from development mode to production mode to prevent unwanted changes to the configuration.

1. In `$HOME/.openig/config/admin.json` (on Windows, `%appdata%\OpenIG\config` ), change the value of `mode` from `DEVELOPMENT` to `PRODUCTION`:

   ```json
   {
     "mode": "PRODUCTION"
   }
   ```

   The file changes the operating mode from development mode to production mode. For more information about the `admin.json` file, refer to [AdminHttpApplication (admin.json)](../reference/RequiredConfiguration.html#AdminHttpApplication).

   The value set in `admin.json` overrides any value set by the `ig.run.mode` configuration token when it is used in an environment variable or system property. For information about `ig.run.mode`, refer to [Configuration Tokens](../reference/PropertyValueSubstitution.html#ConfigToken).

2. (Optional) Prevent routes from being reloaded after startup:

   * To prevent all routes in the configuration from being reloaded, add a `config.json` as described in the [Quick install](../getting-started/preface.html), and configure the `scanInterval` property of the main Router.

   * To prevent individual routes from being reloaded, configure the `scanInterval` of the routers in those routes.

     ```json
     {
       "type": "Router",
       "config": {
         "scanInterval": "disabled"
       }
     }
     ```

   For more information, refer to [Router](../reference/Handlers.html#Router).

3. Restart IG.

   When IG starts up, the route endpoints are not displayed in the logs, and are not available. You can't access Studio on <http://ig.example.com:8080/openig/studio>.