Today we released DogHouse 3.0.

If you are a FatLab client, nothing about how you use it changes. Your requests, your websites, your invoices and your team are right where they were on Friday. Most of what made 3.0 a major version happened underneath, and I will get to why.

This post isn't a feature tour. If you want that, the DogHouse 2.0 post and our client portal page have it. This is the business story: how a client portal we built for ourselves turned into the system the whole company runs through, and what that did to how we work.

From portal to backbone

We launched DogHouse 1.0 in 2025 and shipped 187 releases on it. Version 2.0 came out in June, and we shipped another 247 releases in the five months since. That is more than 430 releases on software that, a few years ago, I would have told you we would never write ourselves.

Somewhere in those five months DogHouse stopped being "our client portal" and became the backbone of FatLab. Every part of the business either lives in it or plugs into it: our support desk, our AI, our development team, our alarms, our billing, our reporting, and the portal you log into. They all read from and write to the same record.

That sounds like plumbing, and it is. But it changed how fast we work and how much you can see, so here is what it looks like from the inside.

One request, start to finish

Say you email us because a form on your site stopped sending.

It becomes a ticket. DogHouse turns your email into a request, files it under your organization, and starts a clock.

Our AI reads it within minutes. Guinness, our AI developer, works out what you are asking, which website it is about, how complex the job is, and whose desk it belongs on. Then he does the homework: he looks at the site and your history, read-only, and leaves a note on the ticket so whoever picks it up starts with a diagnosis instead of a blank page. I wrote about how that works in How We Use AI at FatLab.

Nothing gets lost. If nobody has picked a request up, DogHouse pings whoever is on call. If it is urgent and nobody has touched it, an alarm goes off on our phones and keeps going until someone acknowledges it, nights and weekends included. That alarm system is watched from outside our servers, so if it ever stopped running, we would know.

You hear from us. A person replies. If our response window runs out first, Lacey, our AI coordinator, sends a short note so you know we have it, and she never promises anything.

Bigger jobs go to our development team without falling through the cracks. When a job needs our dedicated development team, the brief they work from is linked to your ticket, and DogHouse watches it. When they reply, their update comes back into your ticket and the status moves on its own. Nobody has to remember to go check.

The work, the time and the invoice point to the same place. The change we make, the notes on why, the time we log and the line on your invoice all trace back to that one ticket. Support time and development time are counted separately, so your dashboard shows which hours were included in your plan and which were not.

You can see all of it. While this is happening, your portal shows where the request stands and whose move it is, in plain language.

None of those steps is special on its own. What changed is that they are no longer separate. There is no copying a ticket number between systems, no spreadsheet tracking which job went to which developer, no reconciling time against invoices at the end of the month.

Why owning it mattered

We could have stitched this together from a help desk, a CRM, a billing tool and a project board. Plenty of companies do. The problem shows up when you try to bring AI into it. Off-the-shelf tools give an AI whatever access the vendor decided on. Because DogHouse is ours, we decide exactly what each AI can do.

Each of our AI tools has its own key, and the key decides what it is allowed to touch. Every action it takes runs through the same code our team uses, lands in the same activity log, and can be cut off without affecting anything else. That is why we are comfortable letting AI do real work in our systems: we built the guardrails ourselves, so we know where they are.

What it changed for our clients

Two things, mostly.

We got faster while the work grew. In September I shared our numbers: compared with a year earlier, we were handling roughly twice as many support tickets, and our typical first reply on a business-hours request had gone from two or three hours to under an hour. Most of that came from the homework already being done by the time a person sits down.

You see what we see. Your dashboard shows how quickly we responded to your recent requests, measured from your message to our first reply and counted in working hours, so the number is honest. About one request in ten is one we open ourselves, a security update we spotted for example, and those are labelled "We opened this for you" instead of pretending you asked. Your websites show uptime, updates, blocked threats, backups and real traffic analytics. If we know something about your website, you can see it too.

So why is this 3.0?

Because of what is underneath. Until now, the question "which requests and websites is this person allowed to see?" was answered separately on seven different pages. In 3.0 one rule answers it everywhere. For our existing clients it gives exactly the same answer it always did. But it means DogHouse can now serve more than one kind of client, and that opens the door to new services.

The first one is for agencies.

Introducing the White-Label Support Desk, built on DogHouse (Beta)

Many of the agencies we work with build great websites and then have nobody to answer the phone when one breaks at 9pm on a Saturday. The White-Label Support Desk gives them a support portal and a support email address in their own name, for their own clients. Their clients sign in, open requests, watch them move and see what is being done to their websites. Our team does the work behind it, around the clock, and FatLab's name appears nowhere. The agency is copied on everything and keeps the relationship.

It runs on everything described above: the same triage, the same alarms, the same status tracking and site reporting our own clients get. We are calling it a beta for now, because we are switching it on with agency partners one at a time. If you run an agency and want to know more, see our white-label hosting page or get in touch.

Still not for sale

The same caveat as last time: DogHouse is not a product you can buy. There is no sign-up page and no pricing tier. It is how we run FatLab, and it is included with every plan we offer.

If you are a client, log in and look around. And if something would make it better, tell us. A lot of those 430 releases started that way.