RudderStack Docs – Use Profiles IDE with Rudder AI

Profiles: Profiles IDE Quickstart

Mon, 01 Jan 0001 00:00:00 +0000

This guide walks you through launching Profiles IDE and making your first changes to a Profiles project.

Prerequisites

A RudderStack workspace with Profiles enabled
A warehouse connection configured in your workspace as a destination
Either an existing Profiles project or plans to create a new one

Tip: If you’re new to Profiles, you can ask Rudder AI within the Profiles IDE to explain concepts as you work, or see the Profiles documentation for more information.

Launch Profiles IDE

You can launch Profiles IDE whether you’re creating a new project or editing an existing one.

For existing projects

Open your Profiles project in RudderStack.
Click Edit with Copilot.

If you have a previous Profiles IDE session, you will see options to continue that session or create a new one. For more information, see Session management.

For new projects

In your RudderStack workspace, navigate to Profiles.
Click Create Project.
Choose the option to build with Rudder AI.

Set up your development environment

When launching the IDE, you need to specify a warehouse output location for development work. Rudder AI writes outputs here while you build and test separately from your production schema — this ensures your IDE experiments don’t affect production data.

Explore the IDE

Once the session launches, you see a development environment with three main areas:

Chat panel: Converse with the Rudder AI assistant
File explorer: Browse and open project files
Editor: View and edit code, configuration files

Rudder AI has context about your warehouse schema, existing project structure, and Profiles best practices.

Make your first changes

Try asking Rudder AI to help with a common task:

Some example prompts are listed below:

Adding an id stitcher model: “Build an id stitcher model with user_id, email, and anonymous_ids as identifiers”
Adding a single feature for an existing project: “Add a feature that calculates last purchase date”
Exploring the current project: “Show me a list of all the current features”

Rudder AI automatically generates or modifies files based on your request. Review the changes in the editor, and ask follow-up questions to refine the code.

Save and publish your work

All changes you make are tracked automatically in Git:

Save: Commits your changes to a development branch
Publish: Pushes your changes to the deployment branch

For your first session, click Save to commit your changes, then Publish when you’re ready to deploy them.

See Profiles IDE Version Control to learn more about Git workflows, session management, and team collaboration in Copilot.

Help and support

See the FAQ guide for common questions, or ask Rudder AI directly — it can explain Profiles concepts and troubleshoot issues as you work.

See more

Guide	Description
Use Profiles IDE with Rudder AI	Use the Profiles IDE powered by Rudder AI to build, run, and debug your RudderStack Profiles projects
Profiles IDE Version Control	Understand how Profiles IDE uses Git to track changes, manage sessions, and enable team collaboration
Understand Rudder AI Context	Understand what context Rudder AI has access to, including warehouse information, project files, and configuration details
Rudder AI Security and Compliance in Profiles IDE	Learn about Rudder AI’s security model, data access scope, and privacy guarantees when building Profiles projects
Profiles IDE FAQ	Answers to common questions about using Profiles IDE with Rudder AI

Profiles: Profiles IDE Version Control

Mon, 01 Jan 0001 00:00:00 +0000

Profiles IDE uses Git to track all changes to your Profiles project. This guide explains how the Git workflow works, how to manage sessions, and how to collaborate with your team.

Every time you work in the IDE, you’re working in a Git branch. When you create a new session, a new development branch is created for your work. When you continue an existing session, you pick up where you left off in that same branch.

This Git-native approach means all your changes are versioned, and you can collaborate with teammates using standard Git workflows like pull requests and code review.

Save vs. publish

Profiles IDE distinguishes between saving work in progress and publishing changes to production:

Save: Commits your current changes to your development branch. Your work is saved, but not yet deployed. You can continue iterating in the same session.
Publish: Pushes your committed changes from your development branch to the deployment branch. Once published, your changes go live in your Profiles project.

Session management

When you launch the IDE from an existing project, you see the following options:

Continue session
Create new session

A new session is created automatically if you’re launching it for the first time in a project.

Continue session

Continues working in your existing development branch. Use this when you want to pick up where you left off — your uncommitted changes, file state, and Git history remain intact.

