Stop abuse before origin
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your Drupal host.
- IP block & allow lists
- Rate limits + 404 bans
- Rules sync to Sitewrap Edge
Supported CMS Drupal
Drupal, faster and quieter at the edge.
Sitewrap sits in front of Drupal so anonymous pages hit edge cache, /user and admin stay gated, and scanners die before PHP workers wake up.
Drupal surfaces Edge policy
/ anonymous HTML · cached /node/* cached when public /user/login gated /admin/* gated /core/* probe-hardened Anonymous HIT · editors on origin · probes blocked
Built for Drupal Edge-first
Enterprise CMS habits, edge-native controls.
Drupal already does a lot. Sitewrap adds the visitor-facing edge: cache, firewall, form defense, and visibility without another full-stack migration.
Keep the back office private
Gate admin and login surfaces until Sitewrap unlocks them with a passwordless magic link or short code — so random scans never reach the unlock screen.
- Magic link + short code
- Unlock cookie on your domain
- Works with remapped paths
Serve pages from the edge
Cache HTML and assets at Sitewrap Edge. Preload from your sitemap so first visitors already hit warm pages.
- TTL + stale options
- Sitemap crawl & warm
- Editor paths stay origin-bound
Spam dies at the edge
Detect HTML forms on proxied pages, harden submissions, and land clean leads in Sitewrap with field mapping.
- Honeypot + time-on-page
- Per-IP form rate limits
- Lead groups & visitor context
Request log + Mixpanel / GA4
See every visit in the Sitewrap request log, then ship the same event catalog to Mixpanel and GA4 without stacking more origin plugins.
- Live users & engagement
- Consent-aware partners
- Server + client events
Publish without origin drama
Deploy selected pages, preload cache, and roll back from the dashboard — while your CMS stays the content source of truth.
- Page-level publish
- Cache preload
- Rollback-friendly releases
Setup Minutes, not months
From origin Drupal to production wrap.
Register the domain, exclude authenticated paths, warm the sitemap, then cut traffic.
Add your Drupal site
Enter the public domain and current origin. Sitewrap verifies ownership and checks reachability.
Tune edge defaults
Turn on firewall, admin gating, cache, and form protection. Exclude editor or checkout paths that must stay live to origin.
Warm important pages
Point preload at your Drupal sitemap so key URLs are cached before you switch traffic.
Point DNS and go live
Issue TLS, flip the A record, and operate from the dashboard — cache, firewall, forms, analytics, deploy.
Operate Drupal like a modern edge site.
Request logs, live users, Mixpanel/GA4, and deploys sit beside Drupal — not inside module sprawl.
Platform Multi-origin
Drupal teams rarely run only Drupal.
Wrap Drupal properties next to WordPress microsites and static docs under one Sitewrap account.
- Any CMS behind the same edge controls
- Static websites without a CMS at all
- Custom origins and hybrid stacks
WordPress Hide WordPress, WAF defaults, admin gate, Oxygen-safe cache, and Forms & Leads. Shopify Edge cache, bot defense, and analytics in front of your Shopify storefront origin. Joomla Edge firewall, admin gating, and cache in front of classic Joomla sites. Magento Absorb catalog traffic and bots at the edge; keep checkout on Magento. Webflow Add firewall, analytics, A/B, and Forms & Leads in front of Webflow sites.
FAQ
Drupal questions, answered.
Do I need to rebuild my Drupal site?
No. Sitewrap sits in front of your existing Drupal origin. Keep your templates, apps, hosting, and editors — Sitewrap adds the edge layer.
Will editors and admins still work?
Yes. Keep admin, editor, and other private paths origin-bound or gated. Public visitors get the cached, protected experience.
Is Sitewrap only for WordPress?
No. Firewall, cache, analytics, forms, deploy, and admin gating work in front of any CMS or static site. WordPress gets extra remaps and WAF defaults.
Can agencies standardize this across clients?
Yes. Wrap each client domain — whether Drupal, WordPress, or static — and manage cache, security, leads, and deploys from one Sitewrap account.
Wrap Drupal without rewriting it.
Create a Sitewrap account, gate admin, warm public pages, and point DNS.