A WordPress checkout can hit PHP memory or concurrency limits while its monthly traffic allowance still has room.
That is the sizing problem I want answered before I compare Kinsta prices. Monthly traffic tells me how much activity a configuration allows over a billing period. It does not tell me how many requests it can process at the same time.
Concurrency is that second thing. Requests being processed simultaneously.
I want one number to settle the hosting decision. Nice, tidy, probably wrong.
For a checkout or membership workload, I would ask Kinsta to size the dynamic workload rather than infer capacity from a visits column. Paying for a higher tier alone is not evidence that the site will run faster.
Here is how I would work through the configuration and the bill.
First, stop treating “visits” as a universal unit
Kinsta counts one unique IP within 24 hours as one visit, then aggregates monthly visits across your portfolio.
That is not:
- Pageviews.
- Analytics sessions.
- Simultaneous users.
Server bandwidth and CDN transfer are separate measures, too.
The plan families introduce another distinction that is easy to skim past:
- Single and WP alternatives: traffic is expressed as server bandwidth or billed visits.
- Launch family: traffic is expressed as server bandwidth and estimated visits. Those estimated visits are not billed-visit allowances.
I would not compare “125k” in two rows until I knew what each number actually represented.
A bigger number is comforting. The accounting basis is more useful.
Match the configuration, not just the install count
These are selected configurations from the November 4, 2026 pricing snapshot, in USD before tax:
| Configuration | Installs | Monthly price | Traffic/month | Storage | CDN/month |
|---|---|---|---|---|---|
| Single 20GB / Single 35k | 1 | $35 | 20GB or 35k billed visits | 10GB | 125GB |
| WP 2 | 2 | $70 | 40GB or 70k billed visits | 20GB | 250GB |
| Build | 2 | $69 | 40GB and 200k estimated visits | 30GB | 250GB |
| WP 10 | 10 | $225 | 125GB or 315k billed visits | 40GB | 750GB |
| Scale | 10 | $169 | 125GB and 650k estimated visits | 50GB | 750GB |
The two-install comparison is where I would slow down.
Build is $69/month. WP 2 is $70/month. Both allow two installs.
They are still distinct configurations.
WP 2 is not recommended for ecommerce or membership sites. Build is part of the Launch family, and every Launch-family plan is recommended for those workloads.
That does not turn Build’s estimated visits into a concurrency guarantee. It means I have a suitable configuration to discuss with Kinsta, not a substitute for sizing.
A few more boundaries matter:
- Multisite is included in all WP options.
- Single pairs include multisite except the entry pair.
- Launch-family plans include multisite except Launch.
- Within the Launch family, cloning and easy transfer start at Build, not Launch Plus.
- Account managers start at Single 125GB / Single 315k, WP 10, and Scale.
My shortcut would be to count installs and pick the cheapest matching row. I would rather catch that shortcut here than build the budget around it.
Decide what “managed” actually removes from your workload
Kinsta says its team handles WordPress migrations. Standard staging and daily backups are included.
That gives me a useful workflow: move the site, test changes in a separate copy, and use available backup recovery points if a deployment breaks something.
It does not make plugins, application code, or checkout behavior somebody else’s responsibility.
Security monitoring, malware removal, and expert support reduce hosting administration. They do not amount to complete site management or custom development.
The control model matters, too. MyKinsta is a managed dashboard, not cPanel or unrestricted access to server settings. SFTP/SSH file access and direct database access are available.
That is the tradeoff I would evaluate: less hosting administration, without assuming unrestricted server control.
For a hobby site, a pre-revenue project, or a $10–20/month budget, I would be cautious about paying for that service model. It needs to remove work I actually have.
Price the recovery and testing requirements separately
Daily backups and standard staging are already included. I would not buy upgrades merely because the options exist.
The relevant recurring charges include:
| Optional item | Monthly price, before tax |
|---|---|
| Additional WordPress site | $30 per site |
| Extra disk | $20 per 20GB |
| Automatic plugin/theme updates | Starts at $3 per site |
| Six-hourly backups | $20 per site |
| Hourly backups | $100 per site |
| Premium staging | $20 per site |
| Redis | $100 per site |
Premium staging supports up to five environments for heavier testing. Automatic Updates includes plugin/theme updates, visual checks, and scheduling.
Neither is automatically included just because the hosting is managed.
The additional-site charge needs its own warning: an extra install does not itself establish more pooled traffic or compute capacity.
I cannot turn “another site fits” into “another workload has enough resources.” Different question.
The $35 plan can produce a $75 recurring subtotal
For the documented one-site example needing extra storage and heavier testing:
Single 20GB hosting $35/month
One additional 20GB disk increment $20/month
One premium-staging add-on $20/month
----------
Illustrative recurring subtotal $75/month
All three inputs are monthly prices. None is an annual equivalent.
This assumes those options are purchased together. It is not a guaranteed invoice, and it excludes:
- Tax.
- Email hosting.
- Usage overages.
- Other outside services.
- Any promotional treatment of add-ons.
Email hosting is not included, so I would keep it in the outside-services budget.
The estimate I actually need is:
Base hosting + chosen recurring options + actual usage charges + outside services + tax
Less tidy than the headline price. More useful.
Keep annual equivalents out of the payment schedule
The entry plan costs $35 monthly or $350 annually, before tax.
Its displayed annual equivalent is rounded to $30/month. That does not mean twelve $30 installments. The annual invoice is $350 upfront.
Annual billing advertises two months free compared with monthly billing.
There is also a separate first-month-free offer for eligible new customers on the entry Single pair, WP 2 alternatives, and Launch.
At entry, that means $0 today, followed after the free month by either:
- $35 monthly, or
- The full $350 annual invoice.
Not ongoing free hosting. Not proof that promotions stack. Not a promise that add-ons are free.
I would record the initial promotional payment separately from the ongoing commitment. Otherwise, the cheapest number on the page quietly becomes my budget.
Kinsta’s FAQ describes a 30-day money-back guarantee after any free period. I would check which charges qualify rather than assume everything is refundable. Upgrades and downgrades through MyKinsta are automatically prorated.
Ask about overages before choosing the billing cadence
The FAQ says sites remain online beyond visit, storage, or CDN limits. Notifications arrive at 80% and 100% usage, with fees based on actual excess usage.
Useful. Still not a complete budget.
A complete current overage schedule, including server bandwidth, is not listed on the pricing page. I would confirm the applicable rates with Kinsta before committing monthly or annually.
An alert threshold tells me when I will hear about usage. It does not tell me what that usage will cost.
My selection checklist
I would choose in this order:
- Count production installs. Identify multisite requirements.
- Match the traffic accounting. Check pooled traffic, storage, and CDN capacity.
- Get dynamic workloads sized. Ask about PHP memory and simultaneous-request requirements.
- Set recovery requirements. Separate backup retention from backup frequency.
- Set testing requirements. Compare included standard staging with paid premium staging.
- Compare targeted add-ons with a larger configuration.
- Confirm the payable commitment. Include promotions, migration scope, support channel and language, and usage rates.
For agencies, I would also compare storage, retention, transfer workflows, and program eligibility. Agency perks are eligibility-dependent, not universal discounts.
For custom capacity or contractual requirements, I would take the discussion to Enterprise. Business and Agency’s 99.9% guarantee and Enterprise’s up-to-99.99% SLA describe contractual commitments, not measured uptime.
That is my dividing line: choose Kinsta because its managed workflows fit the work, then size and price the actual configuration. Not because a higher-priced row looks safer.
For the complete plan matrix, retention differences, and add-on breakdown, I’ve kept the full Kinsta pricing guide here.
Top comments (0)