Effortless Autoscaling For Ruby
Explore for yourself in our sandbox app →
“Scaling is queue management. Queues ensure availability (no one is rejected when resources are busy), but create latency (waiting). Scaling is about ensuring both high availability and low latency, while minimizing cost. ”
All about queue time
Most autoscalers rely on generic metrics like CPU or memory, but queue time is the true measure of server capacity. Judoscale was built for queue time from the beginning.
Learn more about request queue time →Job queues, too!
Queue time isn’t just for web services. Judoscale also uses queue latency to autoscale your background workers, making sure your job queues never back up.
The fastest autoscaler
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 hosting costs
Most Ruby applications are way overscaled, and Judoscale can help. Our precision autoscaling algorithm lets you scale down without sacrificing performance or peace of mind.
Customize your autoscale behavior
Every Ruby app is different, and Judoscale gives you complete control. You can scale by multiple instances at a time and tweak the frequency of scaling. Each process is configured independently with a few simple sliders.
Explore the configs in our sandbox app →- Trusted by900+engineering teams
- Over2.5 millionrequests per month
- Since2017we are here to stay
Supported Ruby Stacks
Web Autoscaling
Worker Autoscaling
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.

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!

I found Judoscale through Nate Berkopec’s Rails Performance workshop. Glad I did, because we’re very happy with Judoscale!

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.

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!

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!!

Start autoscaling for free
Setup takes less than 5 minutes