Start in Sandbox

Steinvar FlowWorkflow orchestrationProcesses you can see, test, approve and replay.

Account opening, payments, loans and deposits each run as a flow you can open and read. Steinvar Flow lets you change the steps in a visual designer, prove the change with a dry run, publish it under maker-checker, and restart a stuck run from the step that failed.

Start in Sandbox All modules
The savings-account flow in the flow designer: version 3, active and view-only, with a dry run.

The HQ back office; the workplace and people’s names are blurred.

30+
operators for accounts, payments, screening, loans and more
400 days
of event history kept and replayable
Dry run
that writes nothing before a flow goes live

Design

  • Visual designer

    Flows drawn from operators for accounts, payments, fees, screening, loans, deposits and notifications, with settings per node.

  • Versions with checksums

    Each version is checksummed and published under maker-checker; what runs is what was approved.

  • Dry run

    A flow runs end to end against real data without writing anything.

Run

  • Restart from the failed step

    A run that stopped resumes at the node that failed, not from the beginning.

  • Circuit breaker

    A failing dependency trips a breaker so a flow stops cleanly instead of failing node by node.

  • Dead letters and replay

    Messages that cannot be processed go to a dead-letter queue and can be replayed once fixed.

Events

  • Durable streams

    Events kept for 400 days on NATS JetStream, with durable consumers that each process a message once.

  • Outbox

    Events a database write owes are written with it and published after, never lost between the two.

  • Replay

    A replay-safe consumer can be rewound to rebuild what it derives.

How a flow change ships

  1. Draft

    An analyst edits the flow in the designer.

  2. Dry run

    The draft runs against real data and writes nothing.

  3. Approve

    A second person approves the version; its checksum is recorded.

  4. Run

    New work runs on the new version; failed runs restart from their failed step.

Controls built in.

  • Maker-checker versions

    Nobody publishes their own flow change.

  • Run log

    Every run and every node’s outcome is recorded.

Standards and formats

  • NATS JetStream
  • Transactional outbox
  • Dead-letter queue

Not in this module today

  • Event streams run as a single replica on one host today; replicated streams are on the roadmap.

Questions about Steinvar Flow

Can we add steps to account opening or payments?

Yes, by editing the product’s flow in the designer. The change is dry-run, approved by a second person and then used for new work.

Try Steinvar Flow in the sandbox.

Start in Sandbox