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 signed DPA (Auftragsverarbeitungsvertrag) and an up-to-date sub-processor list?

Yes, on every tier — including Free. Our Data Processing Agreement v2 (Art. 28 GDPR) is accepted click-through when you create your account, which is a valid written form under Art. 28(9). The full text, with Eurobase OÜ's legal name, registered address and registry code, the technical and organisational measures, and the live sub-processor annex, is always at console.eurobase.app/legal/dpa — print it or save it as PDF for your records. The always-current list of authorised sub-processors is at console.eurobase.app/legal/sub-processors, and the per-project Article 30 report in the console Compliance tab lists the ones actually engaged by the features you have enabled. A countersigned copy of the DPA on our letterhead, with the sub-processor list attached, is a paid-tier service: available on Pro and above on request, not on Free.

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.

Do Free-tier projects really pause, and what counts as activity?

After 30 days without a request, yes. Activity means a request to your project's own endpoint, .eurobase.app — anything the SDK, REST API, realtime or an edge-function call sends. Scheduled cron jobs running inside the project and console / CLI actions on the platform API do not count. Nothing is deleted or archived when a project pauses: the database keeps running, your data stays exactly where it is, and cron jobs keep firing. The only effect is that the first request after a pause takes about 30 seconds while the project flips back to active; every request after that is instant. Pro projects never pause.

How do I script a full export or nightly backup of a project?

Use the compliance export, which works on every tier including Free. Create a Personal Access Token in the console (Account → Personal Access Tokens; it starts with eb_pat_) and call POST /platform/projects/{id}/compliance/export on api.eurobase.app with Authorization: Bearer and a body of {"format":"json"} or "csv". The project's public / anon key cannot call it — it is a platform endpoint, and the token must belong to an admin of the project. The call returns an export id; poll GET …/compliance/exports/{exportId} until status is completed, then fetch download_url (a presigned link valid for one hour). The ZIP holds every table in your project's schema (up to 100,000 rows per table), including the auth users table, plus the project audit log (latest 10,000 entries) and a metadata file, and is kept for 7 days. Uploaded files in storage are not in the archive — pull those through the storage API. Limit: one full export per project per hour, so a nightly job is fine. Every export is written to the audit log. On Free the export is API-only; the one-click button in the console Compliance tab is Pro and above.

Why does my SDK insert fail with 'row-level security policy denied this operation' even with WITH CHECK (true)?

This is a Postgres RLS gotcha, not a gateway bug. The SDK executes every insert as INSERT ... RETURNING * so it can return the created row. On RETURNING, Postgres applies RLS twice: the INSERT policy's WITH CHECK when writing, then the SELECT policy's USING when reading the row back. If you have an INSERT policy but no matching SELECT policy, the write rolls back with the same error text as a real INSERT failure — misleading, which is why WITH CHECK (true) did not help. Fix: add a matching SELECT policy, usually with the same predicate. If your INSERT is WITH CHECK (user_id = auth_uid()), add FOR SELECT USING (user_id = auth_uid()). The Table Editor works because it goes through the elevated is_service_role() branch, so tenant RLS does not apply there. Full guide: console.eurobase.app/docs/rls.

← Back to home

Feature · Automated DSAR

One click. Article 15 + 20. Built into every project.

When a user emails "what do you have on me?" (Article 15) or asks for their data on the way out (Article 20), Eurobase turns the answer into a one-click console export. No SQL to write each time. No middleware to maintain. The 30-day deadline stays statutory; the tooling stops being the bottleneck.

The Cost

The cost of DIY DSAR

A single DSAR runs about $1,500 to fulfil — and request volume is up 246% in two years. That cost lands on whoever happens to be on call.

$1,500

Avg. cost per DSAR fulfilment^[1]

8–12 hrs of engineering per request

246%

Two-year jump in DSAR volume^[1]

Industry survey, 2024

30 days

Statutory deadline (GDPR Art. 12)

Miss it = supervisory-authority risk

€20M

GDPR maximum administrative fine

or 4% of global annual turnover

^[1]Eurobase blog — "The $1,524 GDPR Tax"

The Gap

Built-in elsewhere? No.

Every other major BaaS leaves DSAR fulfilment as homework. Custom SQL across every table, custom middleware, custom audit trail. Re-implemented per project.

Platform	Built-in DSAR?	What you do instead
Firebase	✗No DSAR primitive	DIY Cloud Function across Firestore collections + Auth + Storage
Supabase	✗No DSAR endpoint	Hand-roll across auth.users and every public table
AWS Amplify	✗No DSAR primitive	DIY across DynamoDB / Cognito / S3 buckets
Eurobase	✓One click. Every project. Every tier.	Per-user export + full-project zip + audit trail — out of the box

The Answer

The Eurobase answer

DSAR is a first-class platform feature — not a checkbox in an enterprise tier, not a paragraph in the privacy policy. We built it because we got tired of watching small EU teams treat each request as a fire drill.

✓

Article 15 + Article 20 in one click.

Per-user export (every row referencing their user_id) and full-project export (every table + auth + storage manifest) as a downloadable zip.

✓

Audit log captures every request, completion, and failure.

Actor email + IP, stamped on every action. Your evidence trail is built in, not bolted on.

✓

All bytes stay on Scaleway fr-par.

Zero CLOUD Act exposure. Download links expire after 7 days. EU jurisdiction end-to-end.

✓

API stays open on every tier.

Free-tier projects can still meet a statutory deadline by calling the export endpoint directly — we won't paywall a legal obligation.

In code

End-users can self-serve. Operators can trigger a per-user or full-project export from the console or the platform API. All paths are audit-logged.

// Article 15 — end-user exports their own data via the SDK
const { data: req } = await eb.auth.exportMyData('json')

// Article 20 — operator triggers a per-user export (single subject)
POST /platform/projects/{id}/compliance/exports/user
  { "user_id": "..." }

// Article 20 — operator triggers a full-project export (every table + auth + storage)
POST /platform/projects/{id}/compliance/exports

One click. Article 15 + 20. Built into every project.

The cost of DIY DSAR

Built-in elsewhere? No.

The Eurobase answer

In code

Built in. Audit-trailed. EU-only.