vork@osx: ~
The open source platform for creating and running useful behaviours.
Just Vork.
WHAT IS VORK?
So, what is Vork?
Vork is an open-source platform for building behaviours.
A behaviour is simply something you want to do: watch Reddit for conversations about your project, triage an inbox, investigate a support issue, prepare a newsletter, or coordinate work with other people.
You build the behaviour once. Then you can use it in a conversation, run it automatically, or put a user interface in front of it.
Build behaviours, not applications.
We call this Behaviour Engineering.
Read "I Didn't Want to Build Another Application" →BEHAVIOURS
What can I do with it?
Start with something you want to happen. Then define the behaviour that will make it happen. Here are some examples of real world uses that have already been built with Vork.
Scan Reddit
Find conversations relevant to your project and decide which are worth joining. Draft replies, and post them when you are ready.
Triage an inbox
Inspect a mailbox, classify, draft responses and route to the appropriate folders or team members.
Investigate a support issue
Gather evidence, inspect logs and source code, ask questions, and keep the investigation moving.
Prepare a newsletter
Pull information together, create the content, and send it through the systems you already use.
Process a contractor invoice
Read the invoice, verify supplier, prepare the payment for approval, and submit the transaction to Xero.
Ask someone and carry on
Need information from somebody else? Ask them, wait for their answer, then continue the work.
These are behaviours. Build one, change it, combine it with others, or share it.
THE VORK MODEL
Three ways in.
There are three ways into Vork: use a Surface, talk to an Agent, or let an Automation run one for you.
Agents do the thinking. Skills give them reusable behaviours. Tools and connections let those behaviours interact with the world.
People remain part of the process whenever information, judgement or approval is needed.
There's more to it, but you don't need to learn it all here.
Run it.
Vork is open source. Run it yourself.
$ docker run -d \
--name vork-server \
--restart unless-stopped \
-p 8080:8080 \
-p 8443:8443 \
-v vork_conf:/app/conf.d \
justvork/vork-server:latestTHE THINKING
Why does Vork exist?
I've been building software for nearly 30 years, much of it to run my own businesses. I've always thought software should adapt to the way we work, not force us to adapt to the way somebody else decided their software should work.
AI finally made something I'd wanted for years practical.
Instead of adding another application every time there's a problem to solve, we can build the behaviour itself. Behaviours that understand how we work, use the systems we already have, involve people when they're needed, and get on with the rest themselves.
Less user interface. More automation. Software that's much more closely aligned with the business using it.
More Vorking.
Vork grew out of that thinking. If you want to understand where the idea came from:
What Is Software Development in 2026? →
When implementation becomes cheap, understanding the problem, engineering the behaviour and proving it works become more important, not less.
The Birth of Behaviour Engineering →
What happens when we stop treating applications as the unit of software and start engineering the behaviours themselves.
I Didn't Want to Build Another Application →
The story of why Vork started with a behaviour instead of becoming yet another application.
OPEN SOURCE
Built in the open.
Vork is open source.
Explore the code, use what we've built, change it, or build your own behaviours.