If you searched for this page, you probably know React Flow, like React Flow, and need the same class of node-based editor inside an Angular application. The direct options are wrapping React inside Angular or picking an Angular-native library. Foblex Flow is the Angular-native answer: the same product category — node editors, workflow builders, interactive diagrams — built on Angular's own primitives.
Wrapping works, but you pay for it permanently:
An Angular-native library removes the seam: nodes are your Angular components with your bindings, and the editor participates in change detection like any other part of the app.
The paradigm differs by design. React Flow describes the graph as data (nodes[], edges[]) rendered by the library; Foblex Flow describes the graph as an Angular template rendered by you. What you know transfers directly:
<ReactFlow nodes={nodes} edges={edges}> → <f-flow fDraggable><f-canvas> with @for over your own model;position and data → any element with fNode and [fNodePosition], containing real Angular UI;<Handle type="source" /> → <div fConnector fConnectorType="source" fConnectorId="...">;<f-connection fSourceId fTargetId> with behaviors, types, markers and labels;onConnect → (fCreateConnection) — the library emits intent, your app updates the model;<MiniMap />, <Controls />, <Background /> → <f-minimap>, fZoom + public zoom API, <f-background>;dagre/elkjs layout recipes → the @foblex/flow-dagre-layout and @foblex/flow-elk-layout packages;fitView, viewport helpers → fitToScreen(), resetScaleAndCenter(), centerGroupOrNode().The golden rule in the default stateless mode is the same one React Flow users already respect: the library never mutates your application-owned data — it emits events, you decide. If you prefer library-managed graph records, the optional Managed Flow State plugin applies supported gestures to an explicit typed store and includes snapshots and undo/redo.
This is not a list of features React Flow lacks. React Flow currently supports server-side rendering, controlled and uncontrolled state, keyboard operation, screen-reader semantics, connection reassignment, and third-party layout integrations.
Foblex Flow differs at the framework and interaction-model boundaries:
fConnector can behave as a source, target, source-target, or outlet while connections refer to canonical source and target IDs.withA11y() keyboard layer uses spatial navigation across nodes and connections and supports keyboard connection creation.Both libraries can build production node editors. The deciding question is usually which rendering model and framework boundary your team wants to own.
If those outweigh framework fit for your team, React Flow with a wrapper is a legitimate choice. For a source-linked evaluation matrix covering rendering, state, SSR, accessibility, layout, and migration, read React Flow vs Foblex Flow for Angular teams.
Continue with Get Started, browse the examples, or open the flagship AI Low-Code Platform demo to see how far the same primitives scale.
Claims about React Flow on this page were verified on 2026-07-28 against its official documentation: