Sitewrap Deploy Preload · versions · Enterprise S3

Publish to the edge without risky cache surgery.

Sitewrap Deploy regenerates pages from your origin into SW Edge cache, warms routes from your sitemap, keeps version history for rollback, and on Enterprise can publish to your own S3 / CloudFront — while the CMS stays in charge.

Start deploying Read docs
Deploy Job running
Full site deploy 42%
/pricing SW Edge · writing cache
/contactcached
/enterprisedeploying
/docsqueued
Preload warm Archive on publish Enterprise S3
Pipeline

Origin → disk cache → SW Edge → optional CDN.

Visitors hit Sitewrap Edge. Deploy and preload fill the cache from your origin. S3 / CloudFront is an Enterprise second publish target — not a required migration.

01OriginCMS or static site
02Deploy / PreloadFetch & optimize
03Disk cacheSW Edge serves
04S3 / CFEnterprise handoff
In the dashboard Deploy · Preload · Pages

What operators actually run.

These map to shipping product surfaces — not a slide-deck wish list.

Deploy

Full-site or single-page publish

Regenerate cached HTML from your origin into Sitewrap Edge. Ship the whole site, force a full rebuild, or deploy one page (and its children) from the Pages tree.

  • Deploy full site from the Deploy tab
  • Force redeploy when every page must rebuild
  • Per-page deploy + optional children (Pages · Growth+)
Preload

Sitemap warmup that stays on

Crawl your sitemap so critical routes are warm before visitors hit them. Watch progress live, pause or resume, and reload the sitemap when structure changes.

  • Live warmup status and path table
  • Cached / skipped / failed counts
  • Configurable sitemap URL and poll interval
Versions

Archive, preview, restore

Each page deploy archives the previous cached copy. Preview an older version and restore it to live disk cache without touching the CMS.

  • Version history per path
  • Preview archived HTML
  • Restore rollback without a new archive entry
Targets

Local edge — or Enterprise S3 / CloudFront

Default target is Sitewrap disk cache served by SW Edge. On Enterprise, publish optimized HTML and assets to your Amazon S3 bucket with CloudFront invalidation.

  • Local disk cache + proxy (all plans)
  • BYO S3 bucket, prefix, region, credentials (Enterprise)
  • CloudFront distribution ID + invalidation (Enterprise)
Controls

Publishing knobs that stay connected to cache.

Deploy jobs Track site, page, and (on Enterprise) S3 copy jobs with status and actor email.
Force redeploy Rebuild every page even when Sitewrap thinks nothing changed.
Page tree Browse cached paths, deploy one route, or clear disk cache for a page.
Only serve deployed Optional route mode: undeployed URLs hit your configured error page.
Staging first Warm and validate on a staging host before production DNS cutover.
Asset publish On Enterprise S3 mode, copy referenced static assets with HTML.
How it works

A release path teams can repeat.

01

Origin stays source of truth

WordPress, Shopify, Webflow, static, or custom — Sitewrap fetches from your origin when you deploy or preload.

02

Optimize into disk cache

HTML lands in Sitewrap’s disk cache for SW Edge to serve. Page deploys archive the previous version automatically.

03

Warm what matters

Preload crawls the sitemap so first visitors after publish get cache hits, not origin cold starts.

04

Optional CDN handoff

On Enterprise, set Amazon S3 as the deploy target to upload optimized files and invalidate CloudFront when a distribution ID is set.

Deploy targets

Local Sitewrap Edge, or bring your own CDN.

Default

Local disk cache

Optimized HTML and assets live on the Sitewrap proxy. SW Edge serves visitors with cache labels you can see in the request log.

  • No AWS account required
  • Works with any CMS or static origin
  • Pair with preload for warm first hits
Enterprise

Amazon S3 + CloudFront

On Enterprise, point Deployment settings at your bucket. Test the connection, copy the cache, or run the CloudFormation wizard — then invalidate CloudFront on publish.

  • Bucket, region, prefix, credentials
  • Distribution ID + invalidation
  • Enterprise plan only
Need staging before go-live?

Verify ownership, warm the staging host with deploy and preload, then cut production DNS when the edge looks right.

Deploy guide Enterprise & custom CDN Create account
FAQ

Deploy questions, answered.

What does “deploy” mean in Sitewrap?

Deploy regenerates cached HTML from your origin into Sitewrap’s disk cache (and, on Enterprise, uploads to S3 if that target is configured). It does not replace your CMS — the origin remains the content source of truth.

What is the difference between Deploy and Preload?

Deploy rebuilds pages from origin on demand (full site or a specific path). Preload continuously or on demand crawls your sitemap to warm paths into cache so traffic finds them already ready.

Can I roll back a bad publish?

Yes on plans with the Pages tab (Growth and above). Each page deploy archives the previous cached version. Open version history, preview, and Restore to switch live cache back to that archive. See Pricing for plan matrix details.

Is custom S3 / CloudFront only for Enterprise?

Yes. Local disk-cache deploy is available on Launch and above. Custom Amazon S3 and CloudFront (bucket credentials, distribution ID, invalidation, CloudFormation wizard) is an Enterprise capability.

Can we test before changing production DNS?

Yes. Verify ownership, use the staging preview host, warm cache with preload/deploy, then point the A record and activate TLS when ready.

Do deploys use plan credits?

Yes. Deploy and preload activity counts toward your monthly credit allowance. See Pricing for plan limits and overage.

Ready to publish through Sitewrap?

Wrap your site, deploy into SW Edge, warm the sitemap, and keep rollback on the paths that matter.

Start deploying See pricing All features