GoDeploy - A By Product of Building Audetic

Mat Silva

18 Apr 2025 — 3 min read

godeploy.app

GoDeploy was created to solve a real problem I had while building Audetic's user facing apps and sites... You see back in the day, deploying a single page app(SPA) or static site was dead simple. We had tools like now, firebase deploy, etc that offered one command deployments. I loved those tools.

But when I reached for them, their SPA support was largely, gone?

What the heck happened?

SSR frameworks did. The entire React ecosystem has over rotated. What was once the V in MVC, is now a full blown server side framework that encourages newcomers to 'lock in' to these overly-prescriptive frameworks.

Just look at the react docs today (as of 4-18-2025).

The react docs, pushing new comers to full-stack frameworks, aka SSR

And note...

The push to full-stack frameworks
No mention of vite as an option to scaffold a react app.
A big green note explaining our misconceptions about these frame-works.

It seems to me that the writing is on the wall

Albeit, I did try...

I am not unfamiliar with these SSR frameworks, I just hadn't tried them for client side only apps... & not wanting to reinvent any wheels, I decided to give them a go, thinking,"ok maybe it will be the least path of resistance to build and ship a client side app these days."

But while I was wrestling the framework, I had a moment where I was like why is this so much harder than it needs to be? Are people really happy with with this for client side only apps?

I just needed to be able to ship a relatively simple client side app, quickly. So I reached for vite to scaffold my react app. It was a breeze!

But now for deployments... oof. Wow. How did we take so many steps backwards?

Did I really need to reinvent the wheel? I guess so... so I did and it was glorious.

Then I Stepped Back and Asked:

Wait, what if I made this available... to everyone?

I built it for Audetic. But the more I used it, the more obvious it became: this isn’t just an internal tool. This should be the default way to ship SPAs.

Why are we still pretending frontend teams need full-stack platforms just to host static files? How did we let these platforms convince us they can charge us for bandwidth for our app's static assets? – A commodity that is practically free due to CDN technology.

Why are simple frontend apps being pushed into SSR runtimes and complex CI setups?

GoDeploy has brought back my joy! ✨ 🤗 – in shipping frontend apps.

What It Does

One command: godeploy deploy
Instant HTTPS + CDN delivery
SPA routing built-in
No config. No cloud setup. No SSR required.
Works with any client side stack: React, Vue, Angular, Svelte, whatever you wantt