Alpha Features

This page lists the latest Alpha features supported by RudderStack. Reach out to the RudderStack Product team to get access before using them in production.

Alpha features list

Data Governance

• CLI-based data governance
• Copy Tracking Plans across workspaces
• Rudder CLI tool

Sources

• Kafka source

Reverse ETL

• Manage SQL models using Rudder CLI

The following sections explain each of these Alpha features in more detail.

CLI-based data governance

You can now manage your Data Catalog and Tracking Plans as code. See the demo and check out the documentation to learn more about this feature.

With this feature, you can bring the same rigor and process to your Data Catalog and Tracking Plans that you apply to your application code, ensuring consistency and quality in your data collection strategy.

CLI-based workflows are a key focus area for the Product team, so please reach out with questions and feedback.

Copy Tracking Plans across workspaces

The RudderStack team is actively working on a number of features that will help you version control Tracking Plans within the context of a full development workflow. In the meantime, we’ve built an basic feature you can use to copy Tracking Plans across workspaces in the RudderStack dashboard.

There are two options for copying a Tracking Plan:

1. Copy as a new Tracking Plan: This will copy the Tracking Plan as a net new Tracking Plan in the target workspace. Any new events and properties will be copied into the the Data Catalog of the target workspace.
2. Copy and replace an existing Tracking Plan: This will replace an existing Tracking Plan and connect the migrated plan to the same sources. The original Tracking Plan will be kept and renamed.

Use Option 2 with caution

This is an alpha feature — the action cannot be rolled back.

Reach out and the team can enable this feature for you.

Rudder CLI tool

The Rudder CLI tool is a part of RudderStack’s CLI-based Tracking Plans Management feature. It lets you manage your Tracking Plans and Data Catalog as code, providing a complete command-line interface for working with your YAML-defined tracking plan configuration.

See the Rudder CLI tool documentation for more information.

Kafka source

This feature is available in production.

The Kafka Source enables you to ingest messages from a Kafka stream directly into RudderStack. This can be useful for:

• Applying data governance for behavioral event data.
• Streaming Kafka messages to out-of-the-box cloud integrations.

If you’re interested in streaming data from a system like Kafka, RedPanda, or other messaging queues into RudderStack, reach out to discuss your use case.

You can test this source today — reach out to enable the integration for your workspace and see the Kafka Source documentation for usage and more details.

Manage SQL models using Rudder CLI

You can now use Rudder CLI to manage your Reverse ETL SQL model sources through a Git-based workflow. It lets you store your SQL model configurations as YAML files in Git repositories, and use standard Git workflows to collaborate on any changes.

See Manage SQL Models using Rudder CLI for more information.

Questions? Contact us by Email or on Slack