We built this because we were sick of our own problem.
Our technical team at Relevate spends a lot of time building AI agents and automations for clients. These agents are genuinely impressive, they produce beautiful, structured HTML outputs: dashboards, reports, summaries, proposals.
And then we'd hit a wall.
Sharing that output required spinning up infrastructure. Configuring a repo. Pointing a subdomain. Setting up a deploy pipeline. For a thing that took the AI three seconds to generate, it would take a developer 30 minutes to share. Sometimes longer if DNS decided to be difficult.
This happened over and over. We'd build something great, and then the "publish it" step would swallow an afternoon. It wasn't a complex problem. It was a friction problem. And friction kills momentum.
Rana, our Technical Director, got tired of it. So he built a fix.
The idea was simple: give AI-generated HTML somewhere to go, instantly. No infrastructure. No config. Paste or push your HTML, get a live URL back in seconds. Done.
It started as an internal tool. The Relevate team used it on client projects, on internal automations, on prototypes. It worked so well that people outside the team started asking about it.
So we cleaned it up, gave it a proper home, and shipped it as Pubby.
The name is obvious once you hear it. It's the publish button the web never had.
Relevate still uses Pubby daily. Every internal report, every AI-generated client update, every quick prototype, it goes through Pubby first. So when we say it's battle-tested, we mean it's been tested by the same team that builds enterprise tech stacks for ASX-listed companies. Not a side project someone forgot about.
Founder & CEO
Avon spent years in the Australian Army before moving into business consulting. He holds an MBA, wrote a book called The Business Octopus, and has spent the better part of a decade helping Australian businesses actually use their software, not just buy it.
That last part is Relevate's whole thing. Most consultants implement a system and leave. Avon built Relevate around the opposite idea: stay until people are actually using it. That philosophy shapes everything, including Pubby. Simple tools that people actually use beat complex tools that gather dust.
Technical Director
Rana built Pubby. He's the one who got frustrated enough to stop complaining and start coding.
He leads Relevate's technical work, AI integrations, CRM systems, automations, the full stack. He has an unusual combination of enterprise-scale thinking and a bias for tools that are fast to use. Pubby is both. He built it for himself first, which is usually how the best tools get made.
Pubby is a product of Relevate, an operations, strategy and technology consulting firm based in Brisbane, with teams in Sydney, Melbourne, the US, Thailand, and India.
Relevate is a Zoho Global Enterprise Partner. Their clients include ASX-listed companies. They've helped businesses cut integration costs by $200k and reduce manual reporting by five days a month.
Here's why a consulting firm building a SaaS product makes sense: we've watched businesses struggle with software for years. Not because the software is bad, usually it's fine, but because the gap between "the tool exists" and "people are actually using it" is enormous. That gap is where Relevate lives.
Pubby came from the same observation. The gap between "the AI generated something great" and "someone else can see it" shouldn't be 30 minutes of DevOps. It should be three seconds.
Consulting gave us a front-row seat to every flavour of tech friction. Pubby is what happens when you get tired of watching the friction win.
The web has incredible infrastructure underneath it. None of that complexity should be the publisher's problem.
We're in the early days of agents generating real, useful content. Most of that content is currently stuck in terminals, chat windows, and developer consoles. That's a waste.
If you're thinking about the tool, something's wrong. Pubby should be invisible, you publish, you move on.
When sharing something takes 30 minutes, people don't share. When it takes three seconds, they share everything. The difference in output isn't incremental. It's a different way of working.
If you're building AI agents or automations, just try publishing one output. Pick something your agent generated today, a report, a summary, a dashboard, and put it on Pubby.
You'll understand in three seconds why we built this.
Try pubby.au