Three numbers, priced separately
Memory, vCPU and storage each have a price, and you set each one. The four presets are just starting points. Nobody's sold a tier of storage to get one more vCPU.
Features
Everything it does, in the order you meet it
Not a grid of icons. This is the whole product, grouped by when you'd actually reach for each part: from sizing a Pressy to the day you decide to leave.
01
Choosing one
A Pressy is one WordPress site with its own resources and its own bill. You pick the size, or you pick the kind of site and we pick the size.
Stacks, if you'd rather not decide
Twelve of them, one per kind of site: landing page, blog, restaurant, bookings, shop, membership, magazine, course and more. Each picks the size that suits the workload and installs a theme and up to five plugins while your Pressy is built, so the first screen you see is a site rather than an empty install.
Fully cacheable, so one vCPU is plenty. Jetpack pushes stats, related posts and image serving to WordPress.com, which lowers the load here rather than adding to it — trim the modules you don't use.- One site per container
- Not a folder inside a shared account. Its own container, its own memory ceiling, its own CPU allocation, its own database. Another site's busy day cannot spend the resources you bought.
- Nothing's charged until it works
- Upgrading never quietly hits your card. You see the amount, pay on a secure page, and nothing changes until the payment goes through, bank verification and all.
- Every Pressy is its own subscription
- Three sites means three subscriptions you can start, resize and cancel independently. Everywhere else in hosting, one site needing more means upgrading the plan that holds all of them.
02
The first minute
Most hosts just tell you a site appears. Here's what actually happens between paying and a live WordPress site: the same five steps you watch as they run.
Usually under five minutes, start to finish
- 1
Creating your account
Your account and subscription, set up cleanly.
- 2
Preparing your server space
Your own container, on your address, with the memory and CPU you paid for, and nobody else in it.
- 3
Installing WordPress
The latest version, installed clean, with your Stack's theme and plugins, if you chose one.
- 4
Applying your plan settings
Your resource limits, PHP and caching, set from the numbers you picked.
- 5
Securing your site with HTTPS
HTTPS, issued and verified before we call it ready, so it's secure the moment it's live.
Then an email. You don't have to sit and watch a progress bar. Close the tab whenever.
03
It runs itself
The things you shouldn't have to write a ticket about, or remember, or configure. This is most of what a host is for and most of what a host makes you do.
Backups you can't accidentally wreck
Automatic backups on a schedule, kept 30 days, plus manual ones whenever you want. Restores are free and unlimited and never touch your domain or DNS, so restoring is not a thing to be afraid of at 2am.
Core updates, with a way back
WordPress minor and security releases install themselves from the day your Pressy is built. A core update you start from the dashboard takes a new or recent backup first, checks the site still answers, and attempts a restore from that backup if it does not.
- HTTPS, issued and renewed
- Let's Encrypt on your Pressy address and on every custom domain you connect, with nothing to click and nothing to remember. Renewal is ours, not yours.
- Caching, with the WordPress side handled
- OPcache is on by default. Redis object caching is one switch. And if WordPress needs the plugin for it, we offer to set that up too, rather than leaving you a config file and good luck.
- Everything in your timezone
- Backups, cron runs, renewals and logs all show in the timezone you chose. Cron shows both clocks side by side, so a 3am job is never ambiguous.
04
When you want the controls
The dashboard is built for one site, so everything here is one screen rather than a category of a category. All of it is optional: you can run a Pressy for a year and open none of it.
PHP you can actually manage
Change version in one click, each showing whether it still gets security updates. The four limits people are always told to raise are one click each, and there's a live error log that groups the repeats.
SSH and FTPS, with keys done right
Add a public key and sign in without a password; we never see your private key. FTPS is explicit TLS on port 21, and the screen names the exact client setting to choose, because the near-universal wrong guess is SFTP, and it just fails to connect.
- Cron, without the traps
- Build a schedule from plain controls or write the expression yourself, and see the next runs in your own timezone before you save. It catches the classic mistakes before they cost you a job.
- Databases, and who can reach them
- Databases and their users in one place, not two tables you cross-reference in your head. The one WordPress lives in can't be deleted by accident, and new passwords are shown once, so save them when you see them.
- phpMyAdmin, signed in, one click
- One click opens phpMyAdmin, already signed in as you. Browse tables, run a query, import or export a dump. The tool built for it.
- Node.js apps alongside WordPress
- Run a small API, a webhook receiver or a background worker in the same container, on a path of your own domain, with WebSocket support if you need it. Its log is right there, so you can always see what it's doing.
- WordPress, managed from here
- Core version and update policy, plugins and themes with full control over auto-updates, a maintenance mode, and an activity feed of what actually happened rather than a spinner that ended.
- Custom domains, with the DNS spelled out
- Connect a domain, see exactly which records to add, and watch propagation from the dashboard. Supported registrars can be set up automatically instead of you typing records by hand.
05
When it grows
The part the rest of the industry solves by selling you the next plan up. A Pressy changes shape without moving, and you can rehearse anything first.
Change size on any day
Not at renewal, not by contacting sales. Upgrades take effect immediately and are pro-rated to the day; downgrades land at the end of the period so you never pay twice for the same window. Both quote the exact figure before you confirm.
Staging that is easy to manage
A full second copy at its own address, free and not counted against your plan. Sync down and push live are whole-site operations, and pushing to live backs up your live site first, cancelling the push if that backup fails.
- Put the whole dashboard in staging
- One control turns every screen into the staging copy's version of itself: PHP, databases, cron, files. Billing, domains and settings stay read-only there, because they belong to the real Pressy.
- Usage figures that are actually yours
- vCPU, memory, storage, bandwidth and more, measured for your site against your plan's own limits, not a shared-account average that tells you nothing.
06
When something goes wrong
Support is for when something's broken, not for getting ordinary things done. So this is mostly what you can put right yourself, and how you always know where you stand.
Restore, as often as you like
Free and unlimited, and a restore never touches your domain or DNS. You can also download a .tar.gz of the whole site, files and database, whenever you want, without asking anyone.
A security screen that doesn't flatter itself
What's protecting your Pressy, stated as plain facts: firewall, HTTPS, backups, container isolation. No attack counter, no security score. A made-up number is worse than none.
- Two-factor, and a second ask on the dangerous things
- Two-factor with recovery codes. The dangerous actions ask again even when you're signed in. A laptop left open shouldn't be enough to end a site.
- A status page, so you know when it's us
- If something's wrong on our side, the status page says so. So when your site misbehaves, you're not left guessing whether it's you or us.
07
When you decide to leave
The section most hosting companies don't write. Leaving is a thing customers do, and making it awkward has never once persuaded anybody to stay.
Nothing is destroyed for 37 days after that
Once a cancelled Pressy goes offline it can be brought back in full for 37 days, files, database and backups, with the Reactivate button on its own page. Reactivating starts a new subscription at the then-current price. After those 37 days it is deleted, backups included.
Take everything with you
A .tar.gz of files and database, downloadable at any time, in the format every other WordPress host accepts. We would rather you could leave easily than have you stay because you couldn't.
- Cancelling stops the renewal, not the site
- No notice period, no phone call, no retention offer between you and the button. You are not charged again, and the site keeps serving until the end of the period you have paid for. Then it goes offline.
Where a competitor beats us
Two kinds of thing on this list: choices we've made and would make again, and work that genuinely isn't done. We've marked which is which, because you'll find out either way and it may as well be from us.
Email hosting
A decisionA decision. Get it from someone who does it well and won't throttle you to protect their own IP reputation.
Moving a Pressy between accounts
A decisionNot yet. A Pressy belongs to one account today, so handing a finished site to a client means handing over the account. A real transfer is on the list.
Multi-site plans
A decisionA decision, and the product itself. One Pressy is one site. That is the thing we're arguing for, not a limitation we're apologising for.
A global CDN
Not yetNot yet. Cloudflare in front of a Pressy works today and costs nothing, and we'd rather say that than sell you ours.
More than one region
Not yetNot yet. One region today. More is on the roadmap, but we won't put a date on it we can't keep.
Phone support
Not yetNot planned. Email tickets and docs, answered by the person who built the thing you're asking about.
If you'd rather not start from nothing
Twelve Stacks, one per kind of site
A Stack picks the size that suits the workload and installs a theme and up to five plugins while your Pressy is built. It adds no capability. It removes the blank page. Everything is yours to change the moment it's live.
One page that loads instantly and collects an email address. SeedProd puts a real page up in minutes, and Elementor is there if it grows into a full site.Fully cacheable, so one vCPU is plenty. Jetpack pushes stats, related posts and image serving to WordPress.com, which lowers the load here rather than adding to it — trim the modules you don't use.
A few pages, a contact form and a phone number that has to work on a phone. Site Kit wires up Analytics and Search Console in one step.
Mostly static pages with a trickle of booking traffic. No mega-install menu plugin exists, so the menu is an Elementor page; the food photography is what justifies the storage.
Booking flows can't be cached — every step is a real request — which is what the second core is for.
Serving is cached, so one vCPU is plenty, but high-resolution libraries eat disk fast. Let LiteSpeed handle image optimisation rather than stacking a second pipeline on top of it.
A first catalogue with real checkouts. Carts and checkouts are uncacheable by definition, so the second core does the work the cache can't.That's the whole product
No feature held back for a bigger plan, and no line above that needs a sales call to unlock. Size one and see.