Eurobase is a fully EU-native backend-as-a-service platform — a free, GDPR-native European alternative to Firebase and Supabase. It provides 6 authentication methods (email, magic links, OAuth with Google/GitHub/LinkedIn/Apple, and phone SMS OTP), managed PostgreSQL, object storage, realtime subscriptions, Deno edge functions, encrypted vault, cron jobs, webhooks, a CLI with 50+ commands, and audit logging — all hosted exclusively on European infrastructure under EU jurisdiction.

How is Eurobase different from Firebase or Supabase?

Unlike Firebase (Google) and Supabase (US-based), Eurobase is 100% European-owned and operated on EU infrastructure. It is not subject to the US CLOUD Act, offers GDPR-native architecture with automated DPA reports, GDPR data export, sub-processor registry, and full audit logging. It includes features like encrypted vault, cron scheduling, webhooks with HMAC signing, and a dedicated CLI — with zero sovereignty compromise.

Is Eurobase GDPR compliant?

Yes. Eurobase is GDPR-native by design — not as an add-on. Every project ships one-click DSAR exports (Article 15 right of access + Article 20 right to data portability), an Article 30 Record-of-Processing report generated from your live configuration, a tamper-evident audit log with actor/action/IP, a per-project sub-processor registry, and row-level security. All data is stored on 100% EU-owned infrastructure (Scaleway, France) — zero US CLOUD Act exposure.

Do Firebase or Supabase offer built-in DSAR exports?

No. Neither Firebase nor Supabase ships a built-in DSAR (Data Subject Access Request) primitive. On Firebase you write a custom Cloud Function that walks every Firestore collection plus Auth and Storage. On Supabase you hand-roll SQL across auth.users and every public table. On AWS Amplify you stitch DynamoDB, Cognito, and S3 buckets together yourself. Eurobase is the only EU-native BaaS that ships GDPR Article 15 + Article 20 exports as a one-click platform feature, available on every project and every tier — free included. We won't paywall a legal obligation.

How much does a DSAR cost to fulfil manually?

Industry surveys put the average cost of fulfilling a single DSAR at around $1,500 — typically 8–12 hours of engineering time spent stitching CSV exports together, searching support tools, and walking application logs. Request volume jumped 246% in the two years to 2024. Statutory response time under GDPR Article 12 is 30 days; missing it carries supervisory-authority risk up to €20 million or 4% of global annual turnover. Eurobase replaces the manual workflow with a one-click console export plus an SDK call (`eb.auth.exportMyData()`) that lets end-users self-serve, rate-limited and audited.

Is Eurobase free to use?

Yes. The Free tier includes 5,000 monthly active users, 512 MB storage, 2 GB bandwidth, 50 realtime connections, and every feature — no credit card required. Projects auto-pause after 30 days idle and wake on the first request. Pro is €25/mo per project (no pausing, custom email templates, BYO SMTP, quota alerts, 100,000 MAU). A Team tier with dedicated PostgreSQL 16 (2 vCPU / 4 GB RAM / 50 GB SSD, France) is €149/mo per project (coming soon). A Legal Team tier for German legal-tech is in closed beta — pricing on request.

What are the limits for auth emails (verification, password reset, magic link) on Pro?

No throughput cap from our side when you use BYO SMTP. Verification, password-reset, and magic-link emails all route through the same dispatcher: if a verified custom SMTP sender is configured on your project, the send goes through your provider and skips our platform sender entirely — your provider's limits apply, not ours. Without BYO SMTP, sends go through our platform TEM; there's no hourly project cap enforced today. Rate-limits page in the console shows what applies.

Can I send verification or password-reset emails to thousands of users at once on Eurobase?

Yes — no recipient-count limit. Distributed real users each come from their own IP, so the two anti-abuse throttles that do apply don't bite a real user base: signup/signin is capped per-IP (up to 30 per 5 minutes on Pro), and token verifications are capped per-IP (up to 150 per 5 minutes on Pro). Password-reset volume itself is unbounded from our side. Pair Pro with BYO SMTP (SendGrid, Postmark, Amazon SES, Scaleway TEM) and your provider is the only ceiling.

Can I fully customize verification, password-reset, and magic-link emails on Eurobase?

Yes on Pro and above — subject line and HTML body are independently customizable per template type (verification, password_reset, magic_link). Templates are picked up automatically on every send with no code change. Free tier uses the default templates.

Does Eurobase support German legal-tech retention (§50 BRAO / §257 HGB / §147 AO)?

