Hosting

Your stack,one domain.

Point your domain at Ploy. Keep your existing Framer or Webflow site. Route what matters to Ploy sites — and let routing rules, redirects, and SSL handle themselves.

Trusted by high-horsepower founding teams at

  • Leadbay
  • Taiga
  • Volca
  • Once
  • Raspire
  • Indie Health
  • CodeCrafters
  • Datost
  • Leadbay
  • Taiga
  • Volca
  • Once
  • Raspire
  • Indie Health
  • CodeCrafters
  • Datost

From DNS record,
to live on your domain.

Four steps, all on Ploy's hosting infrastructure — no Cloudflare config to write, no Nginx to maintain, no separate SSL job to schedule.

  • 01

    Point your domain.

    Add the DNS records Ploy gives you — or one-click via Entri on supported registrars. Apex and www auto-detect, and you elect one as the canonical default.

  • 02

    SSL on automatic.

    Certificates issued, renewed, and applied to every subdomain and routing rule on the hostname. No certbot, no rotation, no rate limits to remember.

  • 03

    Route paths to origins.

    Send /blog to a Ploy site, /pricing to another, /docs to a Notion page. Path prefix, regex, or exact match — top-down, first match wins.

  • 04

    Redirect, rewrite, log.

    301/302/307/308 redirects, a fallback proxy for unmatched paths, and first-party analytics injection on every proxied response. One stream across origins.

One hostname, many origins

Keep your Framer site. Add Ploy where it matters.

Point your domain at Ploy and add a fallback proxy to your existing Framer or Webflow origin. Visitors still land on the site you've already built — until they hit a path you've routed to a Ploy site. No big-bang migration. No broken inbound links.

  • Fallback proxy keeps your existing site live at /
  • Route specific paths — /blog, /pricing, /changelog — to Ploy sites
  • Stitch multiple Ploy sites under one canonical hostname
  • Migrate one section at a time, on your schedule
acme.comDefault
5 rules · SSL active
  • /acme.com
    Frameracme.framer.website
  • /blog/*acme.com/blog/*
    Ploy siteacme · marketing
  • /pricingacme.com/pricing
    Ploy siteacme · marketing
  • /changelogacme.com/changelog
    Ploy siteacme · changelog
  • /docs/*acme.com/docs/*
    Notionacme-docs.notion.site
Fallbackacme.framer.website
Routing rules

Rules that read like English.

Match by path prefix or regex. Pick an action — dispatch to a Ploy site, proxy to any HTTPS origin, or redirect with the status code you want. Drag to reorder; first match wins. Changes apply at the edge in seconds, no rebuild, no DNS wait.

  • Dispatch · route a path to a Ploy site you own
  • Proxy · forward to any HTTPS origin, stream the response back
  • Redirect · 301, 302, 307, or 308 with one click
  • Top-down evaluation with a fallback proxy as the catch-all
Routing rulesFirst match wins
acme.com
  • /blog/*Prefix
    acme · marketingPloy site
    dispatch
  • /pricingExact
    acme · marketingPloy site
    dispatch
  • /docs/*Prefix
    acme-docs.notion.sitePreserve host header
    proxy
  • /old-pricingExact
    /pricing
    redirect308
  • ^/blog/2023/.*$Regex
    /archive
    redirect301
Fallback proxyacme.framer.website
Who uses this

One domain. Every team that needs it.

Multi-brand teams

Run every sub-brand under one canonical hostname.

Route /products, /labs, /events to separate Ploy sites

Each sub-brand has its own editor and deploy history

One certificate, one canonical domain, one analytics stream

Election protects SEO — siblings 308 to the canonical

Migrations

Move off Framer or Webflow one section at a time.

Keep your existing site live behind the fallback proxy

Move /blog first, then /pricing, then /features — at your pace

No big-bang launch, no broken inbound links, no downtime

Cut the proxy when the last page is migrated

Microsites & launches

Spin up campaign pages without touching the main site.

New Ploy site lives at /launch-2026 or /partners/acme

Marketing site at / stays untouched

Analytics rolls up to the same domain

Tear it down by removing one routing rule

Hosting FAQ

Custom domains, routing, and reverse proxy — answered.

Point your domain at Ploy, then add a fallback proxy rule pointing at your existing Framer or Webflow origin. Everything keeps serving from there by default. Add routing rules to send specific paths — /blog, /pricing, /changelog, /launch — to Ploy sites or other origins. The rest of your site stays exactly as it was; visitors never see a redirect, never bounce across hostnames.
Each custom domain has an ordered list of rules. A rule matches by path prefix (/blog) or regex pattern (^/docs/v[0-9]+/.*), then picks one of three actions: dispatch (route to a Ploy site), proxy (forward to any HTTPS origin and stream the response back), or redirect (301, 302, 307, or 308). Rules are evaluated top-down — first match wins. Unmatched paths fall through to the domain's fallback proxy if one is set, or to the workspace's default site.
Automatically. SSL certificates are provisioned the moment a domain verifies, renewed on schedule, and applied to every subdomain and routing rule on that hostname. No certbot, no Let's Encrypt rate limits to think about, no manual rotation. Both your Ploy-served paths and your proxied origins serve over HTTPS from the same certificate. Higher-tier plans also support bringing your own certificate — useful for teams with internal CAs, EV certificates, or pinned cert requirements.
Pick one. Ploy lets you elect a canonical default domain (apex or www, or any other variant you've attached), and all sibling domains issue a 308 permanent redirect to it. Search engines see one canonical hostname, analytics stays clean, and link equity consolidates. Switching the canonical later is a single click — the redirects flip with it.
Yes — workspaces with multiple sites can route different path prefixes to different sites on the same domain. A common pattern: marketing site at /, blog at /blog, docs at /docs, changelog at /changelog. Each is its own Ploy site with its own editor and deploy history; the routing layer composes them into one hostname. Useful for multi-brand teams, sub-brands, or acquired company sites that consolidate over time.
Add a redirect rule per path you need to redirect. Choose the status code that fits — 301 for permanent moves, 308 if the request method needs to be preserved, 302 or 307 for temporary. Patterns can be exact paths (/old-pricing → /pricing) or regex (^/blog/2023/.*$ → /archive). Useful when migrating from a previous CMS, retiring URLs, or consolidating multiple campaign domains under one canonical host.
Yes — rules update instantly and atomically across Ploy's edge. Removing a rule sends traffic to the next-matching rule or the fallback proxy. There's no rebuild step, no DNS wait, no cache invalidation lag. If a rule needs to be temporarily disabled rather than deleted, replace its action with a redirect to the destination you want — the rule stays in the list and can be swapped back later.