HT

Hubfly Team

•Dec 01, 2025•Announcement

Look, we’ve all been there.

You finish the fun part (writing code), push to GitHub, and then spend the next four hours fighting with some cloud console that looks like it was designed late night with a hangover.

Firewall rules, IAM policies. “Why is my container OOM-killed again?” I just want my stupid Next.js app to run, not take a second mortgage on a Kubernetes cluster.

So we built Hubfly.

Hubfly is cloud hosting platform using docker containers under the hood, with auto-magic builds, real persistent storage, and a custom reverse proxy, with project isolation and security features, combining all of these into a single to use one click.

Okay, what actually makes this different?

1. The Builder That Doesn’t Make You Write a Dockerfile (Unless You Really Want To)

You know what’s annoying? Having to write a Dockerfile for “Hello World” in 2025.

Our builder is a little Go daemon that looks at your repo and goes:

• “Oh, package.json → Node, cool.”
• “No Dockerfile? I got you, here’s a perfectly fine image.”
• “Wait, you do have a Dockerfile? Respect. I’ll use yours.”

It streams the logs straight to your browser so you can watch npm ci crawl at 2 KB/s and feel the same pain you always feel, but at least you’re not SSH’d into some random VM.

And yes, it uses BuildKit under the hood, so multiple builds are actually fast instead of the usual “let me redownload the entire internet” move.

2. Storage That Doesn’t Disappear When You Blink

Ephemeral containers are cute until you realize your Postgres data lives about as long as my New Year’s resolutions.

Hubfly gives you real persistent blocks you can:

• Attach/detach whenever you want
• Move between containers in the same project
• Pay for exactly what you use (size × uptime)

It’s basically Docker volumes that don’t make you cry.

3. Networking That Doesn’t Require a PhD

By default your containers get no public IP. Zero. Nada. Instead you expose ports → we give you a random c4e2a1f8.hubfly.space subdomain.

Want a proper domain? Point a CNAME, click two buttons, done. Want HTTPS? We run a custom NGINX + Certbot appliance that actually tests configs before reloading (because nothing says “fun Friday night” like accidentally blowing up your entire proxy config).

Zero downtime deploys, automatic renewals, and we even handle the stupid HTTP-01 challenge for you.

4. You Can Actually Choose How Much CPU and RAM You Want

None of this “Small, Medium, Large, Good Luck” nonsense.

Sliders go brrr:

• Need 0.2 vCPU and 256 MB for your tiny API? Cool.
• Need 8 cores and 32 GB because you’re doing something unholy with database? Also cool.

You pay per second of CPU, per GB-hour of RAM. No weird “credits” or “instance hours” – just look at the little cost calculator and see exactly what it’ll cost before you click “Deploy”.

We even have a completely free tier with 360 hours/month of shared runtime – enough for a blog, a demo, or that side project you swear you’ll finish one day.

5. Auto-Sleep Because Electricity Isn’t Free

Leave your dev instance running? It’ll politely go to sleep when nobody’s using it and wake back up the moment someone hits the URL.

Your wallet will thank you. Your future self will thank you. The planet might send you a fruit basket.

6. Team Collaboration That Doesn’t End in Billing Disputes

Here’s the spicy part: billing is per user who owns a project ,not per project shared.

You invite your friend Alice to your project. Alice will be able to play in your project, add containers, destroy containers, and manage permissions. Only You as the owner of the project will be billed for the resources used.

You keep collaborating.

7. Templates So You Don’t Have to Google “How to Deploy Minio Again”

We ship ready to go templates for the usual suspects:

• Next.js (with SSR, static export, whatever)
• Postgres / Redis / MongoDB / Meilisearch
• Strapi, Redis,Vs code server,Minio,Mongo and more
• Even a blank Nginx container if you just want to proxy something weird

Or you can:

Click → connect GitHub → done. Your grandma could deploy a blog with this thing.

We’re Still Cooking

This is very much v0.1-with-sharp-edges. Some buttons are a little janky. The docs are… let’s call them “minimalist”.

But the core loop works:

1. Connect Git repo,Create volume,Create container
2. Click deploy
3. It just works™

And that’s honestly more than I can say for the platforms.

Come Break It With Us

We’re opening early access right now. No waitlist, no “founder approval”, no LinkedIn DMs required.

Just go to https://hubfly.space, sign up, and start deploying stuff.

If it explodes, tell us. If it’s magically perfect, tell your friends.

Either way, we’ll be here probably refreshing the logs at 2 AM like the rest of you.

See you on the other side.

– The Hubfly Team (just sleep deprived devs)

• HubTunnels
• Architecture