every wordpress site gets its own everything.
each site you create runs as its own container with its own runtime, database, cache, and filesystem. no shared pools, no neighbours, no plugin from one site reaching into another.
free trial on Growth, no credit card needed.
every site is a real boundary, not a folder.
when the dashboard says "site" it means a stand-alone slice of infrastructure. every layer below is scoped to your site and only your site.
- 1pick a template
start from blank WordPress or WooCommerce. both ship with the same caching, security, and runtime configuration. you can install whatever else you need on top.
- 2name and create the site
the dashboard binds a container, attaches a free preview URL on our subdomain, and brings the site online without you touching a server.
- 3manage it from one place
you land on a per-site dashboard with backups, domains, plugins, themes, files, logs, and settings. no FTP, no SSH, no support ticket for the basics.
every site is a real boundary, not a folder.
the same anatomy applies on every plan. the only difference between plans is how many sites you can create.
- 01Runtime
Dedicated container · Per site
your site runs in its own Docker container with its own PHP-FPM workers and OPcache. restarts and resource ceilings apply only to your site.
- 02Storage
Dedicated MariaDB · Per site
each site gets its own MariaDB process and its own credentials. a slow query on another customer's site cannot touch yours.
- 03Cache
Dedicated Redis · Per site
object cache, transients, and session data live in a Redis boundary scoped to your site. no cross-customer eviction, no key collisions.
- 04Files
Container filesystem · Per site
wp-content, uploads, plugins, themes, and logs live inside the container's volume. nothing leaks across sites.
- 05Network
Free SSL and preview URL · Per site
every site comes with its own preview URL and its own SSL boundary at the edge. no plan upgrade required to turn it on.
- 06Network
Custom domains · Per site
attach your own domain with a single CNAME. multiple domains per site are supported, and primary domain is a one-click choice.
from new site to live in one flow.
create a site, give it a name, and the platform binds an isolated container to your team. you land back in the dashboard with a working temp URL and a full per-site control surface.
- 1
pick a template
start from blank WordPress or WooCommerce. both ship with the same caching, security, and runtime configuration. you can install whatever else you need on top.
- 2
name and create the site
the dashboard binds a container, attaches a free preview URL on our subdomain, and brings the site online without you touching a server.
- 3
manage it from one place
you land on a per-site dashboard with backups, domains, plugins, themes, files, logs, and settings. no FTP, no SSH, no support ticket for the basics.
shared hosting names sites it cannot really separate.
most managed WordPress hosts call each customer surface a "site" but run them all from one shared PHP-FPM pool, one shared MySQL instance, and one shared object cache. when one customer's plugin loops, every other site on the box gets slower with it.
we built the dashboard the other way around. a site on Yovale is a real container with a real boundary — its own runtime, its own database, its own cache, and its own filesystem. nothing about your site is downstream of another customer's traffic, plugin choices, or runaway code.
shared wordpress hosting vs per-site containers.
Shared WordPress Hosting
Yovale Per-Site Containers
what every site has of its own.
the same control surface is available on every plan. the dashboard, the cache stack, the security defaults, and the lifecycle tools are identical from the smallest plan to the largest.
Per-site dashboard
every site has its own panel for overview, monitoring, domains, backups, plugins, themes, files, cron, logs, and settings. nothing important hides behind a support ticket.
Token-based WP-Admin
log into wp-admin from the dashboard with a single click. tokens are short-lived and scoped per user, so nobody is sharing a password to get in.
Clone to staging
spin up a sealed staging copy of any site with one click. push changes back when you are ready, with the option to keep both around side by side.
Backups built in
automated backups on every plan, stored off the origin server. download from the dashboard even when the source server is offline.
Plugin and theme controls
install, deactivate, update, and remove plugins and themes from the dashboard. a small platform blocklist warns you about plugins that conflict with managed hosting.
Login lock and 2FA
hide wp-admin behind an IP allow-list or a one-time URL, with rate limiting and 2FA available on every plan. no upgrade required to lock things down.
where the per-site model connects to the rest of the platform.
See plan prices, site caps per plan, and what is included on every tier.
How the per-site Docker boundary is built and why it matters in practice.
How a new site comes online from a pre-warmed container pool.
Per-site backups stored off the origin server, downloadable from the dashboard.
Attach your own domain to a site with a single CNAME, with free SSL out of the box.
One-click sealed staging copy of any site for safe plugin and theme work.
questions before you create your first site.
What does "site" actually mean on Yovale?
A site is a Docker container with its own PHP runtime, dedicated MariaDB, dedicated Redis, isolated filesystem, free SSL, and a preview URL. It is not a folder inside a shared box.
Can I install my own plugins and themes?
Yes. There is a small platform blocklist for plugins that conflict with managed hosting (caching plugins, security plugins that fight the platform), but the rest of the WordPress ecosystem is fair game.
Are sites really isolated, or is this shared hosting with separate dashboards?
Every site runs in its own container with its own PHP-FPM, Redis, MariaDB, and filesystem. There is no shared PHP worker pool and no shared object cache between sites.
What templates can I start from?
Two templates are available — Blank WordPress and WooCommerce. Both ship with the same caching, security, and runtime configuration. You can install plugins and themes on top of either.
How are backups stored per site?
Each site has its own backup history stored off the origin server. You can take, restore, download, and delete backups from the dashboard. Downloads work even when the source server is offline.
Can I clone a site to staging?
Yes. Every site has a one-click clone-to-staging action. The staging copy is sealed from the production site and can be pushed back when you are ready.
What happens to my site when I upgrade my plan?
Plan changes apply at the team level, so upgrading raises the site cap for the whole team without rebuilding any existing site. Existing sites keep running on the same container they were created on.
Do I need an SSH or FTP account to manage a site?
No. Plugins, themes, files, database operations, and logs are all available through the per-site dashboard. The actions you would normally need a shell for are exposed as real APIs.
stop sharing space. ship your own boundary.
create a real per-site container in the time it takes a shared host to email you a welcome message. backups, SSL, and the dashboard are part of every plan, not an upsell.