How to Use the RudderStack Config Generator

Step-by-step guide on using the RudderStack Config Generator to set up your self-hosted Control Plane.

RudderStack's Control Plane manages the configuration of your sources and destinations.

For more information on the Control Plane, refer to RudderStack's architecture.

The easiest way to manage these configurations is through RudderStack's self-hosted Control Plane. It is free, requires no setup, and has some advanced features like Live Events Debugger and Transformations.

However, if you want to self-host these configurations, you can use the open-source RudderStack Config Generator to set up your Control Plane. You can then manage the source and destination configurations locally by exporting to or importing them from a JSON file.

Setting up the Config Generator

Before setting up the Config Generator, make sure you have RudderStack installed locally. You can find the instructions for setting up RudderStack in the Install and Set Up RudderStack guide.

Make sure you have Node.js installed before setting up the Config Generator.

In order to set up the RudderStack Config Generator, navigate to the folder where you have installed RudderStack.

Then, run the following commands in the specified order:

  1. cd utils/config-gen

  2. npm install

  3. npm start

The Config Generator can be accessed at http://localhost:3000 by default.

On successful setup, you should be able to see the following UI:

Control Plane set up using Config Generator

Exporting Workspace Configuration

After adding the required sources and destinations in the dashboard shown above, you can export your workspace configuration by simply clicking the EXPORT button.

For more information on adding sources and destinations in RudderStack, refer to the How to Add a Source and Destination in RudderStack guide.

The configuration is then exported and saved as a JSON file. This workspace configuration is required to start the RudderStack server.

To read the workspace configuration from the exported JSON file, you can update the config variables configFromFile and configJSONPath in config.yaml.

For more information on these variables, check out the Configuration Parameters guide.

Starting RudderStack with the Workspace Configuration File

For RudderStack to pick up the exported workspace configuration file, please follow the steps below:


If you are running RudderStack on Docker:

  • Open rudder-docker.yml.

  • Uncomment the volumes section under backend service. Replace <absolute_path_to_workspace_config> with the path of the downloaded workspace configuration JSON file.

  • In the environment section under backend service, uncomment the environment variable RSERVER_BACKEND_CONFIG_CONFIG_FROM_FILE=true.

Native Installation

For a Native RudderStack Installation:

  • Open .env file.


  • Also add RSERVER_BACKEND_CONFIG_CONFIG_JSONPATH=<absolute_path_to_workspace_config>. Replace <absolute_path_to_workspace_config> with the path of the downloaded workspace configuration JSON file.

Developer Machine Setup

If you have set up RudderStack on a developer machine:

  • Open config/config.yaml. Look for configFromFile and configJSONPath under [BackendConfig].

  • Set configFromFile to true and set configJSONPath to the path of the downloaded workspace configuration JSON file.

Using RudderStack Config Generator for Device Mode Destinations

To know more about the difference between Cloud mode and Device mode in RudderStack, read the RudderStack connection modes guide.

RudderStack's web, Android and iOS SDKs expect the source configurations and the associated device mode destination configurations for initialization.

By default, RudderStack SDKs fetch the source configuration from

What is the Control Plane URL?

Since the RudderStack SDKs need the source configuration and RudderStack's Data Plane or the SDKs are not aware of it by default, you must serve the configuration on your web servers and point the SDKs to the same. This configuration must be available at <CONTROL_PLANE_URL>/sourceConfig

To do so, follow these steps:

  • Set up your Control Plane using the RudderStack Config Generator by following the steps here.

  • Go to the Config Generator UI and export the source configuration by clicking the EXPORT SOURCE CONFIG button, as shown below:

  • Host the exported file on your own server at /sourceConfig. Provide the base URL of your server that is serving this file in SDK initialization code snippet:

    • JavaScript SDK: Instructions here.

    • Android SDK: Instructions here.

    • iOS SDK: Instructions here.

    • Flutter SDK: Instructions here.

RudderStack SDKs fetch the configuration by appending the /sourceConfig path to the base URL provided above.

  • The SDKs will fetch the config from <CONTROL_PLANE_URL>/sourceConfig.

Shown below is a sample of the exported source config:

"source": {
"config": {},
"id": "1im8yfXQsocRBGcQLXAaq5M8dYV",
"name": "test-JS",
"writeKey": "1im8yk2sz8oyHVCGVqViSNfKVDF",
"enabled": true,
"sourceDefinitionId": "1TW48i2bIzEl1HPf825cEznfIM8",
"deleted": false,
"createdAt": "Mon Oct 12 2020 16:51:54 GMT+0530 (India Standard Time)",
"updatedAt": "Mon Oct 12 2020 16:51:54 GMT+0530 (India Standard Time)",
"sourceDefinition": {
"id": "1TW48i2bIzEl1HPf825cEznfIM8",
"name": "Javascript",
"displayName": "Javascript",
"category": null,
"createdAt": "2019-11-12T12:39:19.885Z",
"updatedAt": "2020-06-18T11:54:06.114Z"
"destinations": [
"id": "1im927dBatOkbj1oPCV5JntGMj7",
"name": "test-HJ",
"enabled": true,
"config": {
"siteID": "dd41289"
"destinationDefinition": {
"config": {
"destConfig": {
"web": [
"defaultConfig": [
"secretKeys": [],
"excludeKeys": [],
"includeKeys": [
"supportedSourceTypes": [
"id": "1SxbQXdfQ2NzIdqNO3GceshF4V0",
"name": "HOTJAR",
"displayName": "Hotjar",
"createdAt": "2019-10-31T07:49:37.450Z",
"updatedAt": "2020-09-05T10:02:39.744Z"
"metadata": {
"version": "1.0.2"


For a self-hosted environment, how to get the Control Plane URL?

To use the Control Plane URL to initialize your SDKs, follow these steps:

  • Set up the RudderStack Config Generator.

  • Go to RudderStack Config Generator UI and export the source config from the source details page by clicking the EXPORT SOURCE CONFIG button.

  • Host the exported file on your own server such that the config is available at <CONTROL_PLANE_URL>/sourceConfig.

This solution assumes that you have already set up RudderStack locally and are hosting your own RudderStack backend (Data Plane).

Contact Us

In case you come across any issues while setting up or using the RudderStack Config Generator, please feel free to contact us. You can also start a conversation on our Slack channel.