[ ]
one engineer. zero handoffs.
Kelu IT exists because “enterprise IT” usually means enterprise attitude: slow queues, jargon, and a different stranger on every callback. We keep the enterprise-grade engineering and drop the rest — one genuinely technical engineer who answers fast, explains clearly, and treats your stack like his own.
{
engineer: "luke",
based: "sydney",
since: 2021,
handoffs: 0,
anomaly: "a"
}[ ]
answers, not ticket numbers
A ticket number is a receipt, not a result. Every request gets a human answer and an honest ETA — usually the same day.
plain english, always
If we can't explain the fix without acronyms, we don't understand it well enough yet. You'll always know what happened and why.
automate the boring stuff
Humans for judgement, scripts for repetition. If a task shows up three times, it gets automated — and monitored.
own the outcome
No “that's a vendor issue”. If it's in your stack, it's our problem — network, cloud, code, or the printer nobody admits to buying.
[ ]
no big-bang migrations. no drama.
The same loop, every engagement — whether we're taking over your whole stack or just untangling the Wi-Fi.
step_01
listen & audit
We start by reading your environment like a codebase — what's solid, what's duct tape, what's quietly on fire.
step_02
stabilise
Stop the bleeding first: backups verified, security holes closed, the recurring pain sorted before anything shiny.
step_03
standardise
One way of doing things, documented. Naming, patching, onboarding — boring on purpose, so nothing depends on memory.
step_04
automate
Anything done twice gets scripted. Scheduled jobs and workflows quietly do the repetitive work so nobody else has to.
step_05
stick around
No set-and-forget. The engineer who built it keeps supporting it — and it improves as your business changes, not on a sales cycle.
[ ]
when you call kelu, you talk to the engineer who built your network — not a call queue.
That engineer is Luke — Sydney-based, five years deep in business IT, and the same pair of hands across your network, your cloud and your code. Before Kelu: multi-site server environments with AD synced across locations, full cloud migrations, and end-to-end Ubiquiti buildouts — network, cameras and door access. He started Kelu IT in 2021 because business IT deserved a more personal touch. The person who quotes the work does the work, and picks up the phone afterwards.
// off the clock: gaming, friends, family — order depends who's asking.
{ the bus-factor answer }
// one person, documented like it isn't: your environment is written down properly — configs, credentials, runbooks — so nothing lives in anyone's head, and nothing depends on memory.
[ say hello ]
tell us where IT hurts.
// or email hello@keluit.com.au