deploybase vs Netlify
A European alternative to Netlify: the same git push and the same file conventions, hosted in the EU and billed in euros. Netlify does more; here is when that matters.
Choose deploybase if you
- need “where is our data?” to have one answer: the EU
- want the same invoice every month, in euros, with VAT handled
- want single sign-on without an Enterprise contract
- host static sites with forms and a few functions
Choose Netlify if you
- depend on edge functions or build plugins
- need SAML or SCIM sign-on today
- want the largest catalogue of integrations and tutorials
- have no data residency requirement
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
6 companies named by Netlify, all headquartered in the US.
- AWS Infrastructure US
- Datadog Monitoring US
- WorkOS Sign-in and SSO US
- CrowdStrike Endpoint security US
- Fivetran Data pipelines US
- Akismet Form spam filtering US
Netlify's companies as named on its trust center and in its forms documentation, read 24 September 2026; the roles are what each company sells. Ours are listed with legal entities on /subprocessors.
Netlify and deploybase, line by line.
| Capability | Netlify | deploybase |
|---|---|---|
| Where your data lives | ||
| Live platform metrics, public | Status page only | deploybase.eu/open + public stats API |
| EU data residency | US default | Scaleway Paris datacenter |
| No US sub-processors | AWS + US vendors | Scaleway, Bunny.net, Lettermint, Creem: all EU |
| Data stays in the EU | No | Yes |
| EEA-only edge delivery | Global CDN only | Yes |
| Billing | ||
| Transparent EUR pricing | Credits | Yes |
| No overages | Credit top-ups | Yes |
| EU VAT with reverse charge | No | Creem, an EU merchant of record |
| European billing provider | Stripe (US) | Yes |
| Both, on every plan: No per-seat pricing. | ||
| Deploying | ||
| Upload a pre-built site | Drop, CLI | Drag-and-drop or CLI, 20,000 files, zero build minutes |
| Priority builds | Paid plans | Yes, Pro and Scale |
| Both, on every plan: Git-connected deployments, Branch preview URLs, Branch deploy controls, Instant rollback, Auto-deploy on push. | ||
| Access and security | ||
| Geo-filtering (country access control) | Enterprise only | Yes |
| Password-protected share links | Site password on Pro | Yes |
| Private branch previews | Password on Pro only; on Free only the owner sees private previews | Team login and a shared password, free |
| Single sign-on for your team | Enterprise only | Keycloak, Authentik or another OIDC issuer, on the free planBeta, OpenID Connect only |
| Team roles (RBAC) | Paid plans | Yes |
| Both, on every plan: Custom domains + TLS, Environment variables. | ||
| Building | ||
| MCP server for AI tools | Official server | Yes |
| Form handling | US-stored | Stored in Paris, spam never counts |
| Verified external form recipients | No confirmation step | Yes |
| Codeberg integration | No | Yes |
| Serverless functions | Yes | YesBeta, on paid plans |
| Astro on-demand rendering | Yes | Yes, Starter and upBeta, on paid plans |
| Both, on every plan: API keys, Package manager auto-detection, SPA fallback and custom 404 pages, Redirects file (_redirects), Custom response headers (_headers), CLI deploys, GitHub integration, GitLab integration, Bitbucket integration, Scheduled functions. | ||
| Where Netlify is ahead | ||
| Edge functions | Yes | Not offered |
| Build plugins and extensions | Large catalogue | Not offered |
| SAML and SCIM | Enterprise | Not offered |
The same team, priced both ways.
Five people, three sites, 200 GB of traffic and 60 production deploys a month.
Netlify Pro
$40
a month, before requests and compute
- Pro plan with 3,000 credits
- $20
- 60 production deploys × 15 credits
- 900
- 200 GB × 20 credits
- 4,000
- Credits over the included 3,000
- 1,900
- 2 top-ups of 1,500 credits
- $20
deploybase Pro
€19
a month, VAT included
- Pro plan, unlimited members
- €19
- Sites
- 3 of 25
- Traffic
- 200 GB of 1 TB
- Deploys
- not counted
- Build minutes
- 3,000 included
Below 3,000 credits, about 100 GB with the same deploys, Netlify Pro costs $20 and the two are level. The difference is above that line: Netlify sells more credits, and we never add to the bill.
Netlify's prices and credit rates from netlify.com/pricing, read 24 September 2026.
Your netlify.toml, section by section.
Most of a Netlify site moves as it is: build settings copy across, and _headers and functions keep Netlify's format. Here is where each section goes, and what stays behind.
[build] command = "npm run build" publish = "dist"
Build command and output directory in project settings, filled in when we detect your framework.
[build.environment] PUBLIC_API_URL = "https://api.example.com"
Environment variables in project settings.
[[headers]]
for = "/*"
[headers.values]
X-Frame-Options = "DENY" A _headers file in the output directory, in the same syntax. Applied at the edge.
[[redirects]] from = "/*" to = "/index.html" status = 200
The same rule as a line in _redirects: /* /index.html 200. Redirects, rewrites, splats, placeholders and ! force rules apply at the edge.netlify.toml redirects are not read. No proxying to another site, no query or condition matching.
[functions] directory = "netlify/functions"
Move the files to functions/ at the root. Handlers in Netlify's Request and Response format usually run unchanged.In beta on paid plans.
[[edge_functions]] path = "/api/geo" function = "geo"
Nothing runs at the edge on deploybase.No equivalent.
[[plugins]] package = "@netlify/plugin-lighthouse"
Add the step to your build command instead; it takes any shell command.Build plugins are not supported.
Questions from Netlify users.
Something else? Write to support@deploybase.eu. A person answers.
Is Netlify GDPR compliant?
Netlify offers a data processing agreement and standard contractual clauses, which cover the legal side. Its infrastructure runs on Amazon Web Services, a US company. Every company we contract to process your data is headquartered in the EU; card payments in our billing provider's chain can run on Stripe, under standard contractual clauses.
Every subprocessor, namedCan I move a site from Netlify?
Yes. Connect the same repository and the build command and output directory copy across. _headers keeps Netlify's syntax, and functions keep its Request and Response format. Edge functions and build plugins have no equivalent. Move the domain last, by changing its DNS records.
The netlify.toml, section by sectionDoes deploybase run functions?
Yes, in beta on paid plans. A JavaScript or TypeScript file in functions/ becomes an HTTPS endpoint with your next production deploy. What we do not run is code at the edge.
How functions workIs deploybase as fast as Netlify?
For visitors in Europe, close to it. By default every request is answered from edge locations in the EU, Iceland and Norway, so visitors further away wait a little longer for the first byte. A custom domain can switch to worldwide delivery to serve them from nearby.
How is billing different?
Netlify bills in US dollars and counts deploys, traffic and compute against monthly credits, with top-ups when they run out. deploybase has four flat plans in euros, VAT included, with hard limits instead of an overage bill. Pro and Scale have unlimited members.
Every plan limitWhere are form submissions stored?
On deploybase, in Paris, and spam is scored on our own servers with no CAPTCHA. Netlify filters submissions through Akismet, a US service, and offers reCAPTCHA.
deploybase vs Netlify FormsCan I password-protect previews on the free plan?
Yes, on every deploybase plan: your team signs in, and anyone else types a password you share. On Netlify, a password is a Pro feature, and on Free and Personal only the Team Owner can see a private project (checked October 2026). Our Free plan has one member too, plus up to 3 viewers who sign in, and the password lets anyone else in.
Private previewsTry it on one site first.
Free plan, no card. Move the rest when you are sure.