Sessions may time out after extended inactivity. If this happens, you can resume your session from the profiles setting page, by entering the IDE once again. Your saved work will still be available.

Create new session

Starts fresh by creating a new development branch from your deployment branch.

Creating a new session permanently discards any changes not published from your previous session. Make sure to publish your work before starting a new session.

Use this when you want to:

Pull the latest changes from the deployment branch, for example, after a teammate published changes
Start with a clean slate

Collaboration

Profiles IDE supports team collaboration through Git workflows. Each team member works in their own development branch, and changes are integrated through pull requests.

Raise pull requests

When you’re ready to publish your changes, you can raise a pull request from your development branch to the deployment branch. This allows teammates to review your code before it goes live.

To raise a pull request, you need to have your Profiles project connected to your repository. You can configure this in your project settings.

Conflict handling

If multiple team members publish changes to the same files, you may encounter merge conflicts. Here’s how you can handle them:

If there are no conflicts: If your changes don’t overlap with others, the last published change adds to the deployment branch automatically.
If there are conflicts: If there are conflicts, you’ll need to resolve them before publishing. The recommended approach is to raise a pull request from your development branch, review and resolve conflicts, then merge the pull request in GitHub.

Git repository ownership

Even if you don’t connect your own Git repository, Profiles IDE still uses Git internally to track changes. However, connecting your own GitHub repository is strongly recommended for the following reasons, especially once your projects are live:

Pull request workflow: You can raise PRs for team review before changes go live
Full Git history: Git tracks all changes in your repository with proper commit messages
Audit trail: See who made what changes and when
Backup and portability: You own your project code
Save without Publish: You can save your changes without publishing, and preserve the development branches in your git remote

Tip: Go to your Profiles project settings to connect a GitHub repository.

Branch naming convention

Profiles IDE uses a specific branch naming pattern for development sessions: <username>_dev_<hash>. This helps identify which branches belong to which users and ensures branch names do not conflict.

You don’t need to manage these branch names manually — Profiles IDE handles this automatically when you create or continue sessions.

See more

Guide	Description
Use Profiles IDE with Rudder AI	Use the Profiles IDE powered by Rudder AI to build, run, and debug your RudderStack Profiles projects
Profiles IDE Quickstart	Launch your first session in Profiles IDE
Understand Rudder AI Context	Understand what context Rudder AI has access to, including warehouse information, project files, and configuration details
Rudder AI Security and Compliance in Profiles IDE	Learn about Rudder AI’s security model, data access scope, and privacy guarantees when building Profiles projects
Profiles IDE FAQ	Answers to common questions about using Profiles IDE with Rudder AI

Profiles: Understand Rudder AI Context

Mon, 01 Jan 0001 00:00:00 +0000

Rudder AI uses information about your warehouse, project structure, and configuration to provide relevant suggestions and generate code. This guide explains what context Rudder AI has access to during your session.

Warehouse information

Rudder AI can access your warehouse data through the profiles connection configured while entering the IDE session. It starts with information about schemas where your event data is stored, and can discover additional tables and columns as needed while building your Profiles project.

This warehouse access helps Rudder AI suggest appropriate models, features, and queries based on your actual data structure.

Project files

Rudder AI can see all files in your Profiles project, including:

Models: Identity stitching logic and entity definitions
Features: Feature definitions and calculations
Configuration files: Project settings and warehouse connections

Customer context

For projects created through the new Profiles IDE, Rudder AI generates context files automatically in the project folder. These files contains information about your company and what your Profiles project might be used for — essentially a template to guide Rudder AI’s suggestions.

This file is saved in your Git repository and persists across sessions.

Tip: Edit the context markdown file to better reflect your specific use case, business requirements, and data structure. The more accurate this context, the more relevant Rudder AI’s suggestions become.

What Rudder AI cannot see

Rudder AI’s access is scoped to your current Profiles project and connected warehouse.

Rudder AI cannot access data or configuration from other RudderStack workspaces within your organization. It only sees the specific Profiles project you’re working on.

For more details on security and isolation, see Rudder AI Security.

Profiles knowledge

