Hi, I'm Brad. I've Been Thinking About This For a While.

A while back I tried to buy hotel points on two different credit cards.

Neither transaction worked. I was charged on both. The points never showed up.

It happens. Fine. What happened next is the part that stuck with me.

I reached out to the hotel's support team. Every email I sent came back with the same form letter. Not a response to what I'd actually written — a response to the category of complaint they'd decided I was filing. When I called, I got nowhere. When I pushed back on the form letters, I got the same form letters again, slightly rearranged.

I want to be clear about something: the hotel itself is great. The staff there are genuinely wonderful — the kind of people who remember your name and bend over backwards to make your stay good. I'm not here to trash them. What buried me wasn't the people. It was the system around them. They would have fixed it in five minutes if they could. They couldn't.

I eventually got my money back. Not because the hotel resolved it — they didn't. My Credit Union sorted the first charge in a few days, the way they sort most things: quickly, humanly, without drama. The second card took almost two months, working through a dispute process that exists to protect the process, not me.

The company that caused the problem played no role in fixing it. I had to go around them entirely.

This wasn't the first time I'd seen this pattern. It won't be the last.

Over the last five or ten years I've watched something accelerate that's been happening in slow motion for longer than that. Companies getting bigger, processes getting thicker, the actual humans on both sides of a transaction getting further and further apart. Support that routes you to a FAQ. Escalation paths that dead-end. The feeling of being processed rather than helped.

I've watched it at the dentist. I've watched it at hotels. I've watched it inside large organizations I've worked for. I've talked about it for years with anyone who'd listen — on a radio show, in a book project, in conversations with my wife Diane who sees it too in her own work.

People are hungry for something different. Not just as a consumer preference — as a genuine need. There is real appetite out there for companies that actually give a damn, that treat the relationship as more than a transaction, that have a human being on the other end who knows your name and your situation.

That hunger is real. I see it everywhere.

I've been in web infrastructure for thirty years. A major global cloud provider for over a decade of that. I've seen the inside of data centers during events that took down significant chunks of the internet. I've watched hosting evolve from shared boxes in someone's basement to the cloud sprawl we have now.

What hasn't evolved much is the support experience for the small end of the market — the independent founders, the small SaaS teams, the people who've built something real and are depending on their hosting to hold up when it matters. They get a dashboard, a ticket system, and a knowledge base. They get support staff who know the platform but have never read a line of their application code. They get managed hosting that manages the server and stops there.

I built AnchorHost and Haven because I wanted to be the Credit Union in this story — not the hotel. Not even Goldman Sachs. The institution that already knows you, already has context, already understands what normal looks like for your specific situation so that abnormal is immediately obvious.

Haven is managed hosting for SaaS founders. Single tenant. One person who knows your application, built your environment, and gets the alert if something goes wrong at 3am. No ticket system between you and the person responsible for your infrastructure.

It's a small operation, deliberately. That's the point.

I'm here because the Indie Hackers community is full of exactly the kind of people I'm thinking about when I write — founders who've built something real and are figuring out how to run it properly. I've been writing about infrastructure decisions and the gap between what founders assume and what's actually true, and I figured this was the right place to show up and be part of the conversation rather than just shouting into the void.

I don't have all the answers. Thirty years gives you a lot of hard-won opinions and a healthy respect for how fast things can go sideways. Happy to share what I know, hear what you're working through, and have the kind of conversation that's worth having.

If Haven sounds like something that might fit where you are — real product, real users, real stakes, not yet at the scale of needing enterprise infrastructure — you can find us at anchorhost.io.

If it doesn't fit, that's fine too. I'm still happy to talk infrastructure.