Production-ready by default
Preflight checks catch schema & wiring issues before run. The same typed graph ships across dev → staging → prod — no “hardening” rewrite.
Design reliable systems with type-safe graphs, Rust-level performance, and built-in governance. Start local for a head start, then move to edge or any cloud — no rewiring.
Want AI too? Blend classical ML with GenAI when it helps — it’s one more set of typed nodes, not a separate stack.
Please wait while we prepare everything
The graph you sketch is the graph you deploy. Typed ports, preflight validation, and a deterministic Rust runtime mean no throwaway prototypes, no glue-code rewrite, and no surprises when you flip from dev to prod.
Same typed graph across environments — no “hardening” rewrite.
Preflight checks catch schema & wiring issues before run. The same typed graph ships across dev → staging → prod — no “hardening” rewrite.
Typed dataflow with versioned port schemas makes refactors safe & reviewable. Changes are validated, so prototypes stay deployable as they evolve.
The Rust runtime compiles micro-plans, applies back-pressure, and keeps latency stable under load. Add approvals & policies without changing the graph.
Drag nodes, wire typed pins, and validate as you go. Inline errors keep graphs shippable. Snapshot inputs to reproduce issues and compare runs.
Ports know their schema, so refactors are safe.
Miswired edges surface immediately.
Inspect payloads and timings at every edge.
Manage the full lifecycle from the interface — no CLI required. Keep projects private and local, publish to your team when ready, and ship to production targets with a single action.
Same validated graph — different targets.
Create an offline project on your machine. Your data stays local until you decide otherwise.
Flip the project online and invite colleagues. Roles and approvals come along for the ride.
Choose your target — Edge, Cloud, or on-prem. Click deploy. Same validated graph, different runtime target.
Tight memory control, back-pressure aware IO, and zero-copy on hot paths. Nodes are authored in Rust too — lean on the ecosystem without sacrificing performance.
Wrap internal APIs, queues, PLCs, computer vision, or spreadsheets. Versioned ports and validation make shared nodes safe to reuse across teams.
I/O ports are schema-checked and versioned.
Snapshot fixtures & property tests per port keep changes safe.
Publish privately or to a marketplace with semantic versioning.
Integrate the editor into your product or run the engine headless. Apply your design tokens and logo for a seamless white-label experience — governance and observability stay intact.
Mount the visual editor in any route; theme via CSS variables or tokens.
Map your brand palette; instant dark/light support.
OIDC, JWT, and scoped secrets per tenant/app.
Per-tenant quotas, events, and audit trail.
Control flows via SDKs and REST API.
Use Layers so roles see what they need without leaving the canvas. Switch context — keep the graph.
Three interconnected views of the same process
Warranty Claim Intake: submit → triage → approve/decline → notify → payout/repair.
Every project ships with files, tables, and search that plug straight into nodes. Stream bytes, validate schemas, and combine SQL + full-text + vectors in one flow.
Unlimited files and unlimited databases, wired into nodes. Read streams, transform, and write back with typed pins. Keep data in SQL, add full-text and vectors, and combine them for hybrid queries.
Clean, legible cards with real contrast. One featured deep-dive + two quick reads.
Learn how to integrate Google’s Teachable Machine with Flow-Like for seamless AI-powered workflows.
Read postFlow-Like Alpha v0.0.2 introduces Rapid Prototyping mode, new models, secure offline sharing, and execution fixes.
Read postEnterprise-grade workflow automation built for scale. How Flow-Like's typed workflows solve the problems of traditional workflow engines.
Read postSearch, filter, and deep‑link to answers. Built for individuals and enterprises alike.
Locally on macOS, Windows, and Linux; in containers; on the edge; or in any cloud. Start offline on your laptop, move to production later without changing the graph.
Yes. Flow‑Like is local‑first. You can run completely offline or in air‑gapped environments. Sync to cloud later if you choose.
Wrap systems as typed nodes with explicit input/output types. Embed or white‑label the editor, or run the engine headless inside your app.
Nodes are authored in Rust today. A WASM node SDK is planned to broaden language support.
Yes — approvals, policy guardrails, roles, and versioned flows with audit trails are first‑class to meet operational and compliance needs.
Object‑store–centric by design (e.g., S3/local). For vector search we use LanceDB behind the scenes; graphs interact via nodes — no raw SQL required.
Flows are versioned. You can stage changes, request approvals, and roll back safely. Git‑based workflows integrate smoothly.
The same typed graph runs locally and in production. Package as a container, deploy to edge/cloud, and promote versions via approvals.
The runtime is written in Rust for high throughput and low latency. Many workloads run dramatically faster than typical scripting‑based stacks.
You control where data lives. Local‑first by default, no forced telemetry, and encryption in transit. Keep everything on‑prem if needed.
OIDC/SAML‑based SSO and role‑based access controls are on the enterprise track. Ask us about timelines if you have specific providers.
Business Source License (BSL) 1.1 with an Additional Use Grant, and a Change Date after which each version becomes MPL 2.0.
You may use the software (including production use) as long as you do not use it to develop, offer, or provide a product or service that competes with Flow-Like or with products/services from TM9657 GmbH that are substantially similar to Flow-Like’s functionality.
Yes. A Large Entity—defined as an organization with >2,000 employees or >€300M annual revenue—is not eligible to use Flow-Like under the BSL terms in any capacity and must obtain a commercial license from TM9657 GmbH.
Yes, if neither the agency nor the client is a Large Entity and the delivered solution is not a Competitive Product or Service. Large Entity clients require a commercial license.
No. Build visually with typed nodes. Coding is optional for custom nodes or advanced logic.
Projects are file‑based with object‑store artifacts. Use your existing backup tooling and promote versions between environments.
Types on nodes & edges, local‑first design, Rust performance, and governance built‑in. Safer changes, faster execution, portable deployments.