Product workspace for Apache CamelOpen source

Build Camel workflows like a product, not a pile of route files.

Start from templates, design visually, inspect EIPs and components, autosave drafts, and create versions when the flow becomes worth keeping.

Visual

Canvas + code editing

Stable

Autosave and version history

Reusable

Templates and starters

Camel Studio

From starter to versioned workflow

Synced

Start from template

REST to Bean Response

System

Workflow structure

Authoring

Version history

Drafts autosave. Important states become explicit versions.

Stability

Safer load, parse and reopen flows with recovery states.

Core product

Everything around the workflow, not just the canvas

Studio

Visual authoring

Edit Camel routes through a canvas that understands structural operators like choice and doTry.

Code

YAML round-trip

Move between visual and code modes while keeping the stored workflow format predictable.

Templates

Template-driven starts

Use system starters and your own saved templates as repeatable starting points.

Library

Metadata browsing

Inspect EIPs and Components with dedicated library views instead of guessing field shapes.

Workflow loop

Start, shape, validate, version

Cameleon is strongest when the workflow is treated like a product artifact: you start from something solid, iterate safely, and checkpoint meaningful moments instead of trusting ad-hoc files.

1. Start from a template

Pick a practical starter from the template library instead of starting from an empty canvas every time.

2. Explore the building blocks

Browse EIPs and Components with metadata-first details before inserting them into a workflow.

3. Shape the route visually

Use authoring-safe structures, filtered placeholders, and inline validation while editing.

4. Create versions

Autosave keeps the draft safe. Version history captures the milestones that matter.

Where to begin

Jump into the real product surface

The fastest path is to open the app, pick a template, and let the studio guide the structure instead of building route YAML from scratch.

Open source

Product direction stays visible in the code

Cameleon is built in the open and shaped around real workflow authoring problems: editor trust, route structure, templates, versioning, and library discoverability.