Yes, on the Legal Team tier (closed beta). §50 BRAO Aufbewahrungspflicht is 6 years flat; §257 HGB is split (10 years for Handelsbücher / Rechnungen / Jahresabschlüsse, 6 years for Handelsbriefe); §147 AO mirrors the §257 HGB split. Legal Team ships WORM per-prefix object-storage locks, ad-hoc retention holds (per record / per prefix), DSAR erasure that respects legal holds, a 10-year audit-log retention window, signed §203 StGB Verschwiegenheitsverpflichtungen from every staff member with data access, and a GoBD Verfahrensdokumentation. See eurobase.app/security#de-legaltech for the full dossier and the linked v2 legal documents.

What backend does a German legal-tech / Kanzlei-facing product actually need?

Four hard blockers you cannot solve with a plain EU-region Firebase or Supabase deployment: (1) §203 StGB / §43e BRAO staff-secrecy paperwork — signed declarations from every staff member with data access; (2) statutory retention with WORM enforcement — §50 BRAO 6y, §257 HGB 10y books / 6y letters, §147 AO mirror; (3) GoBD-conformant exports plus a Verfahrensdokumentation; (4) 10-year tamper-evident audit-log retention. Eurobase closes all four on the Legal Team tier (closed beta) via an addendum to the DPA. Region-only EU hosting does not satisfy any of them.

Does Eurobase have BSI C5, ISO 27001, and IT-Grundschutz coverage?

Actual certificates are on the post-beta roadmap. Today the dossier at eurobase.app/security#de-legaltech includes a dated BSI C5 roadmap (target Type-1 attestation 12 months post-launch), an ISO 27001 Statement of Applicability draft covering 2022 Annex A controls, a BSI IT-Grundschutz self-declaration under the Basis-Absicherung profile for SME, a NIS-2 positioning document (below employee/revenue thresholds today, voluntary cascade-obligation compliance, commitment to register on crossing), and an AI Act positioning document (Eurobase is infrastructure, not an AI system; the Customer is the deployer for any high-risk build).

Is Eurobase available today?

Yes — sign up at console.eurobase.app, no credit card required. The complete backend platform — including auth, database, storage, realtime with row-level filtering, edge functions with scheduled jobs, vault, cron, webhooks, CLI, GDPR self-serve export, MCP server, and audit logging — is built and in production. Free tier: 5,000 monthly active users, 512 MB Postgres, all features included. Pro: €25/mo per project.

Is Eurobase good for vibe coding?

Absolutely. Eurobase is designed for fast iteration — sign up, get your API keys, and start building in minutes. Auth (6 methods), database, storage, realtime, functions, vault, cron, and webhooks are ready out of the box with simple SDKs and a CLI with 50+ commands. No infrastructure setup, no DevOps, no compliance paperwork. Just vibe and build.

Where is Eurobase data stored?

All data is stored exclusively on European infrastructure operated by EU-owned providers, specifically Scaleway in France. Eurobase has zero exposure to the US CLOUD Act or similar extraterritorial legislation. Your data never leaves EU jurisdiction.

Is there a Supabase alternative in the EU?

Yes. Eurobase is a Supabase-compatible backend built and hosted entirely in the EU. Same Postgres foundation, same auth + storage + realtime + edge functions surface, same SDK shape. The difference is the corporate parent (Estonian OÜ vs Delaware) and the infrastructure floor (Scaleway in France vs AWS). That removes the CLOUD Act exposure that survives even when Supabase is deployed in an EU region.

Is a Supabase EU-region deployment enough for GDPR?

Picking Supabase's EU region gives you physical data residency in the EEA and a standard SCC-based DPA — a competent baseline, but not immunity from the CLOUD Act. Because Supabase Inc. is a Delaware corporation using AWS, US authorities can compel data access even for EU-region deployments. Eurobase removes that exposure by having no US corporate parent and no US-owned processor in the critical path.

How do I migrate from Supabase to Eurobase?

Use the Eurobase CLI: `eurobase import supabase assess` for a read-only report against your existing Supabase project, then `eurobase import supabase schema | data | storage | functions` to move each surface. Auth-user import is next. The CLI reads your Supabase project directly and emits an executable plan; no rewrites required on your app code.

My app is built on the supabase-js client. Do I have to rewrite my client layer?

