A small team that owns its own hardware.

How this started

We began by hosting our own projects, because the providers we were paying kept selling us things that did not exist: unlimited disk on a shared drive, twenty-four-hour support that meant an automated reply at three in the morning, a headline price that doubled at the first renewal. Running the infrastructure ourselves was cheaper and, more to the point, honest.

Other people asked to be put on the same machines. That is the whole origin story. We did not raise money, we did not buy a white-label reseller package and paint a logo on it. We bought hardware, learned to run it properly, and sold the capacity we had left.

What we actually operate

Our platform runs on enterprise hardware in carrier-grade facilities in Secaucus, New Jersey. Shared hosting sits on LiteSpeed with LSCache and cPanel. Virtual servers run on KVM with dedicated cores and NVMe storage. Dedicated machines are exactly that: one tenant, full hardware access, nothing virtualised.

Everything is monitored continuously on our own monitoring system rather than a third-party status widget, and everything is backed up nightly to storage in a separate location. Our uptime target is 99.9%, and when we miss it we say so and credit the account rather than waiting to be asked.

Why we also build websites

Most hosting problems are really application problems. A site that falls over under traffic is usually a badly built site on adequate hardware, not the other way round. We got tired of diagnosing other people's work, so we started doing the build as well: fixed scope, fixed price, on our own infrastructure, handed over with the credentials and no ongoing dependency on us.

You are not obliged to use both. Plenty of customers host with us and use their own developer, and plenty of design clients move the finished site elsewhere afterwards. Neither is a problem.