Judoscale: One-Click Autoscaling for any hosting platform ✨

Greetings, Judoscalers! Anybody else get a nice helping of early-winter snow this month? Winter came early for Ohio!

With Christmas and New Years just a few days out, our whole team (yes, all three of us!) here at Judoscale wish you and your teams, families, neighbors, and friends that happiest of holidays and hopefully some great time off 🙂.

Until then, we’ll close out the year with one last batch of interesting news, positive updates, and a sneak peek into the exciting plans we have in store for the coming year:

• 📊 2025’s Utilization-Based Autoscaling
• 💰 Heroku Direct Rolling Out
• 🔢 The Universal PaaS Pricing Calculator
• 🔁 Judoscale Migrates to Render?
• 📝 (ICYMI) What Nearly a Decade of Autoscaling Your Apps Has Revealed to Us

Let’s dive in!

📊 2025’s Utilization-Based Autoscaling

We’ve been rolling out something big this past season — a fresh take on autoscaling that doesn’t just react to traffic spikes but prepares for them. We call it “proactive autoscaling”. And it’s radically simple: you tell Judoscale the level of capacity you want to maintain, and it continuously adjusts your scale so you always have headroom for sudden bursts. For some background, check out “Autoscaling: Proactive vs. Reactive”, then dive into our nuts-and-bolts explainer on how we’re actually able to accomplish this new model here:

Utilization-based, proactive autoscaling is a major new chapter in Judoscale’s offerings and autoscaling altogether! For the right applications, it’s an epiphany.

💰 Heroku Direct Rolling Out

We’re excited to let you all know that we’ve just finished building our Heroku direct-billing integration (last week!) and will be offering it beginning in early 2026. Judoscale works excellently as a Heroku add-on but if you prefer to pay directly at a bit of a discount, you can proactively switch over to our direct-billing plan. That is, running Judoscale for your Heroku-based application(s) but doing so outside of the Heroku Add-On and paying via direct-billing, at our direct-billing pricing, rather than Heroku’s aggregate invoicing.

You’ll hear more from us in the coming months about this, but feel free to give this page a read in the meantime 👍

🔢 The Universal PaaS Pricing Calculator

And speaking of direct-billing and multi-platform support... did you know that we built out a universal pricing calculator earlier this year? Now you can plug in some data and know what pricing across various vendors will look like for your app before you spend hours migrating over!

Its goal is simple: compare the face-value, out-the-door costs on each platform for your specific application.

So... thinking about jumping to Render or Fly? Maybe you’ll feel stronger about that idea once you see you’ll save fifty percent of your hosting costs! Or maybe you’ll feel less inclined if you see that you’ll double your hosting costs! The goal here is visibility. Check it out here!

🔁 Judoscale Migrates to Render?

Okay, no, not exactly. But also yes! Judoscale’s main production environment still runs primarily on Heroku, but we do have dynamic backups ready to (manually) hot-swap if the need arises. We also have a staging environment that we’ve cloned onto every platform we support!

Adam recently took some time to record a video walkthrough showing that process: what it actually takes to migrate an eight-year-old, real-world SaaS application (Judoscale) from Heroku over to Render, far beyond the typical “Hello World” demo. Web processes, workers, clocks, environment variables... it’s the full gamut! This video is a real migration playbook and we recommend checking it out! See it here:

📝 (ICYMI) What Nearly a Decade of Autoscaling Your Apps Has Revealed to Us

(In Case You Missed It) We posted this article a couple of months ago and got great feedback about it, so we wanted to send it along again for those that didn't see it the first time around. Cheers!

Our little team is extremely proud to be inching closer to that ten-year mark — autoscaling millions of times along the way! We put our heads together and thought about some interesting insights that we could give back after so many years staring at a single thing (autoscaling)... and we feel like we’ve got some good points to share. Highly recommended reading for all devs! Read here:

And that’ll do it for us this month, friends! Happy Holidays, Merry Christmas, Happy New Year, and if you’re anything like me, try to stay warm in these frigid times of winter 🥶😅. We can’t wait to share more exciting developments with you in 2026 🎉

— Jon & The Judoscale Team