Ploy hosting, speed and uptime: what Ploy says, what it does not, and how to test it yourself
Short answer: Ploy is an AI website platform where the site you build is also hosted by Ploy. Its docs say sites are published to a globally distributed hosting network with edge caching, SSL (the padlock certificate) and a CDN (a network that serves files from a server near the visitor). As of November 2026, Ploy publishes no speed score and no uptime guarantee, so you should run your own speed test and watch its public status page before you trust it with a client or a launch.
You want to know whether a site hosted by Ploy will load fast and stay up, and what you can check yourself before you commit.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The short version: Ploy hosts the sites you build on it, the docs describe a standard modern setup (edge caching, automatic SSL, quick deploys), and the only hard uptime numbers are the ones on Ploy's own status page. There is no published speed score, no uptime promise in writing, and no list of data centre regions. That does not make it slow or unreliable. It means you test it, the same way you would test any host. This page shows how.
Everything below about Ploy comes from its own docs and status page as of 21 November 2026, and the test plan is one you can run today on a free Ploy site. Ploy is the product this page is about, and the practical advice works for any host.
This page may contain affiliate links from which Blur Studio earns commissions.
What Ploy says its hosting provides
Ploy's docs and feature pages describe the following. These are Ploy's statements, not independent measurements. Check the linked pages for the current wording.
| Area | What Ploy says | Where |
|---|---|---|
| Hosting and delivery | "Ploy handles publishing, hosting, SSL, and CDN delivery." Sites go to a globally distributed hosting infrastructure with edge caching. | docs.ploy.ai/publishing and /security |
| Deploy time | A few seconds for most sites. Each publish is a full snapshot you can restore later. | docs.ploy.ai/publishing |
| SSL | Certificates are issued and renewed automatically for every custom domain. | docs.ploy.ai/security |
| Free address | Every site gets a free address ending in ploy.build. Free-plan pages there (Production and Preview) show a small "Made by Ploy" badge. Paid plans hide it, and it never shows on a custom domain. | docs.ploy.ai/publishing |
| Routing | Ploy can sit in front of your domain and send some paths to Ploy and others to your old site, with redirects, applied "at the edge in seconds". | ploy.ai/features/hosting |
| Rollback | Open Versions, restore an earlier version, then publish it. Restoring alone does not change the live site. | docs.ploy.ai/publishing |
| Build safety | Builds run in isolated environments. Data is encrypted in transit (TLS 1.2 or newer, the standard that protects data moving over the web) and at rest (AES-256, a strong standard for stored data). | docs.ploy.ai/security |
One detail worth knowing: Ploy's docs are not fully consistent about who issues the SSL certificate. The security and custom domain docs mention the ACME standard (an automatic certificate system) and Google Trust Services, while the launch checklist says certificates come "via Cloudflare". Cloudflare is a large company that runs a worldwide network for hosting and security, and Ploy's trust centre lists it as a hosting and monitoring provider. For your purposes the safe summary is the one all pages agree on: Ploy issues and renews the certificate for you.
What Ploy does not publish
This is the part most reviews skip. As of November 2026, none of these appear on Ploy's pages, so do not assume them:
- An uptime guarantee. An SLA (service level agreement) is a written promise of uptime, often with a refund if it is missed. No Ploy page offers one, including the enterprise page. If a client contract needs one, ask Ploy sales in writing.
- Core Web Vitals or speed scores. Core Web Vitals are Google's three measures of page experience: how fast the main content appears, how fast the page reacts to a tap, and how much the layout jumps. Ploy publishes no numbers for them.
- Page weight, time to first byte, regions, DDoS protection or bandwidth limits. DDoS means a flood of fake traffic meant to knock a site offline. Ploy's pages do not describe its protection or any traffic caps.
- Support response times. Support goes through the help menu, the email address in the docs and a community chat group on Slack (a team messaging app). No response-time promise is stated.
What the status page showed
Ploy runs a public status page at status.ploy.ai, powered by a monitoring service called UptimeRobot. On 21 November 2026 it showed "All systems operational" and these figures for the previous 90 days:
| Monitor | 90-day uptime shown |
|---|---|
| Ploy Hosting Platform | 100.000 percent |
| Ploy.ai App (the editor and dashboard) | 99.997 percent |
| Ploy AI Responses | 99.989 percent |
The same page showed 99.995 percent overall for 90 days. Read these numbers carefully. They are Ploy's own monitors, measured over a short window, and they are a snapshot, not a promise. A host can show 100 percent on its own monitor while a visitor in one country sees errors. Treat the status page as a good sign and a place to check during an outage, not as proof.
The three monitors measure different things: the hosting monitor covers published sites, the app monitor covers the editor.
How to test the speed of a Ploy site (30 minutes)
You do not need a paid plan to test. A Free-plan site on a ploy.build address is enough to see the base speed. Test a site that looks like the real thing: your real images, fonts, chat widget and tracking tags, because those, not the host, cause most slow pages.
- Publish a realistic page. Build the home page and one inner page, publish to Production, and open the live address. Ploy's own going-live checklist suggests asking its Agent (the AI assistant inside Ploy's editor) to run a Lighthouse audit. Lighthouse is a free Google tool that scores a page's speed, accessibility and SEO from a test run. You can also use Google's PageSpeed Insights page or the Lighthouse tab in Chrome.
- Run it 3 times on mobile and 3 on desktop. One run can be off. Write down the median.
- Record the three Core Web Vitals. Google's page on them (web.dev, updated October 2024) gives the "good" targets, measured at the 75th percentile of real visits: main content in 2.5 seconds or less, reaction to a tap in 200 milliseconds or less, and layout shift of 0.1 or less.
- Know lab versus field. A Lighthouse run is "lab" data: one test on a simulated phone. "Field" data is what real visitors experienced over the last 28 days. A new site usually has no field data yet. Judge a launch on lab data, then check the Core Web Vitals report in Google Search Console (Google's free tool that shows how your site does in search) after a few weeks of real traffic.
- Test from where your customers are. If your visitors are in Dubai, London or Sydney, use a tool that lets you pick a test location, or ask a contact there to open the page on their phone and time it.
- Compare against your current site. Run the same test on the old site. The question is not "is Ploy fast" but "is it at least as fast as what I have, with the same content".
Pass and fail rules. Pass if mobile main-content time is 2.5 seconds or less in the median run and layout shift is 0.1 or less. Marginal if it is between 2.5 and 4 seconds (Google's guidance treats above 4 seconds as poor, check web.dev for the current wording). Fail if it is slower than your current site on the same page, or above 4 seconds. If it fails, open the report's list of fixes before blaming the host: oversized images, an autoplay video, and a heavy chat widget are the usual causes.
How to test uptime yourself
Do not depend only on the host's own monitor. Set up an outside one.
- Create a free account with any uptime monitor (UptimeRobot, the one Ploy itself uses, has a free tier. Check its page for the current limits).
- Add your site's home page and one inner page, checking every 5 minutes, with an email or text alert.
- Let it run for at least 14 days before you go live, and keep it running afterward.
- Write down any outage, how long it lasted, and whether Ploy's status page admitted it.
Here is the arithmetic that makes a number real. In a 30-day month there are 43,200 minutes. An uptime of 99.9 percent allows about 43 minutes of downtime. 99.99 percent allows about 4 minutes. The status page's 99.995 percent over 90 days would be roughly 6 minutes of downtime in 90 days. Decide what your business can live with: 40 minutes at 3 a.m. costs little, 40 minutes on a Saturday morning for a booking site costs real money.
Pass if two weeks show no outage longer than 5 minutes. Fail if there are repeat outages, or if your monitor shows errors that Ploy's status page does not.
Domain, DNS and SSL checks
Many "my host is down" problems are really domain problems. DNS (the system that turns a web address into a server location) takes time to update. Ploy's custom domain docs list these checks:
- Publish first, then add the domain. Free plans do not include custom domains. Starter includes one domain family and Pro five, per Ploy's pricing page.
- DNS changes can take up to 24 hours to spread. SSL is issued minutes after the records verify. A short delay is normal.
- If you use Cloudflare for your DNS, set the records to "DNS only" (the grey cloud). Ploy's docs say Cloudflare's "Flexible" SSL mode causes redirect loops. Use "Full (strict)" or "DNS only".
- Add the SSL challenge record first if you are moving a live domain, which Ploy's docs say gives near-zero downtime.
- If you have CAA records (records that say which companies may issue certificates for your domain), they must allow the issuer Ploy names in its docs.
- The apex domain (example.com) and the www version are both detected. Pick one as the main address. The other redirects to it.
After it goes live, open the site in a private window, click the padlock, and confirm the certificate is valid. Then type the address with and without www, and with http, and confirm each lands on the one main address.
Staging, noindex and rollback
Ploy can publish to Production (your live site) and to a separate Preview address that starts with "staging-". Its docs advise putting a noindex instruction (a tag that tells search engines to skip a page) on test pages you publish to Preview, and using a path such as /test/page-name. Test this: open the Preview address and view the page source, then confirm the noindex tag is there. Also keep unfinished work private: Ploy publishes the whole site at once, so a teammate's publish can push your half-done edit live. Its docs suggest private pages for work in progress.
For rollback, practise once before you need it. Make a harmless change, publish, then restore the earlier version in Versions and publish again. Time it. Ploy's docs say deploys take a few seconds. If your rollback takes 10 minutes because nobody knows the steps, that is your real recovery time.
Build a backup plan
Hosting on any platform needs an exit. Plan it on day one, not during an outage.
- Keep the domain yourself. Register it in your own account, or your client's, not the platform's. Ploy can sell a domain during setup, so check whose name goes on the registration. See how to avoid website vendor lock-in.
- Copy the source. Ploy's docs describe a command line way to copy a site's source files, on every plan, including Free. GitHub (a website where developers store code) Code Sync is free when set up through the command line, and connecting it from Workspace Settings in the app needs a paid plan.
- Back up database content separately. Ploy's built-in database exports to CSV (a plain spreadsheet file) up to 10,000 rows per view, and its own docs say CSV is for moving data, not a backup. Keep a regular export anyway.
- Know the exit terms. Ploy's terms say customer data stays available for export for 30 days after termination. Its privacy page says it keeps data for 60 days for export. The two pages differ, so plan around the shorter one.
- Keep a fallback. Ploy can route some paths to an old site, which also works in reverse as a gradual-move plan. For a bigger move, read the migration guide.
Worked example with made-up numbers
A dental practice with a 12-page site wants to move to Ploy. The numbers below are made up to show the method.
| Check | Current site | Ploy test site | Result |
|---|---|---|---|
| Mobile main content (median of 3) | 3.4 s | 2.2 s | Pass |
| Layout shift | 0.18 | 0.04 | Pass |
| Tap reaction | 240 ms | 150 ms | Pass |
| Outages in 14 days (outside monitor) | 1 of 9 minutes | 0 | Pass |
| Rollback drill | not possible | 3 minutes | Pass |
If the Ploy page had come in at 4.3 seconds, the owner would open the Lighthouse list of fixes, find a 2 MB hero photo, compress it, and test again before deciding. That order matters: fix the content, then judge the host.
Who should skip, and when another host is better
- You need a written uptime promise. Pick a host that publishes an SLA, or ask Ploy sales whether one is available on its enterprise plan. Do not assume.
- You must choose the hosting region. Ploy does not publish regions. For data-location rules, ask first.
- You want to self-host or own the server. Ploy's own comparison page with WordPress (a widely used website system you can host yourself) concedes WordPress is the pick for self-hosting. See Ploy vs WordPress.
- You run a full online store. Ploy's docs show an integration with Shopify (an online store platform) and its own comparison page says Ploy has no storefront or checkout. Check the forms, booking and payments guide.
- You just want the cheapest hosting. See hosting options for small business.
Ploy fits when you want the site builder, the AI editing and the hosting in one place and are fine with Ploy's published limits. For general hosting and security questions, the hosting, speed and security guide covers the basics for any platform.
Before you pay: a copy-ready checklist
- Publish a test site on the Free plan with real content.
- Run Lighthouse 3 times on mobile, record the median, and compare to your current site.
- Start an outside uptime monitor and run it 14 days.
- Read status.ploy.ai and note any incidents in the last 90 days.
- Connect a test subdomain, then confirm the certificate and redirects.
- Run a rollback drill and a source copy.
- Ask Ploy support in writing: is there an SLA, what regions, and what are the export steps on my plan.
- Check current pricing and plan limits on Ploy's pricing page.
How I'd approach this
I would treat Ploy hosting as unproven for my site until my own test says otherwise, and I would not pay for a year before a two-week trial. The docs describe a normal setup, the status page looks healthy, and the missing pieces (no SLA, no speed numbers, no regions) are things you can test or ask about.
Your first week. Day 1: start on the Free plan and publish two realistic pages. Day 2: run Lighthouse and record the results next to your current site. Day 3: start the outside uptime monitor. Day 4: run the rollback drill and copy the source. Day 5: email Ploy support the three written questions above. Days 6 and 7: read the monitor and decide.
Decision rule. Move forward if speed passes, two weeks of uptime are clean, and you have a working exit. Stay where you are if any one fails and you cannot fix it with content changes. If you would rather have someone else build, test and look after it, Blur Studio builds the custom version: AI agents that use your business knowledge, connections to your CRM (customer list) and calendar, and ongoing care, see what that includes. If you are weighing Ploy overall, start with the Ploy review, and the final call is yours. When you are ready, you can try the Free plan.
Questions people ask
Where does Ploy host my site?
Ploy's docs say sites are published to a globally distributed hosting infrastructure with edge caching, and its trust centre lists Google Cloud as the cloud provider and Cloudflare for hosting and monitoring. It does not publish a list of regions, so ask support if location matters to you.
Does Ploy guarantee uptime?
No uptime guarantee is published on Ploy's pages as of November 2026. Ploy's status page showed 99.995 percent overall for the previous 90 days on 21 November 2026, but that is measured history from Ploy's own monitors, not a promise. Ask sales in writing if you need an SLA.
Is a Ploy site fast?
Ploy publishes no Core Web Vitals or speed scores, so there is no number to quote. Run Google's Lighthouse or PageSpeed Insights on your own published pages, 3 times on mobile, and compare to your current site. Heavy images, video and chat widgets usually matter more than the host.
Is SSL included, and is it free?
Ploy's docs say certificates are provisioned and renewed automatically for every custom domain, with no setup. Custom domains themselves need a paid plan, per Ploy's pricing page, so check the current plan limits.
Why does my Ploy domain show a redirect loop or certificate error?
The most common cause in Ploy's docs is Cloudflare. If your DNS runs through Cloudflare, set Ploy's records to DNS only (grey cloud) or use Full (strict) SSL. Flexible SSL causes redirect loops. Also remember DNS can take up to 24 hours to spread.
How do I roll back a bad publish?
Open Versions in the editor, restore the earlier version, check the preview, then publish. Restoring does not change the live site until you publish. Practise once before you need it.
How do I keep a staging page out of Google?
Ploy's docs say to use a test path such as /test/page-name, add a noindex tag, and publish to Preview only. Then view the page source on the staging address to confirm the tag is there. See also why a Ploy site may not show on Google.
Can I leave Ploy and take my site with me?
Ploy's docs describe a way to copy your site's source, and its database exports to CSV, but its pages disagree on which plans get which export route, and its terms and privacy page give different export windows (30 and 60 days). Check Ploy's current docs and terms before you rely on any of it, and read how to avoid vendor lock-in.
More in this topic: Ploy.ai: login, startups, enterprise and integrations (8 guides) →