Static sites, hosted
however you want.
Plug-and-play managed hosting on Cloudflare's edge — or deploy to your own S3, R2, Spaces, or any S3-compatible storage. Same Git push, same build pipeline, your choice of target.
Last updated on 17th April 2026
Static hosting deploys your pre-built HTML, CSS, JavaScript, and assets to the web. DeployHQ connects to your Git repository, runs your build pipeline (npm run build, jekyll build, hugo, etc.), and ships the output — either to managed hosting we run for you on Cloudflare's edge, or to your own S3, R2, or Spaces bucket. Same workflow, your choice of destination.
Supported Storage Providers
When you bring your own bucket, DeployHQ deploys to any S3-compatible object storage — with native support for the most popular providers.
Amazon S3
The industry standard for cloud object storage.
Cloudflare R2
Zero egress fees with Cloudflare's global network.
DigitalOcean Spaces
Simple, affordable object storage with CDN.
S3-Compatible
Any provider with an S3-compatible API (MinIO, Backblaze B2, Wasabi, etc.).
How It Works
From Git push to live static site in four simple steps.
Connect Your Repo
Link your GitHub, GitLab, or Bitbucket repository to DeployHQ.
Configure Your Build
Set up build commands for your static site generator — npm run build, jekyll build, hugo, or any custom script.
Set Your Target
Add your S3, R2, or Spaces bucket as a deployment target with your credentials.
Push & Deploy
Push to Git and DeployHQ automatically builds and deploys your site. Only changed files are uploaded.
Why Deploy Static Sites with DeployHQ
Everything you need for production-grade static site deployments.
Build Pipeline Included
Run npm, yarn, Jekyll, Hugo, Gatsby, Next.js static export, or any build tool in isolated Docker containers before deploying.
Incremental Uploads
Only changed files are uploaded to your bucket, making deployments fast and bandwidth-efficient.
Multiple Environments
Deploy to separate staging and production buckets from different branches — same project, different targets.
Works with Any SSG
Jekyll, Hugo, Gatsby, Next.js, Nuxt, Vite, Astro, Eleventy, plain HTML — if it outputs static files, DeployHQ can deploy it.
Perfect For
Common use cases for static site deployment.
Marketing Sites
Deploy landing pages, marketing sites, and documentation to S3 with CloudFront or R2 with Cloudflare CDN.
JAMstack Apps
Build with your favourite static site generator and deploy the output to cloud storage automatically.
Frontend Assets
Upload compiled CSS, JavaScript bundles, and images to a CDN-backed bucket alongside your server deployments.
Frequently Asked Questions
What storage providers does DeployHQ support?
DeployHQ natively supports Amazon S3, Cloudflare R2, DigitalOcean Spaces, Google Cloud Storage, and Rackspace Cloud Files. Any provider with an S3-compatible API (such as MinIO, Backblaze B2, or Wasabi) also works.
Can I run a build step before deploying?
Yes. DeployHQ includes build pipelines that run in isolated Docker containers. You can run npm, yarn, Jekyll, Hugo, or any custom build commands before your files are uploaded to storage.
Does DeployHQ only upload changed files?
Yes. DeployHQ compares your repository state and only uploads files that have changed since the last deployment. This makes deploys faster and reduces bandwidth usage.
Can I deploy to both a server and object storage in the same project?
Absolutely. A single DeployHQ project can have multiple deployment targets — for example, deploy your backend to an SSH server and your frontend assets to an S3 bucket, all in one push.
Do I need to configure the AWS CLI or any cloud SDKs?
No. DeployHQ handles the connection to your storage provider directly. You just provide your access credentials in the DeployHQ dashboard — no CLI tools or SDKs required on your machine.
Can I use a CDN with my static site?
Yes. You can pair your S3 bucket with CloudFront, your R2 bucket with Cloudflare CDN, or your Spaces bucket with the DigitalOcean CDN. DeployHQ deploys to the storage bucket, and your CDN serves the files to visitors.
Do I need an S3 bucket or storage account?
Not anymore. DeployHQ Managed Static Hosting (beta) gives you a *.deployhq-sites.com subdomain delivered through Cloudflare's global CDN, with optional SPA mode for client-side routing — no buckets or DNS setup required. You can still use S3, R2, or any S3-compatible storage if you already have one configured.
Need help? Ask our AI assistant
Got questions about DeployHQ? Our AI support assistant is available 24/7. Get instant answers about setup, configuration, deployments, and more.
Try Ask AIStart Deploying Static Sites Today
Set up your first static site deployment in under five minutes. No credit card required.
Free plan available · No credit card required · Cancel anytime
Explore More Features
Discover all the tools that make DeployHQ the easiest way to deploy your code.
Zero Downtime Deployments
→One-Click Rollback
→Turbo Deployments
→Build Pipelines
→Docker Builds
→Deployment Checks
→Deployment Targets
→Automatic Deployment
→Deployment Templates
→Deploy Behind Firewalls
→SSH Deployment
→Deployment Zones
→Team & Permissions
→Single Sign-On
→Custom Actions
→Server Management
→CLI & Agents
→Powerful Integrations
→Start your free trial today.
Deploy your static sites with confidence.