About CaterOS

The person behind CaterOS

My name is Khokon. I have built WordPress sites since 2011, and CaterOS began with one catering company in Hamburg that needed something nobody had built yet.

2011

building on WordPress since

850+

client projects delivered

50+

countries served

100%

job success score, Top Rated on Upwork

Seven plugins, and the phone still rang.

D’Agate has fed Hamburg since 1962. When I started working with them in September 2025, they were still taking most of their orders by telephone. The job looked straightforward: redesign the website. The site was already running seven plugins, carefully assembled by the developer before me, and together they still could not answer the questions a caterer faces every working day.

Can we deliver to this postcode, and what does that cost? Is there enough notice to cook for ninety people? What is this order actually worth, before anyone agrees to it? Seven plugins, and Prem Kumar Kapoor was still answering all of that on the phone.

The seven plugins D’Agate’s site was running before CaterOS.

So I stopped searching for a plugin that fit, and started listening. CaterOS came out of those conversations.

There is a longer version of this, and it starts in a village where everyone assumed I would farm.

Read the longer story →

Four things I decided early, and have not changed.

Your orders belong to you.

Every order, every customer record and every menu sits in your own WordPress database. Nothing routes through my servers, because in this arrangement I do not have any.

Rent is not ownership.

The catering software market runs on monthly fees. Stop paying and the ordering system disappears, taking the order history with it. CaterOS is a plugin you install and keep.

Accessibility is not an afterthought.

I run an accessibility practice called NexoBee. That work shaped CaterOS: keyboard navigation and screen-reader support were part of the design, not bolted on. Find something I missed and I will fix it.

Small numbers matter.

Most catering software is built for companies with an events department. CaterOS is built for a caterer with a kitchen, a van, and more to do than hours to do it in.

Three businesses, one person

WordPress since 2011, mostly the unglamorous kind.

I recover hacked sites, remove malware, and harden WordPress installations so the same thing does not happen a second time. That background is the reason CaterOS keeps your customer data inside your own database, and the reason I treat GDPR as engineering rather than as a checkbox.

WPBravo

since 2021

WordPress design, security and maintenance for clients who need the site to keep working.

NexoBee

accessibility

Web accessibility audits and code fixes for businesses in the United States.

CaterOS

since 2026

The third, and the first one that is a product rather than a service.

Check any of it before you trust me with anything at all.

CaterOS is one person. Here is what that buys you, and what it costs you.

There is no team behind this, and pretending otherwise would be the first thing you caught me in.

What it buys you

When you email support, I answer. Not a ticket queue, not a first-line agent working from a script. I reply within 24 hours, and I am the person who wrote the code you are asking about.

What it costs you

I cannot ship as fast as a funded company with a dozen engineers. The roadmap moves at the speed of one developer who also answers the support inbox.

The question underneath the question

What happens if I stop?

The free version of CaterOS lives on WordPress.org under the GPL. The code is public. Your site keeps running, your orders stay in your own database, and any WordPress developer can pick it up and maintain it. No rented platform can offer you that. When a rented platform shuts down, your ordering system shuts down with it.

See what those conversations turned into.

The free version includes the full ordering wizard. Install it, send yourself a test request, and decide from there.

Questions first? Email hello@caterospro.com and I will reply within 24 hours.