The honest picture on three levels. (1) Shape-parity: @eurobase/sdk mirrors @supabase/supabase-js deliberately — same .from(table).select().eq() chain, same channel(name).on('postgres_changes', …) subscribe shape, same auth methods. In practice this is search-replace on imports + package name, not a rewrite of query call sites. (2) Drop-in supabase-js wire-compat (same package name, no code change at all) is on the roadmap as a shim package — it removes the young-company objection entirely. (3) Zero-SDK escape hatch on Team tier: a direct Postgres DATABASE_URL means Payload, Prisma, Drizzle, or any Postgres client works without any Eurobase-specific code — the reversibility guarantee then covers your app code too, not just your data.

Are automatic backups included?

Free and Pro projects share a pooled Postgres cluster (Scaleway Managed Database, France) with cluster-level snapshots (daily, 7-day retention). Restores go through support. Team tier gets dedicated Postgres per project with daily scheduled backups (7-day retention) plus customer-triggered on-demand snapshots and 1 self-service restore per calendar month — from either source, either counts against the same cap. On every tier, `eurobase db dump` produces a standard pg_dump you can export anywhere at any time — the first-line reversibility guarantee independent of us.

What happens if I exceed the Pro-tier storage or bandwidth caps?

No overnight blackout — that is a business-risk pattern paying customers can't manage, and one of the clearest pieces of feedback from beta users. The Pro-tier overage policy for public beta: (1) email alerts at 75% and 100% of the storage / bandwidth caps. (2) A 14-day soft-grace window where writes continue and the console shows the overage banner — enough time to upgrade to Team, buy an add-on capacity block, or optimise. (3) Only after the grace window does the affected module hard-block writes — and even then reads always continue. Team tier (dedicated Postgres per project + elastic storage tier) removes the caps entirely and is the recommended path for photo/video-heavy or streaming workloads. We do not meter per-GB overage on Pro — no surprise line items.

How is the 10,000 realtime connections cap counted?

Active concurrent WebSocket connections. No hard limit on messages/second or connection duration today, but soft fair-use at ~100 msg/s per connection and ~1M msg/s per project — raiseable on request. Practical connection duration is bounded by TCP keepalive + our load-balancer idle timeout (600 s).

Can I point Eurobase at my own S3 bucket (BYO storage)?

Not today. BYO S3 is on the Team-tier roadmap — it needs per-tenant credentials + audit-path rewiring. No firm date. In the meantime, our object storage runs on Scaleway (Paris, France) with the same sovereignty guarantees as the rest of the platform.

Who is the contracting legal entity, and does it have any non-EU parent or subsidiary?

Contracting entity: Eurobase OÜ, Estonian private limited company, registry code 17557586, Ahtri 12, Tallinn 15551. Not VAT-registered under Estonian VAT Act §19. No parent company, no subsidiaries, no non-EU entity. Sole shareholder is the founder. Every sub-processor in the RoPA is EU-headquartered.

Do you provide a signable DPA and an up-to-date sub-processor list?

Yes. DPA v2 is signable at eurobase.app/legal. The sub-processor list is auto-generated per project in the console Compliance tab as an Article 30 report (downloadable PDF, updated on every configuration change). No email tickets, no stale spreadsheets.

When can your team access customer data, and can I audit it?

Our team is three people, all physically in the EU. Every operator SQL call goes through an authenticated pool that writes to public.data_access_log — every query stamped with actor, source IP, and active Postgres role. You see that table from your own console (Audit tab). We do not process your data content for any purpose other than platform operation.

What SLA do you commit to per tier?

Free: no commitment. Pro: 99.5%/month, support response within 24h business hours. Team: 99.9%/month, response within 4h. No automatic downtime credits today — honest reflection of team size at launch. Credits land with the Team tier opening.

What happens to my data — and my app code — if Eurobase ceases operations?

Data reversibility, four lines of defence. (1) Standard formats: Postgres + S3-compatible = migration to any host (Scaleway direct, OVH, Aiven, self-hosted) is documented, not a rewrite. (2) Export CLI: eurobase export produces a full dump (schema + data + storage + functions). (3) Source is public today: platform code lives on github.com/STGime/euroback under BUSL-1.1, with an Additional Use Grant that permits self-hosting for your own apps and internal tools; each commit auto-converts to Apache 2.0 four years after it lands. SDK + MCP server are MIT. What is not shipped yet is a supported self-host distribution. (4) On shutdown: 90-day notice + 90 additional days of read-only service to finalise export. App-code reversibility, two mitigations: (a) @eurobase/sdk is shape-parity with supabase-js, so migrating away is search-replace on imports, not query-site rewrites. (b) On Team tier, the direct DATABASE_URL means your app can talk to Postgres with Payload / Prisma / Drizzle / psql — no Eurobase code in the client at all — so migration is a hostname change.

