
The open operating system that remembers how your organisation works.
Just Vork.
Why does Vork exist?
Read "I Didn't Want to Build Another Application" →Software remembers data.
People remember experience.
Vork connects the two.
Modern organisations are built from dozens of disconnected applications.
Knowledge becomes fragmented. Every application solves one problem while creating another.
Vork takes a different approach.
Everything is built from simple records, reusable tools and human-focused skills.
Records
hold truth
Tools
provide capability
Skills
express intent
Agents
execute tasks
Humans
provide judgement
Instead of buying another application...
Teach Vork a new behaviour.
Software shouldn't multiply.
Every SaaS product creates another login. Another subscription. Another workflow. Another copy of your organisation.
Eventually your business becomes harder to understand than the work itself.
The future isn't more software.
It's better memory.
The Vork Model
Everything in Vork is built from six simple building blocks.
Together they create an operating system for work.
Records
Durable organisational memory.
Customers. Projects. Ideas. Articles. Support tickets. Anything that matters.
Unlike conversations, records persist and become part of your organisation's knowledge.
Tools
Capabilities that interact with the outside world.
SSH. HTTP. Email. Git. Webhooks. Containers. LLMs.
Each tool performs one job well. Tools never contain business logic.
Skills
Combine tools to accomplish a specific outcome.
- Read a calendar
- Publish a newsletter
- Search a knowledge base
- Deploy a release
Skills execute within their own isolated context, allowing them to perform complex tasks safely while exposing only the information they need.
Agents
Specialists designed around roles, not conversations.
A Support Engineer shouldn't have access to Release Management. A Marketing Assistant shouldn't be able to deploy production.
Each agent has its own personality, instructions, available skills and tools.
Concierge
Your primary interface to Vork.
It understands what you're trying to achieve. Sometimes it answers directly. Sometimes it delegates to specialist agents.
The Concierge coordinates the system so you don't have to.
Human Judgement
AI prepares. Humans decide.
Every significant action can be reviewed, approved or corrected.
Vork exists to amplify human judgement, not replace it. Every interaction strengthens organisational memory.
Build behaviours,
not applications.
Why organisations choose Vork.
Organisational Memory
- Capture knowledge naturally as work happens.
- Every decision strengthens the organisation.
- Not just today's conversation.
Open by Default
- No user limits.
- No artificial feature gates.
- No workflow restrictions.
- Install it. Own it. Teach it.
Infrastructure Native
- Built by infrastructure engineers.
- Designed around open standards.
- Containers. SSH. Automation.
- Real systems.
Example Behaviours
Teach Vork how your organisation works.
Marketing Agent
- Generate ideas
- Draft content
- Prepare newsletters
- Organise campaigns
Support Assistant
- Read email
- Search knowledge
- Draft replies
- Learn from every interaction
Release Manager
- Coordinate releases
- Prepare announcements
- Publish documentation
- Track progress
Personal Butler
- Remember conversations
- Organise priorities
- Prepare your daily briefing
- Help you focus
Documentation Assistant
- Transform knowledge into documentation
- Keep information current
- Build organisational memory
Infrastructure Operator
- Connect using SSH
- Inspect systems
- Collect evidence
- Assist human decision making
Getting Started
Run Vork with a single Docker command.
$ docker run -d \
-p 8080:8080 \
-p 8443:8443 \
-v vork_conf:/app/conf.d \
justvork/vork-server:latestThat's it. Vork is running. Open your browser at http://localhost:8443 and start building behaviours. For more deployment options visit github.com/justvork.
Behaviours are shared.
Knowledge compounds.
Trust is earned.
Humans decide.
Just Vork.
The ideas behind Vork.
Vork didn't begin as an AI project.
It began with a simple question.
What if software behaved more like a trusted colleague than another application?
The Workshop is where those ideas are explored.
