Eurobase
Sign in Get started

Documentation

A guided tour of Eurobase through the eyes of a real project.

Meet Alex, a full-stack developer building LexVault — a document management SaaS for European law firms. Alex's clients handle sensitive legal documents and need rock-solid GDPR compliance with zero US cloud exposure.

This guide follows Alex from first sign-up to a fully connected application. Each chapter matches a section of the Eurobase console, so you can follow along with your own project.

Estimated read time: ~15 minutes. Every feature is covered — skip ahead with the table of contents if you're looking for something specific.

Start with Chapter 1: Signing Up →

All chapters

  1. 1. Signing Up Alex has heard about Eurobase and navigates to the login page.
  2. 2. Creating Your First Project Alex is signed in and ready to set up LexVault's backend.
  3. 3. The Project Dashboard LexVault is created. Alex lands on the project overview.
  4. 4. Building the Database Alex needs a clients table for LexVault's law firm customers.
  5. 5. File Storage Alex needs to store legal documents that clients upload.
  6. 6. Authentication Setup Alex needs to let law firm employees sign into LexVault securely.
  7. 7. Rate Limits LexVault is about to launch publicly. Alex wants safeguards so a runaway script can't burn through the project's email budget or hammer the auth endpoints.
  8. 8. Custom SMTP LexVault grows past the platform email cap. Alex's signups start hitting the 2-emails-per-hour ceiling. He plugs in the firm's own SMTP provider and the…
  9. 9. Managing End Users A law firm onboards new employees. Alex needs to manage their accounts.
  10. 10. Exploring the API Alex wants to see every API endpoint available for the LexVault tables.
  11. 11. Webhooks Alex wants LexVault to be notified whenever a new client record is created.
  12. 12. Row-Level Security Alex needs each law firm employee to only see their own cases.
  13. 13. Vault (Secrets) Alex needs to store API keys for Mollie payments and Twilio SMS securely.
  14. 14. Scheduled Jobs Alex needs to clean up expired sessions and send weekly reports automatically.
  15. 15. Edge Functions Alex needs to process a payment webhook and update an order — this requires custom server-side logic beyond SQL.
  16. 16. Monitoring with Logs Alex notices slow responses and wants to investigate API traffic.
  17. 17. Compliance, Audit Log & DSAR Alex's client asks for proof that their data stays in the EU and a trail of who changed what — and a user emails LexVault asking "what do you have on…
  18. 18. Project Settings Alex needs to rotate an API key after an intern accidentally committed it.
  19. 19. Team Collaboration Alex wants to give a colleague access to the project without sharing API keys.
  20. 20. CLI Tool Alex wants to manage projects, run queries, and test RLS policies from the terminal.
  21. 21. Schema Migrations Alex wants schema changes that are versioned, reviewable, and repeatable across environments.
  22. 22. Connecting Your IDE Alex wants their AI coding assistant to understand the LexVault schema.
  23. 23. MCP Server Alex wants their AI assistant to actually do things in LexVault — list users, run a SELECT, rotate a Vault secret — not just read schema docs.
  24. 24. Your Account Alex wants to set a display name and update their password.
  25. 25. Direct Postgres connection (Team) When the SDK / REST / edge-functions / SQL editor / MCP aren't enough — because your stack expects a raw postgres:// URL.
  26. 26. Team tier — dedicated Postgres, backups, snapshots Alex's first pilot law firm signs on. LexVault needs production isolation, daily backups, and a way to safely try schema changes without holding their…
  27. 27. Organizations & SSO (OIDC) Alex hires Bea. She needs her own login for LexVault's projects — no shared passwords, no forwarded API keys.
  28. 28. German legal-tech retention (Legal Team) Per-prefix WORM policies and row/object-scoped retention holds for tenants subject to §50 BRAO, §257 HGB, or §147 AO.
  29. What's Next Alex has a fully configured backend. Time to build LexVault's frontend.