How big is the Eurobase team, and how are you funded?

Core team: founder + two long-term freelancers, all EU-based. Bootstrapped, with EU-Sovereign-Cloud grant applications in flight and preliminary angel conversations. The way to size that risk is not our reassurances — it is the reversibility guarantee (Postgres dump + standard S3 + source public on GitHub under BUSL, auto-Apache 2.0 after four years). If we sink, you migrate to Scaleway direct in a weekend using the export CLI.

← Back to blog

What a German LegalTech Startup Actually Needs From Its Backend

Stefan Gimeson·August 5, 2026·7 min read

One of our closed-beta customers is a German legal-tech startup. They are the reason a new premium tier — working name Legal Team — is being built alongside the base Team tier. This post is the honest ledger of what a Kanzlei-facing backend has to do, what Eurobase does today, and what is landing over the next few weeks.

If you are thinking of building a product for lawyers, Steuerberater, notaries, or legal-ops teams in Germany, treat this as the checklist we wish we had been handed on day one.

The four hard blockers most stacks quietly ignore

A German law-firm buyer will not sign an order form until four questions are answered on paper. These are not "GDPR" in the general sense — they are additional, sector-specific obligations layered on top.

1. §203 StGB and §43e BRAO — the secrecy chain. Since the 2017 amendment, a lawyer is only allowed to use a third-party service if that service — and every individual employee of the service with access to client data — is bound in writing to the same criminal-liability secrecy the lawyer is bound to. Miss this, and the lawyer commits a criminal offence the moment client data lands on your servers. The paperwork is not optional and it names names: a signed Verschwiegenheitsverpflichtung for every relevant staff member, revocation dates included.

2. GoBD — Unveränderbarkeit and 10-year retention. The BMF's GoBD circular reads §§145–147 AO as requiring "unveränderbare" (immutable) storage of tax-relevant records for ten years. In practice: object-lock / WORM storage, a Verfahrensdokumentation describing how you achieve it, and export in a specific structured shape (INDEX.XML + CSV per table) so the tax office can ingest it directly.

3. Legal-hold-aware erasure. GDPR Article 17 gives an end-user the right to be forgotten. §50 BRAO says a lawyer must retain the client file for six years. §257 HGB and §147 AO push some records to ten. The two rules collide inside every DSAR request that touches a document with an active legal hold. The correct answer is neither "delete everything" nor "refuse the request" — it is to erase what can be erased, retain what must be retained, and tell the requester which items are on hold and until when.

4. GoBD-conformant export. A generic JSON/CSV dump is not enough. The Betriebsprüfung expects a specific bundle shape (BMF DTD, UTF-8 or ISO 8859-15, semicolon-separated, a Verfahrensdokumentation next to it). Miss the shape and the auditor rejects the export.

These four together are the reason a legal-tech founder cannot just use Firebase-EU, cannot just use Supabase-Frankfurt, and cannot just use a bare managed Postgres from any provider. The gaps are at the application layer, not the region layer.

What Eurobase already ships (every tier, including Free)

The compliance primitives that every GDPR-serious backend needs are in the base product on day one:

▸EU-only jurisdiction, end to end. Eurobase OÜ is an Estonian entity; compute, Postgres, object storage, and edge functions all run on Scaleway fr-par. No US processor in the path — the DPF/CLOUD Act debate is not your problem. We wrote the longer form of this in "Our Data Deserves a Better Agreement".
▸DSAR export in one click. Article 15 + Article 20, per-user or full-project zip. No consultant, no custom SQL join, no PDF-generation library on your critical path.
▸Article 30 record auto-generated from the actual sub-processor registry — so when the auditor asks "who touches this data," the answer is verifiable rather than curated.
▸Tamper-evident audit log, hash-chained per project with a verify endpoint. Every admin action, every DSAR request, every credential rotation is recorded with actor + IP + timestamp, and a broken chain surfaces immediately.
▸Breach register with 24h/72h SLAs aligned to Art 33 GDPR — the workflow that shipped in PR #219 tracks incident acknowledgement, root-cause narrative, and notification to authorities and affected subjects, with the clocks visible on the dashboard.
▸Signed DPA v2 with Eurobase OÜ named as processor; template Article 28 subcontracting clauses included; sub-processor registry linked to feature flags so a customer sees exactly which processor is engaged for which feature.

