Latency-aware Autoscaling For Scalingo
with queue time instead of CPU or memory
“Judoscale has been live in our Scalingo app for several weeks now with really solid results. Autoscaling is doing its job, and we love the calendar feature. ”
Engineered for your stack
Queue time, not CPU or memory
CPU and memory are indirect signals—they tell you how hard your containers are working, not whether your users are waiting. Queue time is the true measure of server capacity, and Judoscale is the only autoscaler for Scalingo that uses it.
Learn more about request queue time →Web containers and background workers
Queue time isn’t just for web containers. Judoscale also uses queue latency to autoscale your background workers, ensuring your job queues never back up.
Autoscaling at ludicrous speed
A capacity issue needs to trigger autoscaling as quickly as possible, and Judoscale is the fastest autoscaler available. Our autoscaling algorithm runs every 10 seconds, ensuring your app scales up before users notice an issue.
Reduce your Scalingo compute costs
Your Scalingo containers are probably overscaled, and Judoscale can help. Our autoscaling algorithm allows you to scale down without sacrificing performance or peace of mind.
Customize your autoscale behavior
Every app is different, and so Judoscale gives you complete control over how your app autoscales. You can scale by multiple containers at a time and tweak the frequency of scaling. Each container type is configured independently with a few simple sliders.
- Trusted by900+engineering teams
- Over2.5 millionrequests per month
- Since2017we are here to stay
Still have questions?
Check out our docs for a whole lot more. If you still can’t find what you’re looking for, send us an email!
What languages and frameworks does Judoscale support?
We support many web frameworks and job/task queues for Ruby, Python, NodeJS, and Java. See the full list in our docs.
What data can Judoscale access in my app?
Our language-specific packages only collect queue-related metrics for requests and job queues along with basic process metadata. No actual request or job data is ever collected.
Can we have a call to see if Judoscale makes sense for my app?
Sure, let’s talk! Use this link to book a call with us.
You guys are rock stars!! I think this is the 3rd time now that you've already had a solution ready to go to solve our problem. This is exactly what I was looking for!!
Judoscale’s deep integration with Sidekiq queues let us easily tag which queues we wanted a faster response. We were able to tune our scaling sensitivity for exactly our usage pattern of intermittent batches of large jobs.
As we onboarded larger customers, we expected traffic peaks that needed to be addressed quickly. Judoscale did exactly that.
If I was the king of the world, I would make it illegal to horizontally scale based on execution time. Scale based on queue depths, people!
Chameleon has been extremely stable thanks to Judoscale. We have very high spikes in traffic, and I don’t even have to think about it.
We could see the care in Judoscale’s documentation, the gems were well-documented and designed with a general sense of quality.
Request queue time is the single most important part of this. Scaling by CPU and memory consumption makes no sense—your server should have stable memory usage and nearly 100% CPU utilization.
We’re really impressed by the simplicity and ease of use of Judoscale. We’ve gone from constant worries over site performance, to complete confidence in our configuration. What a great tool!
Start autoscaling for free
Setup takes less than 5 minutes