Skip to main content
Devset is a local-first workflow engine that puts you in control of testing your event-driven systems. Everything runs on your machine — no accounts to create, no cloud dependencies, no data leaving your environment. Whether you’re firing single messages, live-tailing Kafka topics, or orchestrating multi-step test scenarios, Devset gives you a complete toolkit that works against real brokers.

Introduction

Learn what Devset is, how it works, and why local-first matters for testing event-driven systems.

Quickstart

Get Devset running in under 5 minutes with Docker and send your first message to a broker.

Flow Builder Guide

Compose multi-step event pipelines visually on a drag-and-drop canvas.

API Reference

Explore the Workflow DSL engine API to drive Devset programmatically or from CI.

​
Get up and running

Follow these four steps to go from zero to running your first workflow.
1

Install Devset

Pull and start the Devset container with a single Docker command. Mount a named volume so your data persists across restarts.
docker run -p 8082:8082 -v devset-data:/data ghcr.io/devset-io/devset-ce:latest
2

Open the UI

Navigate to http://localhost:8082 in your browser. The Devset UI is served directly from the same port as the backend — no separate frontend process needed.
3

Connect a broker

Open Settings and add a Kafka or RabbitMQ connector. Point it at your running broker and save. Devset will validate the connection and make it available across all features.
4

Build your first workflow

Open the Flow Builder, create a new workflow, drag stages onto the canvas, and run it against your connected broker. Devset executes each stage in order and reports the results in real time.