Calculator hosting for sites that are all requests, no database.
A tool site serves enormous numbers of requests that ask the database almost nothing. Sizing it like a normal WordPress site gets both halves of that wrong.
Everything a calculator site asks of a host.
The page is identical for everyone, the arithmetic happens in the browser, and the load is request volume rather than database work.
Tool pages answered entirely at the edge
A calculator's markup does not change between visitors, so it is served from the nearest region without reaching the origin - which is why a tool site can take traffic far beyond what its plan's PHP capacity suggests.
The arithmetic runs in the browser
Calculation logic delivered as a cached script costs the server nothing per use, so a hundred thousand calculations a day and a hundred represent the same load on the origin.
AJAX kept off the critical path
Where a tool genuinely needs the server, those calls are routed and rate-limited on their own, so one expensive endpoint cannot starve the rest of the site of workers.
Core Web Vitals as the product
Tool sites live on search traffic with no brand loyalty behind it, so asset delivery, font loading and layout stability are tuned as a feature rather than as a cleanup task for later.
Hundreds of tools on one site
A large set of tool pages is a routing and caching question rather than a capacity one, and the platform treats it that way rather than selling you a bigger plan.
Watch requests, not page views.
The number that describes a tool site is requests per second at the edge, and how few of them ever reach PHP at all.
- Edge hit ratio per tool page
- Origin request rate against plan
- One-click admin login
- Restore any daily backup from the dashboard
A tool page under real search traffic.
Almost every request should be answered without the origin hearing about it. What remains is the small fraction that genuinely needs a server.
What we change for a calculator site
These are the settings that differ from a standard WordPress site on the same plan. Each follows from a workload that is request-heavy and database-light.
| Setting | What we do | Why |
|---|---|---|
| Page cache lifetime | Long, with tool pages marked fully static | A calculator's markup is identical for every visitor, so any origin request for it is a request that did not need to happen. |
| Capacity sizing | Measured in edge requests rather than PHP workers | Sizing a tool site by PHP concurrency buys capacity for the one percent of traffic that ever reaches the origin. |
| AJAX endpoints | Routed separately and rate-limited per endpoint | One server-side tool becoming popular should not consume the worker pool that the entire site shares. |
| Static asset delivery | Versioned, immutable, with far-future expiry | The calculation script is the same file for months, and revalidating it on every visit is latency spent on nothing. |
| Font and script loading | Preloaded and self-hosted rather than fetched from a third party | Tool sites are judged on first render by visitors with no reason to wait, and a third-party font request is the usual cause of the delay. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
How much traffic can a tool site take?
What if a calculator needs server-side logic?
Can I host hundreds of tools on one site?
Do you help with Core Web Vitals?
Will caching break a calculator?
Move your tool site to a host sized for requests.
Free migration, tool pages answered at the edge, and server-side endpoints that stay contained.