Secure by default, not as an upsell
Backups, updates and safe settings are part of the build. I have seen what it costs when they are an optional extra somebody declined.
Durbanville, Cape Town — 33.9°S
Leo Liebenberg
Engineer · Founder of Trevern Technologies
I build websites and the automation behind them. Before that I built a system that checked thousands of machines against the day's live vulnerability data every morning — unattended, and right with nobody watching.
- Hand-written static HTML
- No page builder
- WhatsApp booking that answers at 21:00
- n8n, self-hosted
- Anthropic API
- Cloudflare
- AI that drafts, a human that approves
- POPIA from the first line
01 — Who
I'm an engineer who got tired of tools that lie.
I build websites for companies and groups, and the automation that runs behind them — bookings on WhatsApp, quotes that send themselves, assistants that draft the reply and wait for a human.
I came up through security, not marketing. It shows in what I leave out: no database to breach, no plugin stack to patch, nothing to fix on a Sunday night. Still studying it — BSc Cybersecurity and Networking at Eduvos.
This page is hand-written static HTML. One stylesheet, no framework. View the source — it is all in front of you.
02 — What I build
Systems that tell you the truth about themselves.
A website brings the enquiry in. What happens next is where companies lose money — and it is almost always the same four jobs.
-
01
A message at nine at night
Answered while you are asleep. Booked if it is routine, flagged if it is not.
-
02
A booking written on a pad
Then typed up twice, and once wrong. Taken straight into the system instead.
-
03
The quote that never left
Drafted from the job, waiting for you to read it and press send.
-
04
The invoice nobody chased
Chased on schedule, politely, until it is paid or you say stop.
Someone hears your name and looks you up on their phone, on mobile data, with one bar of signal. What loads in the next two seconds decides whether they call. That is an engineering problem before it is a design one — so the sites are hand-written HTML and CSS, or Astro, built on Cloudflare Pages, Workers and KV, and measured against Core Web Vitals with structured data and accessibility in from the start.
03 — The hard one
I built a platform that checked every machine, one at a time.
The tools on the market flagged machines that had already been patched, and reported at company level when the only question that matters is which machine, right now.
- Thousands
- of machines, checked individually — not sampled, not estimated
- Every morning
- against that day's live vulnerability data, not last month's scan
- Unattended
- nobody watching it run, which is what made correctness the hard part
A false clean is worse than no answer at all, because somebody acts on it. So it proved the result per machine instead of asserting it in aggregate.
Everything I ship now is that same shape on a friendlier problem: fetch the real state of the world, compare it to what should be true, involve a human only where judgement is genuinely required.
04 — How I work
Four things I won't trade away.
AI that drafts, humans that decide
Assistants answer the routine questions and draft the rest for approval. Nothing a customer could hold you to goes out unattended.
You own all of it
The site, the tools, the data, the client list — yours from day one and exportable any day. Nobody should keep your business by holding it hostage.
Plain English, fixed price
One price in writing before anything starts. If the job runs bigger than I judged, that is my problem — not an invoice you did not expect.
05 — The studio
When it's a job rather than a conversation, it goes through Trevern.
Trevern Technologies is the studio I founded, in Durbanville, in Cape Town's northern suburbs. Websites, AI and automation, mobile apps for iPhone and Android, and online presence — for companies and groups across the Western Cape, and remotely anywhere in the world.
Behind Trevern is a team of engineers, working in-house. The people who scope the work are the people who build it. No account manager in the middle.
Straight answers
Questions people ask.
Who is Leo Liebenberg?
Leo Liebenberg is an engineer in Durbanville, Cape Town, and the founder of Trevern Technologies. He builds websites, AI and automation, and mobile apps for companies and groups, after coming up through cybersecurity and vulnerability management.
What did you build before Trevern?
A vulnerability-management platform. It pulled the day's live vulnerability data every morning, checked thousands of machines against it individually, and proved the result per machine instead of reporting at company level. It ran unattended, which is the hard part — nothing was watching it, so it had to be right.
Do you work with businesses outside Cape Town?
Yes. Websites, automation and apps are built and delivered remotely, so those clients can be anywhere in the world. Only on-site work has a boundary, and that is the Western Cape, by appointment.
Why does a web designer have a security background?
Because it changes what gets built. Static sites with no database to breach, no plugin stack to patch, backups and updates included rather than sold as an extra, and personal information handled the way POPIA expects from the first line of code.
How do I hire you?
Through Trevern Technologies. Say what the problem is and you get a straight answer and one fixed price in writing before any work starts. If it turns out bigger than I judged, that is my cost to carry, not a surprise invoice.
Contact
Let's talk.
A website, a booking system, an assistant that keeps the inbox moving — or just a second opinion on something you have been quoted for. Say what the problem is and you will get a straight answer.