Unmanaged Rails hosting

Ruby on Rails hosting on an unmanaged VPS

Use an unmanaged KVM VPS for Rails when you need control over Ruby, Puma, the database, background jobs, reverse-proxy behavior, and the deployment method.

Join waitlist Compare plans →

Bitfoo opens for orders soon.

Platform: Unmanaged VPS
App server: Puma
Deployments: Your workflow
Storage: Persistent NVMe

Choose by responsibility

Choose VPS when Rails needs a durable, customizable host

Rails can run in several deployment models. A Bitfoo VPS fits a team that wants direct control and has a clear owner for production operations.

Direct control

Choose a Bitfoo VPS

Operate the complete Rails stack on a persistent server.

Custom Ruby and native package requirements
Puma, background jobs, and database services need deliberate sizing
The team owns deployments and Linux operations

Review the VPS platform →

Managed operations

Consider a managed Rails platform

Reduce server work when control of the host is not a product requirement.

The team wants platform-managed deploys and runtime
No one is assigned to patch and monitor Linux
Automatic service orchestration matters more than host access

Discuss the workload →

Production foundation

Treat web and background work separately

A Rails application is usually a set of cooperating processes, not one command running behind a domain name.

Puma process model

Set worker and thread counts from measured memory use and concurrency rather than copying a generic maximum.

Background jobs

Run job processors under supervision, monitor queue delay, and restart them safely during releases.

Database lifecycle

Choose where the database runs, back it up independently, and design migrations for the deployed application state.

Repeatable deployments

Use a release workflow such as Kamal, Capistrano, or another documented process with health checks and rollback.

Plan comparison

Size the complete Rails process set

Account for Puma, background workers, the database, cache, deployment tasks, and the operating system—especially when they share one VPS.

Swipe horizontally to compare every plan.

Compare unmanaged VPS plans for Ruby on Rails Hosting.
Specification	VPS-1 Development, staging, or a light Rails app	VPS-2 A small production Rails application Recommended starting point	VPS-4 More Puma workers, jobs, or adjacent services	VPS-8 Higher-traffic or multi-application servers
vCPU	1	2	4	6
RAM	1GB DDR5	2GB DDR5	4GB DDR5	8GB DDR5
Storage	25GB NVMe	50GB NVMe	100GB NVMe	200GB NVMe
Bandwidth	1TB	2TB	4TB	6TB
IPv4	1	1	1	1
Price	Coming soon	Coming soon	Coming soon	Coming soon
Availability	Join waitlist →	Join waitlist →	Join waitlist →	Join waitlist →

Exact prices will appear when ordering opens. VPS plans are unmanaged and do not include an automated backup service.

Before deployment

Make deployment and data changes reversible

Production Rails work is safest when application, process, and database changes are coordinated.

01
Pin the runtime

Document the Ruby version, native dependencies, JavaScript tooling, and environment variables required by the release.
02
Model every process

List web, job, scheduler, cache, and database processes with their restart and health-check behavior.
03
Stage database migrations

Use backward-compatible steps when old and new application versions may overlap during deployment.
04
Test rollback

Confirm that code, assets, processes, and database state can return to a known working condition.

Related hosting guidance

Docker hosting Use containers when the Rails release will be packaged and deployed as images. Node.js hosting Review production process and reverse-proxy patterns for another application runtime. VPS plans Compare resources and the unmanaged responsibility boundary.

Common questions

Is Rails pre-installed?

No. The VPS starts as a server environment. You install and maintain Ruby, Rails, the database client, proxy, process supervisor, and any native dependencies.

Can I deploy with Kamal or Capistrano?

Yes. A VPS provides the SSH and server control those workflows need. Your team remains responsible for configuring, testing, and maintaining the deployment method.

Should the database run on the same VPS?

It can for smaller deployments, but that means application and database processes compete for the same memory, CPU, storage, and recovery boundary. Size and back up accordingly.

Which plan should I start with?

VPS-2 is the general production starting point shown here. Measure the memory used by Puma, workers, database, cache, and deployment tasks before choosing a final size.