
The choice comes down to how much sits around your WordPress site. Kinsta is a great choice for a site or a portfolio that needs speed, backups, and support with little operational work. Upsun Cloud is the stronger choice when you need several runtimes in one project, per-branch previews with live data, a choice of cloud providers, or compliance across every environment.
The clearest way to distinguish the two: Kinsta is a managed WordPress host, and Upsun Cloud is an application platform that also runs WordPress. Kinsta is built to take the operations of WordPress off your plate. Upsun Cloud is built to run whole systems, of which a WordPress site may be one piece. Both run WordPress well.
Dimension | Kinsta | Upsun Cloud |
| What it is | Managed WordPress host | Multi-cloud application platform |
| Pricing model | Per install, per visit, plus storage and bandwidth | Resource-based (CPU, RAM, storage) |
| Root access | No, SSH and WP-CLI on WordPress plans | SSH, plus config-as-code |
| Runtimes beyond WordPress | PHP and WordPress | 10+ runtimes in one project |
| Managed data services | MariaDB, MySQL, PostgreSQL, Redis | Fully managed databases and services |
| Preview environments | One staging copy per site, refreshed manually | Per branch, clones live data |
| Cloud provider | Google Cloud | AWS, GCP, Azure, IBM Cloud, or OVHcloud |
| Compliance | SOC 2 Type II and ISO 27001 | ISO 27001, SOC 2 Type 2, PCI DSS Level 1, HIPAA, and TX-RAMP |
| Support | 24/7 support | 24/7 support |
A managed WordPress host runs and tunes WordPress for you. An application platform runs whatever your system is built from and treats WordPress as one service among several.
Kinsta puts every site in an isolated container on Google Cloud and handles updates, daily backups, caching, and a Cloudflare content delivery network. For a site or a portfolio, that removes almost all of the day-to-day operational work.
Upsun Cloud starts from the whole application. One .upsun/config.yaml file describes every service, so a WordPress front end, a separate API in Node.js or Python, and the databases they share deploy together from Git.
Kinsta offers Application Hosting and Database Hosting as separate products, so you can run a custom app and a managed database under a single account. The difference is how the pieces fit: on Kinsta, they are separate products you connect; while on Upsun Cloud, they are services in one project, sharing one config, one Git workflow, and one set of preview environments.
Kinsta prices by sites and visits; Upsun Cloud prices by the resources you provision.
Kinsta plans are set by WordPress installs, monthly visits, and storage, with overage fees past your limits. This is easy to budget for a fixed set of sites with steady traffic, and harder to forecast when traffic is spiky or a portfolio grows unevenly.
Upsun Cloud is resource-based: you pay for the CPU, RAM, and storage you provision, with commitment options for a predictable floor. It prices a busy custom service the same way it prices a WordPress site, since both are the same kind of thing on the platform.
Which is cheaper depends on your traffic and how many services you run, so treat any cost claim as workload-specific. Model your case with the pricing calculator.
Yes, on both. The difference is how the pieces connect: Kinsta runs other stacks as separate products; Upsun Cloud runs them as services in one project.
Kinsta's Application Hosting supports Node.js, Python, Go, Ruby, Java, PHP, and more, with Git deploys and Dockerfiles, and Database Hosting offers MySQL, PostgreSQL, Redis, and MariaDB. A site plus a custom app plus a database is possible under one account, but as separate products, you wire up each with its own setup.
On Upsun Cloud, a WordPress site, a custom service in another language, and their databases are defined in one .upsun/config.yaml and deployed as one unit. Managed services include PostgreSQL, MySQL, MariaDB, Redis, Elasticsearch, OpenSearch, RabbitMQ, and Kafka. For a headless build (a WordPress back end feeding a separate front-end framework), both halves run in one project rather than across two products.
Kinsta steers through a dashboard; Upsun Cloud keeps the project in a file in Git. Both are deliberate design choices.
Kinsta offers no root access, by design: they own the server configuration, so you do not have to. You get SSH and WP-CLI on WordPress plans and the MyKinsta dashboard for the rest. This suits teams who want WordPress handled, and pinches when you want the infrastructure itself in version control.
Upsun Cloud keeps the whole project in one .upsun/config.yaml, so services, routes, and build steps move through the same review as application code, driven from the CLI, Console, and API. That suits teams who treat infrastructure as code and want every change tracked.
Kinsta gives you a staging copy you refresh by hand; Upsun Cloud gives every branch an environment that clones live data on its own.
Kinsta includes one free staging environment per site, a copy of the live site you push to production with one click, with extra staging billed per environment. It works well for testing a plugin or theme change, but it is a manual copy tied to a site, not a fresh environment per branch.
Upsun Cloud creates a preview environment for every branch, each cloning production data, config, and code, so what you test matches what runs live. For a team opening several branches at once, this removes the staging-to-production drift that catches teams late.
Kinsta runs on Google Cloud only; Upsun Cloud lets you choose the provider, which matters for data residency and for avoiding a single-provider tie.
Every Kinsta product runs on Google Cloud, with many regions but no option for another provider or your own cloud account. This is a limitation when a client, regulator, or residency rule calls for a provider that Kinsta does not offer.
Upsun Cloud runs your application on AWS, GCP, Azure, IBM Cloud, or OVHcloud from one workflow, so you can place a workload where a contract or residency rule requires and work the same way across all of them.
How do Kinsta and Upsun Cloud compare on compliance?
Both hold recognized certifications. The differences that matter are HIPAA, the wider set, and whether compliance covers every environment or only production.
Kinsta holds SOC 2 Type II and ISO 27001. Per Kinsta's own documentation, they do not offer a HIPAA-compliant product and do not sign Business Associate Agreements, so workloads handling protected health information do not fit.
Upsun Cloud holds ISO 27001, SOC 2 Type 2, PCI DSS Level 1, HIPAA, and TX-RAMP, applied across every environment rather than production alone, which matters when preview and staging environments also touch sensitive data.
Choose Kinsta if WordPress is the whole job: a site or portfolio that needs speed, backups, a content delivery network, and expert WordPress support with little operational work of your own. Kinsta is very good at this, and a full application platform would be more than you need.
Choose Upsun Cloud if WordPress is one part of a larger system, or if you need per-branch previews with live data, several runtimes in one project, databases beyond the default, a choice of cloud provider, or compliance across all environments.
The shape of the move is: export the WordPress files and database from Kinsta, write an .upsun/config.yaml that describes the site, and import the data. A small site is a short job; the time depends on how much media and how many services you run.
One difference from a platform-to-platform migration is worth calling out. Because Kinsta is fully managed, there is no existing infrastructure config to translate; you write the Upsun Cloud configuration from the WordPress install itself. In practice, that means declaring the PHP app, a MariaDB or MySQL service, and storage mounts for wp-content/uploads and cache, then bringing over a database dump and the media files.
The WordPress migration walkthrough shows the target configuration and the data steps in full, including the config file, the database import, and moving media between hosts. It is written for a platform-to-platform move, so treat the config and data mechanics as the reusable part rather than the starting-project steps. For a modern WordPress structure, the Bedrock guide is a useful companion.
Is Upsun Cloud cheaper than Kinsta?
It depends on the workload. Kinsta prices by WordPress installs and monthly visits; Upsun Cloud prices by the CPU, RAM, and storage you provision. For a single low-traffic site, Kinsta's model is simple and can be lower-cost. For a growing application with several services or uneven traffic, resource-based pricing gives more control over spend.
Can I run WordPress on Upsun Cloud?
Yes. Upsun Cloud runs WordPress as a PHP application with a MariaDB or MySQL service, described in a single .upsun/config.yaml. The WordPress migration walkthrough shows a working configuration end-to-end.
Can I run WordPress plus a custom app in one place?
On Upsun Cloud, yes, in one project: a WordPress site, a custom service in another language, and their shared databases are defined together and deployed as one unit. On Kinsta, you can run a WordPress site and a custom app under one account, but through separate products (WordPress Hosting and Application Hosting) rather than one project.
Does Kinsta support multi-cloud or my own cloud?
No. All Kinsta products run on Google Cloud, with a choice of regions but no option for another provider or your own cloud account. Upsun Cloud deploys to AWS, GCP, Azure, IBM Cloud, or OVHcloud.
Do I lose managed convenience if I move to Upsun Cloud?
You trade a fully hands-off setup for config-as-code control. Kinsta owns the server configuration, so you do not touch it; Upsun Cloud puts the project configuration in your Git repository, which gives more control and asks a little more of your team.
Is Kinsta or Upsun Cloud better for a headless or decoupled WordPress build?
Upsun Cloud, in most cases. A headless build pairs a WordPress back end with a separate front-end framework, and Upsun Cloud runs both halves as services in one project with one workflow and shared preview environments. On Kinsta, the two halves would run as separate products.
Does Kinsta offer HIPAA-compliant hosting?
No. Per Kinsta's own documentation, they do not offer a HIPAA-compliant product and do not sign Business Associate Agreements. Upsun Cloud's compliance set includes HIPAA, applied across all environments.