Presumably no information is conveyed by the first 4 significant digits. And can anybody compare this pricing to e.g. AWS or Google Cloud? I have never known my compute cost to second resolution, so I'd need to do calculations to even ballpark this.
Suggestion: Don't obfuscate the price, just remove it. Clearly you don't really want casual browsers to know how much you're charging[1]. Which: fine, this is the current trend in tech. So just remove the pricing and put your calendar link there as a CTA instead. Be classy. Don't play games with your audience.
1 - anybody who plugs this into a calculator will a) understand why you don't show monthly pricing and b) think this is screamingly expensive. Which reinforces my recommendation to just replace the price with a CTA and your calendar link.
For a VM running for a month? No.
For highly scalable batch tasks? Yes.
For small experiments? Yes.
For Full e2e tests creating a full env and killing it a minute later? yes.
Yeah, thanks, can you now also give us the downsides?
We don’t need a new Wordpress that subscribes to today’s current tech trends.
“It doesn’t scale well” what does that even mean?
That was 14 years ago. So imagine thinking that wordpress is “behind” in 2026 just because it doesn’t subscribe to the deranged cloud subscription culture that has infected the industry.
Wordpress has heaps of technical and non technical issues to solve (especially in governance), but being server-side ain’t one of them.
Because there's an immense difference when it comes to hosting between a blog/brochure site that is fully cachable and a woocommerce or, worse, social network/LMS/other highly dynamic site.
To be clear though, I'm not advocating for distributed cloud architecture - that sort of stuff is best done on a vertically-scaled server, which can get up to many hundreds of CPUs these days.
<p className="text-[17px] leading-[1.75] tracking-[-0.1px]">
The difference is subtle but significant. Apache is a web server — it can host and
run any web application, for example one written in PHP. Whereas WordPress sits a layer
above; in fact it typically runs on Apache. What makes it a better analogy for the
"agentic workload" is what you do with it — or rather, who and how uses it.
</p>