Build the app.
Own the whole stack.
A Flow-Like app holds everything a business process needs: its logic, its interfaces, its data and who may use it. Draw it, write it or describe it to Flux, then run it on a laptop, a phone, your own servers or the cloud.
- Pages & widgets Dashboard · Form · Widgets
- Events Chat · Page · REST · MCP · Cron
- Flows Typed nodes · FlowScript
- Data Tables · Ontology · SQL
- Access & audit Roles · Versions · Audit trail
Everything a process needs. In one place.
No glue between five tools. An app is one boundary for logic, interface, data and permissions, so it ships, versions and moves as a whole.
Flows
The logic, drawn as typed nodes on a board. Every board also reads and writes as FlowScript, a TypeScript-like text form.
Pages & widgets
Responsive interfaces built from components, visually, as JSON or by Flux. Flows can update a page while it runs.
Events
The ways into a flow: a chat, a page, an API, an MCP server, a schedule, a chat bot or a mailbox. Each follows the latest flow or a pinned version.
Data Studio
Tables that live with the app, an ontology that explains them, and SQL across them and your other sources.
Storage
Shared files for the app and private files per person, with optional write-once storage for records that must not change.
Templates & versions
Immutable versions of every flow, and templates to start the next app from the last one.
One flow.
Every way in.
Give the same logic a chat, a page, an API, an MCP server for AI clients or a schedule. People get the interface they need; the flow stays one.
A chat for people, built in.
- History and attachments
- Tools, starter prompts and reactions
- Publish it on a link, sign-in by default
How did EMEA do last week?
Revenue was €412k, up 8% on the week before. Tuesday carried most of it.
AlsoQuick ActionAPIDaemonDeeplinkLocation RegionInbound Email
Draw it, write it, or ask for it.
The board, the code and the conversation are three views of the same flow. Switch whenever it's faster.
FlowScriptChange fast.
Break nothing.
Apps change every week. Versions, roles and an audit trail make that boring in the best way.
- 01
Versions you can pin
Every flow version is immutable. Each interface follows the latest one or stays pinned until you move it.
- 02
Releases with checks
Replay recorded inputs before you promote a change, split traffic in the cloud, and restore an earlier version in one step.
- 03
Roles and visibility
Custom roles, invites, join requests and API keys. Keep an app private, share it with a team or publish it.
- 04
A tamper-evident trail
Signed, chained records of what happened, exportable to your own storage or SIEM and verifiable offline.
Runs where the work happens.
The same app runs on a laptop without an account, in the browser, on your phone, on a device in the warehouse or in your own cloud.
Desktop
Windows, macOS and Linux. Offline apps need no account and never leave the machine.
Web
Online apps in the browser, with hosted chats, forms and pages behind sign-in by default.
Phones
Shortcuts and Siri actions, home screen widgets, Live Activities and Android quick tiles.
Your devices
A small agent runs apps on office PCs, edge gateways or home servers. Outbound connections only, no port forwarding.
Your cloud
Self-host with Docker Compose or Kubernetes. By default every run gets its own single-use sandbox.
Local automation
Browser, computer and RPA steps run on the machine that has the screen, never on a shared server.
Thousands of nodes. Add your own.
More than 2,000 built-in nodes cover AI, data, documents, the web and industrial protocols. When one is missing, write it in one of 15 languages, from Rust and Python to TypeScript and Go. It compiles to sandboxed WebAssembly and ships through the package store.
Write a nodeBuild your next app.
Download the desktop app and start offline, without an account. Move to the cloud when the team joins.