Websites, line-of-business applications, file services, and backups — specified, migrated, and kept running. Advisory if you have a team, fully managed if you don’t.
Business-to-business only. Sole traders and small firms are exactly who this is for.
Most small businesses end up hosting by accident. A website goes on whatever the web designer used, the accounts package ends up on a server in a cupboard, files live in whichever cloud drive someone signed up for, and the backup is a job nobody has checked since it was configured. It works right up until it doesn’t — and then the person who set it up has moved on.
We take that estate, work out what it actually costs and what it actually risks, and give you something deliberate instead: sized correctly, documented, backed up, and either handed back to your team or run by us.
WordPress and static sites on infrastructure that’s patched, backed up, and behind a CDN — with TLS certificates that renew themselves and a staging environment for changes.
The database-backed application your business runs on, moved off the machine under someone’s desk and onto something with a backup and a restore procedure.
Microsoft 365 or Google Workspace configured properly — SPF, DKIM, and DMARC set so your mail arrives, MFA enforced, and offboarding that actually removes access.
Shared storage with permissions that match your org chart, versioning for when someone overwrites the master, and a retention policy you chose deliberately.
Offsite, encrypted, and — the part everyone skips — periodically restore-tested. A backup nobody has restored from is a hypothesis, not a backup.
Registration, DNS, and certificate lifecycle in one place, with records documented so nobody is guessing what an entry does five years from now.
We don’t resell hosting or take vendor commission, so the recommendation is genuinely the one we think fits.
What’s running, where, on whose account, costing what, and who depends on it. This step alone frequently uncovers services nobody remembered paying for.
A written target architecture with costs, a migration sequence, and a rollback position for each step. You approve it before anything moves.
The new environment is built and populated while the old one keeps serving. You get to test against real data before committing.
Scheduled at a time that suits your business, with DNS TTLs lowered in advance and the old environment kept warm until we’re all confident.
Old services shut down and stopped being billed, final documentation handed over, and either a handover to your team or the start of a managed retainer.
Wherever practical, infrastructure is bought in your name, on your account, with your payment method. You own the relationship and the data, and you’re never locked into us to keep the lights on. We bill for our work, not for a markup on someone else’s compute.
Usually not. Most engagements we do are tidying and right-sizing an existing estate rather than moving it somewhere new. If what you have is fundamentally sound, we’ll say so and the work becomes configuration and documentation rather than a migration.
You keep everything. Infrastructure is in your accounts, documentation is written to be handed over, and credentials are yours throughout. We’ll do a structured handover to whoever takes over. A managed service you can’t leave isn’t a service, it’s a hostage situation.
Yes, and it’s common — particularly on advisory work where an independent second opinion is the point. Tell us the boundary you want and we’ll respect it.
Advisory work is a fixed-scope project price, quoted up front. Managed hosting is a monthly retainer sized to the estate, not billed per ticket — you shouldn’t have to weigh whether a problem is worth reporting. Infrastructure costs are yours directly and we help you forecast them.
Even a rough list is enough to start. We’ll tell you what’s fine, what’s costing more than it should, and what would keep us up at night.