Follow the guides in this section if you want to set up RudderStack in your preferred development environment.

The RudderStack backend is written in Go, with a simple React.js UI to manage your sources, destinations, and the connections between them.

Overview

Installing and setting up open source RudderStack involves the following steps:

  • Control Plane Setup: Setting up the control plane to manage your source and destination configurations.
  • Data Plane Setup: Setting up the data plane(backend) for RudderStack to track, process, and route the events.
  • Sending Test Events: Sending test events to verify your RudderStack installation.

FAQ

Do I need to sign up for an account to set up open source RudderStack?

Signing up for RudderStack Open Source is the easiest way to set up and manage your data pipelines. The web app is only used for source/destination configuration and does not have access to your data. It also provides a Live Events feature for debugging purposes, only for a limited time.

RudderStack does not persist any of your data.

However, if you do not wish to sign up for RudderStack and want to self-host the source/destination configurations, you can use the open source Control Plane Lite utility. To set up the RudderStack server (backend) in your own environment, follow the steps listed in the Data Plane Setup guide.

The control plane set up using Control Plane Lite does not have features like Transformations and Live Events.

What is a data plane URL? Where do I get it?

For routing and processing the events to the RudderStack backend, a data plane URL is required.

Refer to the RudderStack Architecture guide for more information the RudderStack data plane.

If you're using open source RudderStack, you are required to set up your own data plane in the preferred environment.

An open source RudderStack data plane URL typically looks like http:localhost:8080, where 8080 is the port where your RudderStack data plane is hosted.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

Contents