$ cat ./ROADMAP.md

what we're building. in the open.

An honest view of what's shipped, what we're working on now, and what's on the horizon. No fixed dates — we ship when it's right. Items and ordering may shift as we learn.

current_buildv0.2.x
shipped_items07
in_progress02
$ filter --theme=
# phase 01

shipped

07

engine foundation

coreCAR-35

engine extraction + ctx ports

engine pulled out of the monolith. ctx interface with ai, audit, and logger ports — and deliberately no db port. engine never imports sdk or platform code — it doesn't even depend on them.

shipped
v0.1
coreCAR-103

walker, flow dispatch, durable sleep

edge-driven workflow runtime. category=flow dispatch, delay node, and workflow.sleep wrapping temporal — workers can die mid-delay and the run resumes.

shipped
v0.1
coreCAR-134

engine primitives suite

edge-driven walker (reachable bfs), flow primitives (if_else, switch, parallel, join, fail), human-in-the-loop via signal + timeout race, decorator slots, cost channel, template grammar.

shipped
v0.1
sdkCAR-150

sdk + lifecycle events + sub-workflow

@flowget/sdk: thin temporal-client wrapper (submit, subscribe, cancel, signal, query). lifecycle stateevents emitted. runsubworkflow primitive via executechild.

shipped
v0.1
securityCAR-127

payload codec (sdk + aes-256-gcm)

payloadcodec option in the sdk plus a reference aes-256-gcm codec that encrypts at the worker edge with a customer-held key. opt-in per tenant.

shipped
v0.1
securityCAR-126

security baseline

lint blocks eval/function/vm. a redaction helper covers known secret patterns — tokens, jwts, urls — applied opt-in. activityfailure mapped to nodeerror with classification. security.md + private disclosure across our published packages.

shipped
v0.1
opsCAR-89

github packages publish pipeline

versioned publish chain for types, engine, cli, stdlib under @flowget. public-read with no token required, ready for the customer scaffold.

shipped
v0.1
# phase 02 · now

in progress

02

spec locked, implementation active

sdkCAR-151

subscribe protocol

two surfaces — sdk.subscribe (asynciterable) and workeroptions.onevent — both wrap the same temporal update streamevents handler. one primitive, two ergonomics.

in progress
~v0.5
coreCAR-156

definenode lifecycle + actor layer

authorize, validate, computecost, finalize, configure hooks on every node. actor layer separates engine wiring from customer code. spec locked after four review passes.

in progress
~v0.5
# phase 03 · next

planned

03

onboarding, primitives, tooling

dxCAR-153

zero-friction cli onboarding

npx create-flowget-app scaffolds a ready project → flowget-worker runs your nodes → submit workflows via the sdk. customer onboarding in a few commands.

planned
~v0.6
coreCAR-157

input scope + sub-workflow registry

execution input exposed as {{ input.* }} in template scope. stdlib subworkflownode with in-process child registry injection.

planned
~v0.6
dxCAR-124

workflow.json schema codegen

flowget schema emits a json schema for workflow.json so editors give autocomplete and validation without manual setup.

planned
~v0.6
# phase 04 · horizon

exploring

04

cloud, ai authoring, compliance

coreCAR-86

cloud control plane + byo worker

hosted control plane with worker running on customer vpc. multi-tenant ctx, auth handoff with signing-key rotation, cluster db cross-tenant safety, tenant isolation playbook.

queued
securityCAR-38

codec wire format + guardrail service

grpc wire with permanent v1 backwards compat. codec-server for temporal ui decrypt, manifest auto-push on connect. internal guardrail for admission control and abuse detection.

queued
sdkCAR-142

first real customer rebuild on sdk

a design partner rewrites its runtime on @flowget/sdk + ctx ports while keeping its own database. validates the engine-has-no-db architectural bet.

exploring
dxCAR-88

ai authoring + cost portability

authoring_session_id and node_shape_signature as first-class telemetry contract. cost model portability when the worker runs inside a customer vpc.

exploring
Tickets, progress, and ordering on this page are illustrative — not a commitment.
$ got a request? tell us