I’m Keith Groben. People ask why we don’t just build the site, hand over the code, and let them host it somewhere cheap. The honest answer is that I’ve seen how that story ends, and I won’t put my name on it.
We only build sites we host and maintain. Every path. No handoffs to self-host.
Why won’t you just give me the files?
Because the files aren’t the product. A website isn’t a one-time deliverable you collect and store on a shelf. It’s a living asset, and living things need tending. The day it ships is the day it starts aging — search rules shift, AI answer engines change what they reward, browsers update, security holes appear, and the copy that was current slowly stops being true.
Hand the code to a stranger’s server and there’s nobody minding any of that. Six months later it’s slow, a year later it’s stale, and it slides right back to looking like the 2022 brochure it replaced. That’s not a site anymore. To a customer running their four-minute check, it reads like a gamble.
I’d rather not build that. So I don’t.
A boundary, not just a perk
I’ll be straight: this is also a line I draw for my own sake. I can’t promise a site is fast, secure, and findable on infrastructure I don’t control. If something breaks on a host I’ve never seen, it becomes my reputation and someone else’s access. So the answer is that R7 hosts and maintains every site it builds — the speed, the security, the new pages, the schema that keeps it readable by AI. That’s how I can actually stand behind the result.
It’s a boundary. It’s also why the work stays good.
So what does maintained actually mean?
It means the site keeps working after launch instead of decaying. Hosting and monitoring are handled. Speed and security are watched. On the plan, new pages keep arriving so the site grows instead of going stale. Even if you buy the build outright, hosting and maintenance stay with us — because a site nobody tends is a site nobody can trust.
A website is either tended or it’s rotting. There’s no third state. We only do the first one.