Hi Brice,
Some of the doc pages you found were written before our latest hosting and legal updates. Where they disagree with this post, the Terms and DPA take precedence.
1. Capacity
Concurrent users. There is no concurrent-user limit. App sessions and end users are also unlimited on every paid WeWeb Cloud tier. What is metered is resources:
The front end is served from a CDN, so concurrency depends on how much backend work each user generates, not on user count. On Scale+, the database autoscales, and you can configure serverless RAM up to 10 GB.
Tiers and Enterprise limits. The current tiers are Free, Front-end only, Launch+, Grow+, and Scale+. The docs page you found still uses the old names. Enterprise limits are not published: they are set in your contract and sized to your expected usage.
What happens above a limit? It depends on the tier. On Free, Launch+, and Grow+, the included allocations are hard limits: if you exceed one, you may see throttling or temporary service interruptions until you upgrade or the monthly allowance resets. Your data is never deleted. On Front-end only and Scale+, your app is not cut off: usage beyond the included allocation is billed automatically at the published per-unit rates, for example, $0.25/GB of bandwidth beyond 200 GB on Scale+. On an Enterprise contract, the overage terms in your agreement apply. For a production public-sector app, I would recommend Scale+ or Enterprise-sized limits, so the app can never be blocked for hitting a limit.
Load testing. We are happy to support one, but please coordinate it with us first. Our Terms (§12.3.3) require prior written consent for load tests against WeWeb Cloud, so the traffic isn’t treated as an attack. Send us your plan (target concurrency, scenarios, timing), and we will set it up with you.
2. Security
Certifications. WeWeb does not currently hold SOC 2 or ISO 27001 itself. The platform runs on AWS, which holds SOC 2 Type II and ISO 27001 for its data centers. Our technical and organizational measures are set out in Annex 2 of the DPA:
-
TLS in transit and encryption at rest
-
MFA and least-privilege access to production
-
Monitoring, logging, and an incident-response process
-
Periodic penetration tests and vulnerability assessments
-
Redundancy across multiple availability zones
WAF and DDoS. Apps on WeWeb Cloud are served through AWS CloudFront, which includes AWS Shield Standard DDoS protection.
Whitepaper and audit contact. Annex 2 of the DPA is our formal security documentation. For audits and security questionnaires on an Enterprise contract, please contact us.
3. Hosting and GDPR
EU hosting. Yes. When you set up a WeWeb Cloud backend, you choose its Hosting Region: US, EU, or APAC. Database records, files, and serverless workflow execution stay in that region (Terms §8.1–8.2).
The FAQ answer about Northern Virginia is outdated.
-
You can’t change the region later. It’s fixed when you first set up the project’s backend. If your backend already exists in the US region, you’d need a new project in the EU region and a data migration.
-
The residency commitment covers backend data only. The following are handled outside your chosen region:
-
The Editor and project configuration, account data, and telemetry, which run on our central infrastructure (mainly US and EU)
-
Front-end files cached at CDN edge locations
-
Data sent to AI model providers
For a public-sector app, I would suggest three things:
-
Keep only anonymized or sample data in your development environment. The Editor’s AI features can read it; they never touch staging or production.
-
Don’t send personal data through AI Gateway; use your own API key with an approved provider.
-
Connect your own email provider instead of the default one.
DPA. Yes. It’s published at dpa.weweb.io and forms part of our Terms. An updated version takes effect on 15 November 2026. It covers:
-
Article 28 obligations
-
The sub-processor list with data locations (Annex 3)
-
Standard Contractual Clauses for transfers outside the EEA
-
72-hour breach notification
-
Audit rights
We can also provide information for a transfer impact assessment on request (§7.4). WeWeb is WEWEB SAS, headquartered in Paris, and both documents are governed by French law.
SLA and status page. Standard tiers don’t include an SLA. Enterprise does: uptime commitments, remedies, and support response times are set in your Enterprise Agreement. You can follow live status and uptime history on our public status page at status.weweb.io.
If you need sovereign or on-premises hosting
If your organization’s policy requires a SecNumCloud-qualified host, or your own infrastructure, you can export the full application (front end and backend) and self-host it. This works even in an air-gapped network, and WeWeb Cloud limits don’t apply when self-hosting. See the AWS full-stack self-hosting guide.