WORKFLOW MODEL
Executable GraphML
GraphML is the executable interchange format. The graph carries nodes, edges, routing outcomes and version identity across authoring and execution.
Product & features
A graph is the application’s behavior.
Ravenroot is a graph-governed backend workflow runtime. Teams author flows visually, exchange them as executable GraphML and run them through a controlled, observable engine.
ROUTING
Branch and rejoin
The baseline supports fan-out, outcome-based routing and basic correlated all/any fan-in. Advanced retry, quorum and distributed execution remain planned.
CATALOG
Typed building blocks
Standard behaviors include log, template, checked CEL transforms and decisions, JSON parse/path, delay and allowlisted HTTP requests.
AUTHORING
Visual editor
Load, edit and save workflows; create edges with pointer or keyboard; inspect the live catalog; test or run; and follow activity events.
OPERATIONS
Observable execution
The server publishes correlated activity through SSE and structured JSON logs. The UI projects active, completed, fallback and failed nodes.
PORTABILITY
Multiple delivery shapes
Use direct Java embedding, a self-contained JAR or OCI image, the CLI or the static browser UI. Version 0.6.1-alpha.1 publishes release assets, Maven modules and a server image.
No-code / low-code
Different contributors, one inspectable contract.
The palette makes composition approachable to functional specialists. GraphML, schemas, policies and runtime events keep the result reviewable by engineers. Ravenroot reduces the distance between roles; it does not remove the need for engineering.
01
Compose nodes
02
Configure contracts
03
Test or run
04
Observe events
Boundaries
Extension points are not bundled powers.
Ravenroot names its limits directly so a catalog entry is never mistaken for a configured capability.
Integrator supplied
Model and agent adapters
llm-prompt and agent are catalog extension points. The default distribution includes no ModelProvider or AgentRuntime; execution stops with a configuration error until an integrator deliberately supplies one.
Experimental
Programmable artifacts
The local artifact lifecycle is bounded and in memory. JavaScript execution also needs an integrator-provided OS sandbox supervisor and an explicit allowlist; the default distribution fails closed.
Current boundary: the standalone service defaults to SQLite; an optional PostgreSQL adapter provides shared durable state under documented lease, source and topology rules. Recovery verifies pinned definitions and manifests, and ambiguous effects follow explicit repeatability or reconciliation contracts. Ravenroot is not a generic connector catalog or a bundled autonomous-agent runtime.
Explore the contract
Move from capability to a running local evaluation.
The documentation separates current behavior, integrator-supplied seams and roadmap work. Start with the newest published prerelease or build the 0.7.0-alpha.1 development source.