One developer, a lot of broken sites, and a local stack that finally does what it’s told.
Who I am
I’m Rob Carey. I build websites and fix them when they break, and I’ve been doing it long enough to know why they break. Usually it’s something somebody copy-pasted off a forum in 2014 that has been quietly load-bearing ever since.
I live in the real world of web development — the one where the deadline was yesterday, the client is breathing down your neck, the CMS is duct-taped together, and nothing works the way the README promised. I’ve patched PHP disasters at 7 a.m. before the coffee kicked in. I’ve read code that deserved jail time. Some of it I wrote.
I’m not precious about elegant. I don’t care whether the code follows a pattern with a capitalised name. I care that it works, works reliably, and doesn’t fall over the first time it meets real data. If your answer sounds like a TED Talk, I’m already out. Just give me the damn file.
Why Kiln exists
Because every local setup I ever cobbled together wanted a weekend of my life before php -v printed the number I was expecting.
I wanted real Apache and real nginx — the same servers production runs — not a clever approximation that behaves slightly differently right up until launch day. I wanted one client on PHP 7.4 next to another on 8.5, running at the same time, without juggling PATH variables like a street magician. I wanted HTTPS that just worked, so I could stop clicking through browser warnings and start trusting what was on my screen. I wanted every test email caught before it reached a real human. And I wanted all of it in one folder, so that when I was finished I could delete it and my machine would be exactly as I found it.
I got tired of wishing that tool was already installed. So I built it. Then I used it every day, swore at the parts that annoyed me, and fixed them. That’s Kiln: a local stack built by someone who has to live with it.
How I roll
Direct
No meandering. No buzzwords. If it can be said in one sentence, that’s the sentence you get.
Just give me the file
Show me the code that works. I’ll read it faster than you can explain it, and I’ll spot the bit that doesn’t.
Details matter
I catch what others miss. It’s a gift. It’s also why I’m still looking at logs when everyone else has gone home.
Load is the only review
Keep the pitch deck. If it doesn’t hold up with real traffic and real data, it’s garbage, however nice the diagram was.
Loud, then fixed
I’ll trace variables, dig through logs and curse at the screen. Eventually it works, because I don’t quit until it does.
Duct tape counts
Sometimes it isn’t pretty. It holds. A few things still run today only because I made them run.
What that means for Kiln
- No mystery modals. Good UX is clarity and speed, and never making you think “now what?”. Every screen in Kiln was built by someone who has rage-clicked through enough bad ones.
- It respects your machine. Signed installers, one data folder, nothing scattered across your system, and an uninstall that actually uninstalls. I’m the person who cleans up after bad software. I wasn’t going to ship any.
- It’s used in anger. This website is developed on Kiln. So is everything else I work on. When something annoys me, it gets fixed, because I’m the one it annoyed.
- If it breaks, tell me. The community goes straight to me, and the changelog says who asked for what. Bug reports with logs attached get a special place in my heart.
What Kiln is not
Kiln isn’t trying to be everything. It’s a local web stack for PHP sites that behaves like production and then gets out of your way. It won’t write your code, deploy your client’s site at 2 a.m. or make the coffee. It will make sure the environment is never the reason something broke, which in my experience is about half the reasons.
Go download it. Your first site is free. So is telling me what I got wrong.