Rudder AI understands RudderStack Profiles concepts, best practices, and configuration patterns. You can ask it to explain Profiles features, suggest implementation approaches, or troubleshoot issues — even if the information isn’t explicitly in your project files.

See more

Guide	Description
Use Profiles IDE with Rudder AI	Use the Profiles IDE powered by Rudder AI to build, run, and debug your RudderStack Profiles projects
Profiles IDE Quickstart	Launch your first session in Profiles IDE
Profiles IDE Version Control	Understand how Profiles IDE uses Git to track changes, manage sessions, and enable team collaboration
Rudder AI Security and Compliance in Profiles IDE	Learn about Rudder AI’s security model, data access scope, and privacy guarantees when building Profiles projects
Profiles IDE FAQ	Answers to common questions about using Profiles IDE with Rudder AI

Profiles: Rudder AI Security and Compliance in Profiles IDE

Mon, 01 Jan 0001 00:00:00 +0000

This guide explains Profiles IDE’s security model, access scope, and data privacy guarantees when building Profiles projects.

Overview

Profiles IDE is a web-based IDE hosted by RudderStack that includes an AI-powered chat interface to help you build Profiles projects.

Since Profiles functions as a semantic model builder for customer data, Rudder AI may need to query your data warehouse to provide relevant assistance. These queries may access tables containing personally identifiable information (PII) as stored in your warehouse.

Access control

This section explains Rudder AI’s access control policy while working in Profiles IDE.

Warehouse selection

When entering Profiles IDE, you configure a warehouse destination to be used for the profiles runs. Rudder AI inherits the permissions of the selected warehouse connection.

Tip: Follow the principle of least privilege when configuring warehouse credentials.

Grant read-only access to source data tables and write access only to Profiles output schemas.

What Rudder AI can access

Rudder AI operates within your selected warehouse connection’s permissions. If your warehouse credentials allow access to tables containing PII, Rudder AI can query that data to provide relevant assistance.

Warehouse isolation

Rudder AI can only access the warehouse connection you explicitly select. It cannot access other connections you may have configured, or other parts of the workspace.

Data privacy

This section covers details on the model provider used for Rudder AI and its data retention and PII handling policies.

PII handling

Unlike RudderStack’s AI chatbot in slack (Rudder AI), Rudder AI does not mask PII in the Profiles IDE. When Rudder AI queries your warehouse to answer questions, raw results, including any PII in those tables, are processed to generate responses.

Configure your warehouse connection permissions carefully — your warehouse credentials determine what PII Rudder AI can access.

AI model provider

Rudder AI uses foundation models (for example, Claude Sonnet) hosted on Amazon Bedrock to process your queries and generate responses.

According to AWS Bedrock’s data protection policies:

Your prompts and warehouse query results are not shared with third-party model providers (Anthropic, Meta, etc.)
Amazon Bedrock does not store your data
Data remains in the region where your RudderStack data plane is hosted
All data is encrypted in transit (TLS 1.2+)

What RudderStack collects

RudderStack collects Profiles IDE usage data for product improvement. Chat interactions and warehouse queries and responses are not collected.

See more

Guide	Description
Use Profiles IDE with Rudder AI	Use the Profiles IDE powered by Rudder AI to build, run, and debug your RudderStack Profiles projects
Profiles IDE Quickstart	Launch your first session in Profiles IDE
Profiles IDE Version Control	Understand how Profiles IDE uses Git to track changes, manage sessions, and enable team collaboration
Understand Rudder AI Context	Understand what context Rudder AI has access to, including warehouse information, project files, and configuration details
Profiles IDE FAQ	Answers to common questions about using Profiles IDE with Rudder AI

Profiles: Profiles IDE FAQ

Mon, 01 Jan 0001 00:00:00 +0000

This guide answers common questions about using the Profiles IDE with Rudder AI.

General

What is Rudder AI?

Rudder AI is an AI assistant that helps manage customers their RudderStack workspace. It is also available within the web app, in the new Profiles IDE.

Rudder AI helps customers in building their RudderStack Profiles projects. It works within a hosted development environment and understands your warehouse structure and project configuration to provide contextual guidance.

