Runtime and processes
Check Ruby applications that need the correct runtime, Bundler dependencies, application server, reverse proxy, workers, database access, and restart strategy.
Ruby application hosting
Run your Ruby application with its required version, gems, database and workers. Use a self-managed VPS to control the server configuration.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check Ruby applications that need the correct runtime, Bundler dependencies, application server, reverse proxy, workers, database access, and restart strategy.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
Ruby web apps commonly run on Puma behind a reverse proxy, and capacity comes from two dials: worker processes, which cost full copies of the application in memory, and threads per worker, which share memory but contend on the interpreter. MRI Ruby runs one thread of Ruby code per process at a time, so CPU bound work scales with workers.
Boot time and memory growth are the operational facts of Ruby hosting. Workers that grow over days usually hold leaking objects or unbounded caches, so configure worker recycling after a set number of requests, and run bundle install from the lockfile during deploy so the server never resolves gem versions live.
Record resident memory per Puma worker after boot and again after a day of traffic. Steady growth means recycling workers on a request count, not adding memory.
Set the connection pool at least equal to threads per worker. A pool smaller than the thread count makes requests wait for a connection under load.
Preloading the app before forking lets workers share memory pages. Measure the saving with real process memory, since gems that write at boot reduce the benefit.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.