Welcome to Vork

Why Vork Exists

Every business has software that almost fits.

A spreadsheet exists because the CRM can't quite do what the business needs.

Someone spends an hour every morning copying information between systems because two applications don't talk to each other.

An approval process lives in Slack because changing the ERP system would take months.

These aren't really business problems.

They're software problems.

For decades we've accepted that changing the way a business works means changing the software that supports it. That usually involves buying another product, commissioning another application, or writing another integration.

The cost of changing software has become one of the greatest barriers to improving businesses.

Vork exists to change that.

Behaviours, Not Applications

Traditional software is organised around applications.

You build a CRM.

A helpdesk.

A booking system.

An approval system.

Each contains its own workflows, user interface, integrations and business rules.

Vork takes a different approach.

Instead of building applications, you build behaviours.

A behaviour represents something useful that an organisation can do.

Examples include:

Triaging support emails
Creating customer quotations
Booking appointments
Approving annual leave
Monitoring cloud costs
Issuing SSH certificates
Publishing software releases

Once defined, a behaviour can be used from anywhere.

A web page.

Slack.

Telegram.

A scheduled job.

Another behaviour.

Or an interface that hasn't even been invented yet.

The behaviour stays the same.

Only the way people interact with it changes.

Behaviour Engineering

Vork is built around the idea of Behaviour Engineering.

Instead of designing applications, you engineer behaviours.

A behaviour describes what the organisation can do, not how a particular user interface performs it.

Behaviours are assembled from a small number of reusable building blocks.

Agents provide conversation and decision making.
Skills perform units of intelligent work.
Reflections connect behaviours to external systems and services.
Jobs execute behaviours automatically or on a schedule.
Surfaces present behaviours through user interfaces.

Each component has a single responsibility.

Together they form behaviours that can be reused across many different interfaces and workflows.

A customer support behaviour, for example, might combine:

An Agent that communicates with support staff.
Skills that classify and prioritise emails.
Reflections that access Gmail and your CRM.
Jobs that monitor the inbox.
Surfaces that allow staff to review and manage requests.

The behaviour exists independently of any particular application.

Whether it is accessed through a web page, Slack, Telegram, or a future interface, the behaviour remains the same.

Behaviour Engineering is a term that emerged during the development of Vork, reflecting a shift away from building applications towards engineering reusable behaviours that can be presented through many different interfaces.

AI Changes the Interface

For decades software relied on forms, menus and buttons because computers couldn't understand what people wanted.

We translated our intent into clicks.

Find the customer.

Open the invoice.

Click Receive Payment.

Enter the amount.

Press Save.

The interface wasn't there because people enjoy clicking buttons.

It was there because the computer couldn't understand:

John has paid invoice 123.

Generative AI changes that.

For the first time, computers are beginning to understand human intent directly.

That doesn't mean every application should become a chatbot.

Far from it.

Humans still benefit enormously from visual interfaces.

Charts.

Maps.

Calendars.

Dashboards.

Those aren't going away.

What changes is the role of the interface.

Instead of translating intent...

...it becomes a window into what the behaviour is doing.

Open by Design

Vork is built around open technologies wherever practical.

Surfaces are standard HTML, CSS and JavaScript.

Reflections describe external systems rather than hiding them behind proprietary code.

Behaviours are composed from reusable building blocks that remain visible, understandable and editable.

The goal is not to replace existing systems.

The goal is to allow them to work together.

Built to be Transparent

Vork uses familiar technologies wherever practical.

Surfaces are built using standard HTML, CSS and JavaScript.

Reflections describe external systems through open contracts.

Behaviours are assembled from reusable building blocks that remain visible and editable.

AI can generate interfaces, write code, refactor existing implementations and help evolve solutions over time.

But nothing is hidden.

Every file remains accessible.

Every behaviour can be inspected.

Every generated artefact belongs to you.

Whether you prefer to write code yourself, work alongside AI, or let AI generate an initial implementation that you refine later, Vork keeps the implementation transparent.

The goal isn't to replace developers.

It's to remove unnecessary effort, allowing people to focus on solving business problems rather than plumbing and boilerplate.

The Vork Philosophy

Everything in Vork is guided by a few simple principles.

Behaviours over applications
Software should adapt to businesses, not the other way around
AI should accelerate developers, not replace them
Use open standards wherever practical
Keep humans in control
A behaviour should be usable from many different interfaces

These principles influence every part of the platform.

Agents help people interact with behaviours.

Skills perform work.

Reflections connect external systems.

Jobs automate processes.

Surfaces provide user experiences.

Together they form reusable building blocks that can be combined to solve real business problems.

Who is Vork for?

Vork is for people who want agency.

People who don't just want to consume software—they want to build with it.

Whether you're automating your own business, creating tools for customers, replacing spreadsheets, integrating systems, or building entirely new products, Vork gives you the platform to do it.

You don't need to ask permission.

You don't need to wait for a SaaS vendor to add the feature you need.

You build it.

Vork is open source because we believe powerful tools should be accessible to everyone.

Build something useful.

Build something for yourself.

Build something for your customers.

Charge for your time.

Charge for your expertise.

Charge for the solution.

Or give it away for free.

That's your choice.

Vork isn't trying to build your application.

It's giving you the operating system to build your own.

Today that means AI agents, skills, reflections, jobs and surfaces.

Tomorrow it will be whatever you imagine.

Our goal isn't to create another SaaS product.

It's to create the next generation operating system for work.

So stop waiting.

Go build something useful.

Go get to Vork.