Do I need to know Profiles to use Rudder AI?

Not necessarily — Rudder AI can explain Profiles concepts and guide you through building projects. However, understanding basic identity resolution and entity modeling concepts will help you work more effectively.

Is Rudder AI available for other RudderStack products?

Currently, Rudder AI is available for building Profiles only.

It is also available as a Slack bot, with a different set of security and compliance requirements. See Rudder AI Security for more details

How is Rudder AI in Profiles IDE different from Rudder AI Slack bot?

Rudder AI in the Profiles IDE provides a development environment for building and editing Profiles projects, with full access to your warehouse data. Rudder AI Slack bot is a chat interface for debugging pipelines, troubleshooting errors, and answering setup questions, without warehouse access.

Use Rudder AI within the Profiles IDE when building or modifying Profiles projects. Use the Slack bot when investigating pipeline issues or understanding your workspace configuration.

Pricing and availability

How much does Rudder AI cost?

Rudder AI is currently in beta and included with your Profiles plan at no additional cost.

Sessions and workflow

How long do sessions last?

Sessions may time out after extended inactivity. If this happens, you can resume by going to the profiles setting page and click on edit project, then continue your session; your saved work will still be available.

Does Profiles IDE autosave my work?

Yes. Profiles IDE automatically saves changes in your session, even if you haven’t saved (committed) them. If your session times out or you close the browser, you can resume your session and continue where you left off with all your edits intact.

What happens to saved work that’s not published?

All the saved and autosaved changes are only in your current session until you publish them to your development branch. If you open a new session without publishing your work, Profiles IDE permanently discards the saved changes. If you own the project in your git repository, you can recover any saved changes from there as every save is pushed to your repository.

Can multiple people work on the same project?

Yes. Each person works in their own development branch. When publishing changes, make sure there are no conflicts with others’ work. If conflicts exist, resolve them by raising a pull request and merging in GitHub.

What happens if I create a new session?

Creating a new session starts fresh from your deployment branch and permanently discards any unpublished changes from your previous session. Make sure to publish your work before creating a new session.

Can I work on multiple features in parallel?

Each Profiles IDE session represents a single development branch. To work on multiple features in parallel:

In your Profiles project settings, connect your project to your GitHub repository.
When you save or publish in Profiles IDE, it automatically pushes changes to your GitHub repository.
Use the terminal in Profiles IDE to switch between branches with Git commands, for example, git switch feature-branch.

This allows you to manage multiple branches within the same Profiles IDE environment.

Git and version control

Do I need my own Git repository?

No, but it is strongly recommended that you connect your own GitHub repository.

Profiles IDE uses Git internally even if you don’t connect your own repository. However, connecting your GitHub repository enables pull requests, code review workflows, and gives you full control over your project history.

How do I connect my GitHub repository?

Go to your Profiles project settings and configure the GitHub repository connection.

How do I resolve merge conflicts?

If multiple team members publish conflicting changes, the recommended approach is to raise a pull request from your development branch to the deployment branch, review and resolve conflicts, and then merge the pull request in GitHub.

Security and privacy

Is my data secure?

Yes. Each Profiles IDE session runs in an isolated environment with scoped access to only your warehouse credentials and project files. Sessions are ephemeral and cleaned up after inactivity.

See Profiles IDE Security more information.

Can Rudder AI see data from other projects or workspaces?

No. Rudder AI access is limited to the specific Profiles project you’re working on and its connected warehouse.

See more

Guide	Description
Use Profiles IDE with Rudder AI	Use the Profiles IDE powered by Rudder AI to build, run, and debug your RudderStack Profiles projects
Profiles IDE Quickstart	Launch your first session in Profiles IDE
Profiles IDE Version Control	Understand how Profiles IDE uses Git to track changes, manage sessions, and enable team collaboration
Understand Rudder AI Context	Understand what context Rudder AI has access to, including warehouse information, project files, and configuration details
Rudder AI Security and Compliance in Profiles IDE	Learn about Rudder AI’s security model, data access scope, and privacy guarantees when building Profiles projects