work.flow
Join the waitlist

One sentence in.A working pipeline out.

No code. No setup. Just describe it.

See it

Describe. Verify. Get your time back.

One tool. Build any kind of workflow.

the library

Everything
in one place

work.flow can transform files, images, audio, video, PDFs, spreadsheets, pull market data, send emails, and do much more. All on the canvas.
See exactly what’s happening, every step of the way.

161

built-in tools. Open any one and read it

0

files uploaded. Your documents never leave your device

3

platforms: macOS · Windows · Linux

20s

from one sentence to a working pipeline

how it works

Three steps. No surprises.

01 · describe · you type it

Describe it

wordsplan
Inputplain English
Modeplan first, or build now
Stepsas many as needed
Wiresdrawn for you

Type what you want done, in plain English. Preview the step-by-step plan generated by work.flow or build as you go and undo anything.

02 · verify · you approve it

Verify it

planfiles
Previewplain English
Reads312 files
Writes312 new ones
Deletesnothing

Nothing moves until you say so. You get a plain summary of what work.flow will read, write and delete, with real counts. Rehearse it first if you want.

03 · run · on your machine

Run it

filesresults
Scheduledaily, or on new files
Saved asinvoices.flow
Logevery run, plain English
Doneenjoy your day

work.flow runs on your machine, the same way every time. Bind it to a folder, or run it with no interface at all. Every run leaves a plain log.

read the code

See the code behind every step

The agent picks steps, wires them, explains itself. Ask why, change a step, have it write a new one.

Never a black box: settings on the card, edits stay. No wizards, no formulas.

Don’t like it? Tell the agent. Your version becomes a new building block.

Turn every video in my Clips folder into a small, optimized GIF, and put the GIFs right next to the originals.
Built it. Three steps, wired on your canvas: pick folder export to GIF save here
Before anything runs: I’ll read 14 videos from Clips and write 14 new .gifs beside them. Your originals aren’t touched.

↶ Undo canvas changes

What’s actually inside that Export to GIF step?
Real Python. Open the Scratch tab and you’re looking at it: it builds an optimized palette first, then maps the frames onto it. Change the fps parameter, save your version, and it becomes a step of yours.
Nice. Set the fps to 15 and run it.
fps is 15 on your card now. The edit stays. Ran it: 14 GIFs written to Clips, 38 MB total, 41 seconds. The plain-English log is saved with the run.
Do this every Friday from now on, and keep the workflow somewhere safe.
Scheduled: every Friday · 9:00 And it’s saved as clips-to-gif.flow beside your Clips folder. Plain JSON, runs without me. Same steps, same way, every Friday.
See how each step works. Open any step in the app, inspect the code, make changes, and save your own version.

before anything runs

Nothing leaves your machine unless you told it to.

01No servers, no account, no cloud

Every install runs fully on your own machine. There’s no account to make and nothing waiting on a server somewhere.

02Own environments

Each step runs in its own environment with its own dependencies, so steps never interfere with each other or the rest of your setup.

03Your credentials

Your own API keys stay on your device. They’re never sent anywhere but the model provider you chose.

04Bring your own model

Use Anthropic, OpenRouter, or DeepSeek with your own key, or go fully local with Ollama or MLX for zero network egress.

Frequently Asked

Questions

01What does it cost?

Free during the beta. Final pricing isn’t set, but one thing already is: no per-task fees and no credits, ever. The waitlist hears first when that changes.

02What can I automate?

Anything that repeats on your computer: renaming and sorting files, resizing images, cutting video, merging PDFs, spreadsheets, market data, sending email. If you can describe the chore in a sentence, work.flow can build the automation.

03Does my data leave my device?

Your files never do. It calls the AI provider you choose, with your own key, or runs a local model and sends nothing out at all.

04Will it do the same thing every time?

Yes. The AI helps you build the pipeline. It’s not part of running it. Once built, the same steps run the same way, every time.

05Do I need to know Python?

No. The Python is there when you want it, not because you need it.

06Which platforms?

macOS, Windows, Linux.

07When do I get in?

A confirmation when you sign up, then one email when your build is ready. Nothing else until then.

08What’s the catch?

Team features, scheduling recovery, and a few other things aren’t here yet. We’d rather you heard that from us.

09What if work.flow disappears?

Your .flow files are plain JSON on your own disk. The app keeps running whether we do or not, because there’s no server it depends on.

join the community

It’s early and rough.
Come help us find the edges.

Free during beta. No account, no card required.

You’re on the list. Watch for one email.