deploybase vs StaticHost

Two European static hosts. Both keep your data in the EU, so residency is not the question here: pricing and features are. StaticHost does some things we do not; here is which.

Choose deploybase if you

  • want the whole team on one price, not €19 a seat after five
  • want hard limits instead of overage charges
  • want a preview of every branch, made on push
  • need forms, single sign-on or functions next to the site

Choose StaticHost if you

  • want unlimited sites for €9 a month
  • need redirects and proxy rewrites applied today
  • want to build with a Docker image you choose
  • host code on SourceHut or Azure DevOps

Who handles your data.

A data processing agreement tells you what a company promises. The list of companies behind it tells you where the data actually goes.

4 companies, all headquartered in the EU. Sign-in and the database run on our own servers in Paris.

  • Scaleway Servers, builds, database, storage Paris, FR
  • Bunny.net Delivery, site files, DNS Ljubljana, SI
  • Lettermint Email Zwolle, NL
  • Creem Billing, the company you buy fromCard payments can run on Stripe (US) Tallinn, EE

StaticHost runs its core systems on its own servers and names one processor in its privacy policy: its bank. Its CDN provider is not named there.

  • StaticHost Run by Variable Object Assignment Stockholm, SE
  • Own servers Accounts and core systems EU/EEA
  • Handelsbanken Bank transfers SE

StaticHost as described in its privacy policy, read 24 September 2026. Ours are listed with legal entities on /subprocessors.

StaticHost and deploybase, line by line.

Feature comparison between StaticHost and deploybase
CapabilityStaticHostdeploybase
Where your data lives
Live platform metrics, publicNodeploybase.eu/open + public stats API
Both, on every plan: EU data residency.
Billing
No overagesOverage billingYes
No per-seat pricing€19/seatYes
Both, on every plan: Transparent EUR pricing.
Deploying
Upload a pre-built siteZip or CLIDrag-and-drop or CLI, 20,000 files, zero build minutes
Branch preview URLsA separate site per branchYes
Priority buildsPaid plansYes, Pro and Scale
Both, on every plan: Git-connected deployments, Auto-deploy on push.
Access and security
Password-protected share linksWhole site, basic authYes
Both, on every plan: Custom domains + TLS, Environment variables, Team roles (RBAC).
Building
Form handlingNoStored in Paris, spam never counts
Verified external form recipientsNoYes
Codeberg integrationForgejo, CodebergYes
Serverless functionsNoYesBeta, on paid plans
Scheduled functionsNoYes
Astro on-demand renderingNoYes, Starter and upBeta, on paid plans
Both, on every plan: API keys, GitHub integration, GitLab integration, Bitbucket integration.
Where StaticHost is ahead
Redirects and proxy rewrites at the edgeYesNot offered
Any Docker image as the build environmentYesNot offered
Unlimited sitesFrom €9 a monthNot offered
SourceHut and Azure DevOpsYesNot offered

The same team, priced both ways.

Ten people, five sites, 300 GB of traffic a month.

StaticHost Professional

€144

a month

Professional, 5 seats included
€49
5 more seats × €19
€95
300 GB of the included 1 TB
€0
Builds, 5,000 minutes included
€0

deploybase Pro

€19

a month, VAT included

Pro plan, unlimited members
€19
Sites
5 of 25
Traffic
300 GB of 1 TB
Build minutes
3,000 included

For one person it flips: StaticHost Starter is €9 for unlimited sites and 5,000 build minutes, where our €9 Starter has 10 sites and 1,000. StaticHost's pricing page does not say whether VAT is included; ours is.

StaticHost's prices from statichost.eu/pricing, read 24 September 2026.

Your StaticHost site, file by file.

Both hosts read _headers and _redirects, so most of a site moves as it is. The build image, regex headers and most redirects do not, yet.

Your repository on deploybase
# statichost.yml
image: node:20
command: npm ci && npm run build
public: dist

Build command npm run build and output directory dist in project settings. We install dependencies and pick the build image from your framework.You cannot choose your own build image.

# _headers
*
    X-Frame-Options: DENY
~/\.([a-f0-9]{8})\.js$/
    Cache-Control: public, immutable

The same _headers file works for plain and wildcard paths, applied at the edge.Regex paths (~/…/) are not supported; one * per path.

# _redirects
/*        /index.html   200

Detected as the single-page app fallback, on its own.

# _redirects
/old/post.html   /posts/old/   301

Read and stored with the deployment.Not yet applied at the edge.

# Password protection (dashboard)

A password on a share link, for any deployment. The production site itself stays public.No password on the production site.

./shcli your-site ./public

deploybase deploy ./public, or drag the folder onto the dashboard. Uploads use no build minutes.

Questions from StaticHost users.

Something else? Write to support@deploybase.eu. A person answers.

Aren't both of you European?

Yes. Both keep your data in the EU, and neither runs on a US cloud. Residency is not the difference here. Pricing is (seats and overage charges against one flat price), and so are the features: previews, forms, single sign-on and functions here; redirects, any build image and unlimited sites there.

How does pricing differ?

StaticHost Professional is €49 with five seats, then €19 a seat, and past the included amounts it charges €1 per 10 GB of traffic and €1 per 100 build minutes. deploybase has four flat plans, VAT included, unlimited members on Pro and Scale, and hard limits instead of an overage bill.

Every plan limit
Does StaticHost have branch previews?

Not yet. Its documentation lists automatic preview links as on the roadmap and suggests a separate site per branch meanwhile. Here every branch gets its own preview URL when you push.

Can I keep my _headers and _redirects files?

_headers works as it is for plain and wildcard paths; regex paths do not. From _redirects, the single-page app catch-all is applied, and every other rule is stored but not yet applied at the edge. StaticHost applies them all today.

Which git providers does each support?

StaticHost: GitHub, GitLab, Bitbucket, Azure DevOps, Forgejo (Codeberg) and SourceHut. deploybase: GitHub, GitLab, Bitbucket and Codeberg. Both also take a direct upload.

Can I password-protect a site?

On StaticHost, yes: the whole site, with HTTP basic auth, on plans that include it. On deploybase, a password goes on a share link to a single deployment, on every plan. The production site itself cannot be password-protected yet.

Compare them on one site.

Free plan, no card. Both of us are in the EU; pick on the rest.