Platforms & Hosting

The application that owns the state and decides what happens next. Every other layer is something it drives, and when it is wrong, everything downstream is wrong in a way nobody notices for a week.

Vector exposes just over a hundred versioned endpoints, keeps external services behind configuration toggles so it degrades instead of failing during an upstream outage, and scopes every query to the authenticated account. TurboHub is a control panel with no users table at all — authentication is one middleware class that asks WHMCS.

Getting from a button click to a running site, across a dozen services that are each asynchronous, each able to fail on their own, and each needing a different recovery when they do.

Vector records each resource the moment it is created, so a half-finished provision is a targeted retry rather than a guess, and explicit state machines reject illegal transitions by construction. Helix dispatched four different ways depending on the work — synchronous REST for the flat resources, a queue with an HTTP callback for anything that might take minutes. More on automation & AI workflows.

Addressing thousands of machines that fail on their own schedule, and shipping code to them when you cannot push and they cannot accept an inbound connection.

TurboHub made the queue name the server, so addressing a machine, naming it, and authorizing it are the same act — no routing table to keep in sync, and no way to reach a box you are not entitled to. Delivery is pull: every server checks in on cron, and the updater updates itself first. 5,000 servers, four regions.

What actually serves the traffic. Caching, TLS, load balancing, and the isolation model that keeps one busy tenant from becoming everyone's problem.

Vector runs WordPress serverless on Lambda, content-hashing assets so a deploy does not pay to move bytes that did not move. Helix assembled Varnish, nginx, HAProxy, and Apache in mass virtual host mode, with one PHP-FPM master per site and a purge daemon that authenticates callers by socket peer credentials rather than a shared secret.

One deployment serving many companies, each of which believes it is the only one. Isolation as a structural property of the schema and the policies, not a WHERE clause someone remembered to add.

Helix made the brand a data model rather than a config file — its own domain, TLS certificate, gateway credentials, registrar, nameservers, catalog, pricing, and view overrides, resolved per request from the incoming host. It carried dozens of partner brands through three companies and two acquisitions. On Vector, partners are separated by infrastructure and never touch AWS.

Getting customers onto the platform without an incident. A billing migration cannot be rolled back, because the moment the new system charges a card the outside world has changed.

Wormhole moved roughly ten thousand customers off three legacy WHMCS installations, one brand per announced maintenance window, with resumable exports and an audit ledger mapping every legacy ID to its replacement. Nobody had to apologize to a customer about a charge.