Rust-powered workflow orchestration

Your Handlers, Your AWS Account.
Full Flow.

Bring your own handlers to a workflow runner built for parallel work. Start locally, run supported workflows on devices and at the edge, and scale orchestration in your own AWS account.

Get Rippflow Studio Explore a workflow →
One flow. Your application logic.
Validate
↓
Handler AHandler BHandler C
↘ ↓ ↙
Aggregate
↓
Complete
DEFINE → FAN OUT → BRING RESULTS TOGETHER

Your infrastructure. Our durable orchestration.

Bring your handlers. Choose where each workflow runs.

  • Your infrastructureYour hardware or AWS account
  • Your dataYour inputs, outputs and storage
  • Your security controlsYour roles and access policies
  1. 01 / Define

    Your workflow

    Workflow definition

    Describe the steps and the dependencies between them.

    Your handlers

    Supply the code each step invokes.

    Workflow input

    Pass the starting data to the run.

  2. 02 / Orchestrate

    Rippflow engine

    Fan out

    Dispatch independent steps as their inputs become available.

    Join results

    Bring parallel branches together before the next step.

    Recover work

    Checkpoint supported edge workflows in SQLite so execution can resume after a restart.

  3. 03 / Execute

    Where work runs

    On device

    Run a supported workflow close to the equipment that produces its inputs.

    At the edge

    Process work on a gateway or local server, including while offline.

    In your AWS account

    Distribute compatible workflows across workers in a provisioned installation.

  4. 04 / Deliver

    Your results

    Workflow output

    Return the result assembled by the final step.

    Your storage

    Use your handler to write results to a store you choose.

    Downstream services

    Call the next service from your handler using its configured permissions.

In practice / CareerGR

One résumé.
Many paths forward.

Turn a résumé into a career report. Coordinate specialist analysis in parallel, bring the results together, and route work through review before publishing.

Parallel analysis feeds a draft, followed by up to two review cycles. Approved reports publish; unresolved reports go to manual review.

Your application owns the intelligence. CareerGR handlers extract, analyze and edit.

Rippflow owns the coordination. Definitions describe phases, lanes, outcomes and bounded rework.

Keep sensitive data in your stack. Pass artifact pointers between phases where appropriate.

Your handlers / Your language

Rust at the core.
Your code at every step.

The workflow stays the same. Choose a language to see its handler contract and local starter commands.

Rust handler

Single-phase handler · JSON in, JSON out

use rippflow_sdk::{run_handler, PhaseOutcome};

fn main() -> Result<(), Box<dyn std::error::Error>> {
    run_handler(|ctx| {
        Ok(PhaseOutcome::completed()
            .with_payload(ctx.payload.unwrap_or_default()))
    })
}

Try an editable starter

The shipped finance example demonstrates sync phases, async shard work, fan-in and bounded rework. Customize its handlers for your application.

rippflow example finance --lang rust --dir my-flow
cd my-flow
cargo build
rippflow dev workflow.json --handlers handlers.json \
  --input input.json --shards a,b --report report.json

Package a handler for Lambda →

Pricing

AWS cloud plans

Preview pricing for workflows in your AWS account by monthly transitions, execution cells and Regions.

Developer

Free

Self-managed · manage your own updates

Included transitions / month
100K
Above the allowance
Upgrade required
Execution topology
1 cell · 1 Region

No SLA or support.

Starter

$49 / month

Monthly subscription

Included transitions / month
1M
Overage per 1M transitions
$6.00
Execution topology
1 cell · 1 Region

Maintained releases · low-touch support

Growth

$199 / month

Monthly subscription

Included transitions / month
5M
Overage per 1M transitions
$5.00
Execution topology
2 cells · 1 Region

Cell-level redundancy · one Region

Scale

$399 / month

Monthly subscription

Included transitions / month
15M
Overage per 1M transitions
$4.00
Execution topology
4 cells · 2 Regions

Self-service · no contractual availability or recovery SLA

Enterprise

Annual contract

Custom commercial terms

Included transitions / month
Negotiated
Overage per 1M transitions
$3.00 target
Execution topology
2+ cells · 2+ Regions
Contact us ↗

Negotiated support and guarantees. Standard up to 6 cells / 3 Regions; custom and multi-account terms available.

Devices, gateways & fleets

Custom quote

Production edge licensing

Tell us how many devices or gateways run workflows, how often they connect, and how your fleet will grow.

Discuss fleet pricing →

Paid plans are in preview. AWS bills infrastructure separately.

Rippflow Studio

Install Rippflow Studio (desktop app and CLI) on macOS, Windows or Linux.

Development license

Get started with Rippflow

Let's talk

Contact Rippflow

Tell us about your workflows, deployment or pricing.

We'll reply to your email.

Search docs

Search workflows, handlers and operations.