Internal site. Jolli authentication required to view.
Skip to Content
🚀 Getting StartedQuick Start

Last Updated: 3/19/2026

Quick Start

Get Feldera running locally with Docker in under 5 minutes. This guide will walk you through starting the service, accessing the Web Console, and creating your first pipeline.

Prerequisites

You’ll need Docker installed on your machine. If you don’t have it yet:

If you’re on Apple Silicon, we recommend enabling Rosetta  for x86/amd64 emulation.

You’ll also need a web browser such as Chrome or Firefox.

Start Feldera

Run the following command to start Feldera:

docker run -p 8080:8080 --tty --rm -it images.feldera.com/feldera/pipeline-manager:latest

This command will:

  • Pull the latest Feldera container image (first time only)
  • Start the Feldera Pipeline Manager
  • Expose the service on port 8080

Once the container downloads and starts, you’ll see the Feldera logo in your terminal. This indicates that the service is ready.

Access the Web Console

Open your web browser and navigate to:

http://localhost:8080

You should see the Feldera Web Console, which provides a graphical interface for creating and managing pipelines.

Create Your First Pipeline

Let’s create a simple pipeline to get familiar with Feldera:

  1. Click “New Pipeline” in the Web Console

  2. Name your pipeline (e.g., “my_first_pipeline”)

  3. Write some SQL in the editor. Here’s a simple example:

CREATE TABLE events (
    id BIGINT NOT NULL PRIMARY KEY,
    message VARCHAR
) WITH ('materialized' = 'true');
 
CREATE MATERIALIZED VIEW event_count AS
SELECT COUNT(*) AS total_events FROM events;

This creates a table to store events and a view that counts them.

  1. Click the Play button (▶) to start the pipeline

The pipeline will compile (this takes a moment the first time) and then start running. You’ll see the status change to “Running” in the interface.

Insert Some Data

With your pipeline running, let’s add some data:

  1. Open the “Ad-hoc query” tab in the Web Console

  2. Run an INSERT statement:

INSERT INTO events (id, message) VALUES
(1, 'Hello Feldera'),
(2, 'Second event'),
(3, 'Third event');
  1. Query the results:
SELECT * FROM event_count;

You should see the count of events you just inserted.

Observe Changes

Feldera continuously updates views as data changes. Try inserting more data:

INSERT INTO events (id, message) VALUES
(4, 'Another event');

Query the event_count view again, and you’ll see the count has been updated incrementally—Feldera didn’t recount all events, it just added 1 to the previous result.

Stop the Pipeline

When you’re done experimenting:

  1. Click the Stop button (■) in the Web Console
  2. This shuts down the pipeline and clears its state

To stop the Docker container, press Ctrl+C in the terminal where it’s running.

Alternative: Docker Compose

If you want to experiment with Kafka and other auxiliary services, you can use Docker Compose instead:

curl -L https://raw.githubusercontent.com/feldera/feldera/main/deploy/docker-compose.yml | \
docker compose -f - up

This brings up Feldera along with Redpanda (Kafka-compatible), Prometheus, and Grafana. You can enable specific services:

curl -L https://raw.githubusercontent.com/feldera/feldera/main/deploy/docker-compose.yml | \
docker compose -f - up pipeline-manager redpanda

Access the Web Console at the same URL: http://localhost:8080

Try the Online Sandbox

If you prefer not to install anything locally, Feldera maintains a free online sandbox  where you can try tutorials and demos. Note that pipelines are automatically shut down after 24 hours of runtime, and the deployment may be refreshed periodically.

What’s Next

  • First Pipeline: Learn how to create a complete data pipeline with SQL tables, views, and connectors
  • Pipelines Core Concepts: Understand the fundamental building blocks of Feldera pipelines
First PipelineCli Reference