That gets a general SaaS to a GDPR-defensible posture. It does not, by itself, meet the four hard legal-tech blockers.

What is landing in the Legal Team tier (weeks, not quarters)

The base Team tier ships a dedicated Postgres instance per project, daily scheduled backups with on-demand snapshots, and a direct DATABASE_URL for Payload / Prisma / Drizzle stacks — the last of those merged this morning. On top of that, the Legal Team tier layers the four blockers above:

§203 / §43e paperwork surface. A signed de-legal-tech-addendum extends the DPA with §43e BRAO clauses and a §203 StGB Verschwiegenheitsverpflichtung template. Every Eurobase staff member with data access signs an individual declaration; the register is queryable via a public read endpoint so your firm can pull it into its own §43e audit file. A signed staff registry means your customer's compliance officer does not have to trust our marketing.

Object-lock / WORM on tenant storage (GoBD Unveränderbarkeit). Scaleway Object Storage supports S3 Object Lock in both compliance and governance modes. Team-tier buckets are created with object-lock enabled; a per-prefix policy UI lets you pin /invoices/*, /mandant/*, /tax/* to a ten-year retention by default. Immutable at the storage layer, not just enforced by app code.

Legal-hold-aware erasure. A retention_holds table records legal basis + expiry per row / per object / per table. The DSAR path checks it on every erase, skips held items, and returns them in the response as "retained under <legal_basis>, purgeable after <expires_at>" — so the requester and the DPO see the exact reason and the exact date. A daily worker sweeps expired holds so the erasure surface reopens automatically.

GoBD export endpoint. A dedicated endpoint that returns INDEX.XML (BMF DTD-conformant) + one CSV per table + a Verfahrensdokumentation template alongside. Uses the same River queue + S3-signed-URL delivery mechanism as the existing DSAR export, so the audit trail is identical.

10-year audit-log retention. The audit-log retention worker on Legal Team is pinned to 3,650 days so the tamper-evident chain itself is queryable inside the full statutory window, without falling back to the off-box WORM archive.

Under the hood these are Milestone M2b on the Team-tier roadmap, tracked in a stacked series of PRs against main. The addendum text sits open pending German + Estonian legal signoff (issue #333).

What we deliberately do not do

Every honest sales conversation should include a list of things the product does not solve. For the German legal stack that list includes:

▸beA integration. The BRAK's electronic-lawyer inbox is an app-layer concern. We do not sit in that flow and do not intend to.
▸TR-ESOR / BSI TR-03125. The German long-term-preservation profile expects dedicated middleware from Governikus or the ArchiSafe ecosystem. We integrate with those, we do not try to replace them.
▸DATEV / ELSTER. Steuerberater tooling for accounting export and tax filing is app-side. Our GoBD export produces the raw structured records; the last-mile format-conversion into DATEV or ELSTER-XML lives in your app.
▸Formal ISO 27001 / BSI C5 certification. On the roadmap post-beta with a target date documented in the trust center. Not certified today. If your customer requires a paper certificate before signature, we are not ready; if they will accept a Grundschutz self-declaration + a scheduled certification, we are.

Concrete positioning for a legal-tech founder

If you are picking a backend for a legal-tech product aimed at the German or wider DACH market:

▸Bare managed Postgres from an EU provider (Scaleway, OVHcloud, Aiven) solves the region + jurisdiction question. It does not solve DSAR, audit log, retention holds, GoBD export, or §203 paperwork — those are hundreds of hours of app-layer engineering per team.
▸Firebase or Supabase EU-region solves the developer-experience question. It does not solve any of the four hard blockers, and adds a US-parent CLOUD Act exposure your customer will notice on the second call.
▸Eurobase solves the region + jurisdiction question on day one (Free tier), the compliance-primitive question on every tier, and — once the Legal Team tier ships in the coming weeks — the four legal-tech-specific blockers. The trade-off is the price step (Legal Team carries a large premium over base Team, and the number is deliberately not published until the closed beta lands its first paid conversion), and the ISO/BSI paper certificates that are on the roadmap rather than in hand today.

If any of the above sounds like your product, the closed beta is where the actual product feedback loop is happening. The Legal Team tier will open with hand-picked customers first, at zero cost while we lock in the price and the paperwork. If you want to be one of them, open an issue on the public tracker or reach out — the door is open, small enough that we know our customers by name.