We keep web applications running.

We build web applications, and more often, we keep them alive: patched, backed up, monitored, and online.

Most of our work starts the same way. Someone has a site or an application that matters to their business, and nobody is really looking after it. Updates are behind. Backups have never been tested. Nobody is watching at 3am. That is the problem we solve.

Where we go deep

Management systems

The systems an organisation runs on: bookings and scheduling, warehouses and inventory, accounting workflows, administration. We start from the problem, not from a product. We study the case, then pick the right tool: sometimes proven open-source software we customise, sometimes something built from scratch to fit exactly. One of these systems has been running in production, under our management, for over a decade.

Making systems talk to each other

These systems rarely stand alone. They exchange data with payment providers, accounting tools, external platforms, and each other. We design and build the APIs that connect them, and the access and login layers that decide who gets in and what they are allowed to see. This is the part that is usually underestimated, and the part that is expensive to fix later.

What we work with

We do not sell one platform. We start from what the application actually has to do: how much content, how many people use it, what it has to connect to, and who maintains it after launch. We choose from there.

What does not change is what happens afterwards. Whatever it runs on, it runs on our infrastructure, and we keep it running.

We run our own infrastructure

We are not a reseller. Our clients' applications run on Kubernetes clusters we built and operate ourselves. That means we can answer the questions most web companies have to forward to someone else: how it behaves under load, why it went down, and what we changed to stop it happening again.

Who we work with

Most of our work is for clients in Europe. We also take projects in Jordan, though not every one that comes to us.

We are selective, and not arbitrarily so. We take on work we intend to still be responsible for years after launch. In practice that means three things:

• The application matters to the business
• It has a future, not just a launch date
• It is something we can host and maintain ourselves

A one-off build with nobody looking after it afterwards is usually better placed with someone else. We would rather say so in the first conversation than halfway through the project.