Managed shared hosting
WordPress Hosting
Run WordPress on LiteSpeed, NVMe storage, and isolated account resources while Bitfoo manages the hosting server, control panel, and routine platform operations.
View hosting guidance →Hosting by workload
Hosting by application
These pages translate application requirements into one of two products: managed shared hosting or an unmanaged KVM VPS. Laravel can use either, depending on its process requirements.
Bitfoo opens for orders soon.
- Managed apps
- 2
- Two-path apps
- 1
- VPS workloads
- 7
- Ordering
- Opening soon
WordPress and WooCommerce
Laravel
Custom runtime and server control
Guidance available now
Choose by responsibility
Two hosting paths underneath every workload
Choose the operating model before choosing capacity. A larger server does not replace platform management, and a managed account does not provide root access.
Bitfoo manages the platform
Managed shared hosting
Use the supported LiteSpeed, PHP, database, control-panel, certificate, and backup workflow.
- Best fit for WordPress and WooCommerce
- Application maintenance remains with you
- No Linux administration or root access
You manage the server
Unmanaged KVM VPS
Install and operate the runtime, proxy, database, workers, containers, and other services the application needs.
- Best fit for persistent or custom runtimes
- Full root access and defined server resources
- You own patching, monitoring, security, and backups
Managed shared hosting
Applications that fit the supported hosting platform
Bitfoo operates the hosting server and account platform. You maintain the site, content, extensions, users, and application configuration.
Managed shared hosting
WooCommerce Hosting
Run a WordPress store on LiteSpeed and NVMe storage with daily recovery points, while keeping cart, checkout, account, inventory, and payment behavior in the application’s control.
View hosting guidance →Choose from process requirements
An application with two valid paths
Straightforward Laravel applications can use Business or Pro shared hosting. Persistent queue workers, Redis, Octane, or custom services move the workload to VPS.
Shared hosting or VPS
Laravel Hosting
Use Business or Pro shared hosting for a straightforward PHP and MySQL application. Choose an unmanaged VPS when Laravel needs persistent workers, Redis, Octane, or custom server services.
View hosting guidance →Unmanaged KVM VPS
Workloads that require a server environment
These applications need a persistent runtime, custom system packages, containers, background services, or direct server control. Every page begins with the unmanaged responsibility boundary.
Unmanaged KVM VPS
Next.js Hosting
Run a Next.js server on an unmanaged KVM VPS when you want to own the Node.js version, reverse proxy, process supervision, persistent storage, and deployment workflow.
View hosting guidance →Unmanaged KVM VPS
Ruby on Rails Hosting
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.
View hosting guidance →Unmanaged KVM VPS
Docker Hosting
Install Docker Engine and Compose on an unmanaged KVM VPS when you want control over images, networks, volumes, ports, and the Linux host beneath them.
View hosting guidance →Unmanaged KVM VPS
Node.js Hosting
Use an unmanaged KVM VPS when the application needs a persistent Node.js process, custom system packages, background workers, or direct control over the reverse proxy and runtime.
View hosting guidance →Unmanaged KVM VPS
Ghost Hosting
Use an unmanaged KVM VPS for Ghost when you are prepared to operate the supported Ubuntu, Node.js, MySQL, Nginx, systemd, and Ghost CLI workflow.
View hosting guidance →Unmanaged KVM VPS
Python Hosting
Use an unmanaged KVM VPS for Django, Flask, FastAPI, and workers when you want to choose the Python runtime, WSGI or ASGI server, proxy, database, and deployment workflow.
View hosting guidance →Unmanaged KVM VPS
Django Hosting
Use an unmanaged KVM VPS when you want control over WSGI or ASGI serving, static files, the database, workers, production settings, and the deployment sequence.
View hosting guidance →