A Small Team That Builds And Hands Over
We configure servers, tunnels, firewalls and cloud environments on hardware and accounts that already belong to you, then give you the credentials and the notes and leave. There is no platform here, no dashboard to log into, and nothing that keeps billing you once the work is finished.
That is a worse business than selling subscriptions, and it is a better outcome for the person paying. A monthly fee is easy to sell and it makes every customer permanently dependent on the seller. We would rather build the thing properly, explain what is on the machine, and be the people you call when you want something new rather than the people you cannot leave.
Why The Work Is Sold This Way
A subscription earns for years and a build earns once, which is the entire reason almost everything in this industry is rented. Six places where that decision shows up, and what happens instead when the thing belongs to you.
It can be taken away
Prices rise, terms change, features move to a higher tier, and companies get bought or shut down without asking you first.
It keeps doing what it did
None of that reaches a machine you own. The software carries on behaving exactly as it did the day it was installed.
The bill grows with your team
Per person pricing means hiring costs you twice, once for the person and again for their seat, while the product stays the same.
One bill, whatever the headcount
A server costs the same serving five people or twenty. Adding somebody is an account created, not a seat purchased.
You are asked to trust a policy
Every provider says the right things about privacy and none of it can be checked from outside the company.
There is nothing left to trust
You hold the root password on a machine we keep no copy of the keys to, which is a stronger position than any promise.
Leaving is made difficult
Getting data out is harder than getting it in, and after a few years the cost of leaving is the reason people stay.
Leaving means not calling
Standard software, ordinary formats, your own hosting account. Nothing has to be extracted from anywhere.
Nobody explains the setup
A managed service stays a black box on purpose, because a customer who understands it can eventually replace the provider.
You get the notes
Every job ends with a written explanation of what is on the machine, plain enough for a different engineer to pick up.
Hourly billing rewards slowness
A meter pays more for taking longer, which is a strange arrangement to agree to before any work has started.
Quoted per job, before it starts
A fix that turns out to take twenty minutes costs what it was quoted, and nobody is charging you to read documentation.
A customer who owns their setup does not have to come back, and plenty do not. That is genuinely a worse business than a monthly fee, and pretending otherwise would be the same overselling the rest of the industry does.
It is a trade. We give up recurring revenue and get people who recommend us, return with the next project by choice, and never feel trapped. That is also why every recommendation on this site can be the honest one rather than the one that keeps a subscription alive.
Anything on this site that sounds like a claim is something you can hold us to. If a page ever promises something the work does not deliver, that is a mistake to tell us about rather than a policy to accept.
What We Will Actually Put In Writing
Most pages in this industry are full of things nobody can check. User counts, audits, awards and memberships that sound impressive and mean very little to the person deciding whether to hand over a root password. These are the commitments that appear on every service page instead, and every one of them is something you can watch us do.
-
We read before we change anything
Read only access is enough to start on almost every job. The configuration gets looked at before a price is agreed, so the quote reflects the actual problem rather than a guess about it.
-
Nothing changes on a live system without a window
You pick when. Backups are taken first, changes go in a few at a time, and anything uncertain gets flagged rather than removed quietly, because the rule nobody remembers is occasionally the one holding up something important.
-
It gets tested before it is called finished
Applications tested from the networks they are used on, tunnels checked in both directions, renewals forced early, backups restored once. A system reporting healthy has told you very little on its own.
-
Every page says what the work does not cover
Limits are written on the page before you buy rather than explained afterwards. Where a job needs somebody on site, or a different tool entirely, that is said in the first conversation.
-
We sell no hardware and take nothing from what you buy
No commission, no referral arrangements, no reseller margin. If the equipment or hosting you already have is fine as it is, that is what you will be told, even when it costs us the job.
-
You end up holding everything
Root access, config files, hosting accounts, store and ad accounts where they apply, and written notes. Change every password afterwards and the setup carries on working without us.
There is no transparency report here, no membership badge and no audit certificate, because we do not have any and would rather say so than borrow the language. What there is instead is a set of behaviours you can check on the first job, which is the only proof that matters before somebody trusts you with their infrastructure.
How A Job Runs, Start To Finish
The same five stages whether it is a Raspberry Pi in somebody's cupboard or a firewall in front of an office. Nothing here is a surprise once the work starts, which is mostly the point of writing it down.
You describe it
What you have, what you need, and what stopped working if anything has. A screenshot of an error or a config export answers most of it faster than a conversation does.
We look, then quote
Read only access where it helps, so the price reflects the real problem. If the answer is that you do not need us, that is the reply you get instead of a proposal.
You approve the plan
What goes in, what comes out, and why. On anything live you pick the window, and a backup is taken before a single change is applied.
Built and tested
Changes go in a few at a time and everything is tested from where it is actually used, rather than declared working because a dashboard turned green.
Handed over for good
Credentials, config files, hosting accounts and written notes. Change every password afterwards and it keeps working, which is how you know the handover was real.
Most jobs finish inside a day or two of the access arriving. Bigger builds are staged across windows you pick, and anything urgent goes to the front of the queue without a premium attached to it.
After handover you can ask questions, come back for the next project, or never speak to us again. All three are fine, and only one of them is a problem for the sort of company that sells subscriptions.
Ask Us Whether You Actually Need This
Describe what you have and what you are trying to do. If it turns out the equipment you already own is fine, or a cheaper option would do the job, you will hear that instead of a quote. The worst outcome is a straight answer that costs you nothing.