Supabase · Keycloak · EU-Hosting
SupabaseAgency for Postgres backends
Auth, realtime, storage and edge functions on Postgres – set up production-ready and maintained for the long run.
Supabase Agency – happycoding
We are a Berlin-based agency focused on scalable web and app architectures using Supabase as a data and authentication backend. Our goal: high-performance platforms that connect to your existing systems and grow with your requirements. With Supabase, we build data-driven products that react in real time: customer portals, business software, dashboards and SaaS platforms.
Performance in real time: Supabase combines PostgreSQL, authentication, storage, and edge functions in a cloud-native architecture. We use this for applications with live data: changes appear instantly for every user via Realtime, whether in a chat, a dashboard or a shared document. The result: less custom backend code and shorter development cycles.
Integration & Security: We connect Supabase with CMS solutions such as Sanity or WordPress Headless, commerce platforms like MedusaJS, and analytics tools via REST or GraphQL. Row Level Security defines directly in the database who may see and change which data, so data only goes where it is meant to.








































































Typical Supabase projects
Supabase fits applications where people sign in, work with data together and only see what they are allowed to see.
Real-time apps: chat and collaboration
Messages, comments and status changes appear for everyone involved at once, without anyone reloading the page. Supabase Realtime pushes the changes and shows who is online right now.
Customer portal with Supabase and Keycloak
Your customers find orders, invoices and documents in one place and handle requests themselves instead of calling. Keycloak handles sign-in, Supabase separates each customer company’s data directly in the database.
Business software for SMEs
Orders, scheduling or inventory no longer live in scattered spreadsheets but in one web app for the whole team. Each role only sees its own data, and everyone works on the same version at the same time.
Intranet with single sign-on
Your employees sign in with their Microsoft account and find news, documents and workflows in one place. Which department may see what is governed by permissions in the database instead of scattered folder shares.
API portal for partners
Retailers, suppliers or customers access exactly the data you release to them through a documented API. Supabase provides the database, sign-in and permissions per partner; we build key management and documentation on top.
AI assistant with Supabase and pgvector
Your team asks questions about manuals, contracts or tickets and gets answers with sources. The vectors of your documents sit in Supabase next to your business data, under the same access rules.
Your project is not on the list? In a 30-minute intro call we clarify the operating model, sign-in and cost range.
Book an intro callRunning Supabase in line with the GDPR: three options
The region alone is not enough: Supabase itself says choosing a region is not proof of compliance. What counts is the contract, the data flows and operations. These are the three options we implement.
| Criterion | Supabase Cloud (Frankfurt) | Cloud plus Keycloak in Germany | Fully self-hosted (Hetzner) |
|---|---|---|---|
| Where the data lives | Database, sign-in and files in Frankfurt; edge functions and CDN cache distributed worldwide by default | Passwords, MFA and the user directory in Keycloak on your own server; Supabase still keeps each user’s ID, email and provider details in Frankfurt | The entire data layer on Hetzner servers in Germany |
| Contracting party | Supabase Pte. Ltd. (Singapore), DPA with EU standard contractual clauses; sub-processors include Supabase, Inc. and AWS (USA) | As with Cloud, plus the server host | Only the server host |
| Residual risk | Possible access under US law (CLOUD Act) belongs in your risk assessment | As with Cloud for application data; credentials stay outside | No third-country transfer in the data layer; check email delivery, CDN and front-end hosting separately |
| Operating effort | Low: daily backups included, point-in-time recovery at extra cost | Plus running Keycloak | Full: backups, updates, monitoring; no branching, no point-in-time recovery, community support only |
| Fits when | you want to start fast and your data protection officer accepts the route via standard contractual clauses | a B2B portal needs single sign-on and credentials must stay under your control | your requirement is “no third country” for the data layer and there is budget for operations |
Where the data lives
- Supabase Cloud (Frankfurt)
- Database, sign-in and files in Frankfurt; edge functions and CDN cache distributed worldwide by default
- Cloud plus Keycloak in Germany
- Passwords, MFA and the user directory in Keycloak on your own server; Supabase still keeps each user’s ID, email and provider details in Frankfurt
- Fully self-hosted (Hetzner)
- The entire data layer on Hetzner servers in Germany
Contracting party
- Supabase Cloud (Frankfurt)
- Supabase Pte. Ltd. (Singapore), DPA with EU standard contractual clauses; sub-processors include Supabase, Inc. and AWS (USA)
- Cloud plus Keycloak in Germany
- As with Cloud, plus the server host
- Fully self-hosted (Hetzner)
- Only the server host
Residual risk
- Supabase Cloud (Frankfurt)
- Possible access under US law (CLOUD Act) belongs in your risk assessment
- Cloud plus Keycloak in Germany
- As with Cloud for application data; credentials stay outside
- Fully self-hosted (Hetzner)
- No third-country transfer in the data layer; check email delivery, CDN and front-end hosting separately
Operating effort
- Supabase Cloud (Frankfurt)
- Low: daily backups included, point-in-time recovery at extra cost
- Cloud plus Keycloak in Germany
- Plus running Keycloak
- Fully self-hosted (Hetzner)
- Full: backups, updates, monitoring; no branching, no point-in-time recovery, community support only
Fits when
- Supabase Cloud (Frankfurt)
- you want to start fast and your data protection officer accepts the route via standard contractual clauses
- Cloud plus Keycloak in Germany
- a B2B portal needs single sign-on and credentials must stay under your control
- Fully self-hosted (Hetzner)
- your requirement is “no third country” for the data layer and there is budget for operations
Not legal advice: we provide the technical documentation with data flows, sub-processors and the permission model for your data protection officer. Which option fits your requirements is what we clarify in a Supabase intro call.

Supabase as a Scalable Backend for Modern Platforms

Working together with Next.js, Keycloak and Sanity
Services
We offer a full range of services around Supabase as the backend of your application – from initial concept to ongoing operations:
Concept & Architecture
Requirements analysis and workshops
Data modelling and API design
Authentication and user management
Technology and infrastructure consulting
Implementation
Supabase project setup
Database, Auth, Storage and Edge Functions.
API development with TypeScript
Frontend integration
Next.js, React or Vue.
Deployment and CI/CD
Hetzner, your infrastructure or Vercel.
Role and security logic
Via Row-Level Security.
Integration with your systems
SSO (Keycloak, Entra ID), ERP, CRM and PIM.
Operations
Monitoring and observability
Security audits and performance tuning
Data migration and backups
Maintenance and support
Analytics, tracking and AI features
Integrated into your application.
Security & compliance
Your customers trust you with sensitive data. We take that responsibility seriously.
Whether it's your data protection officer, your IT security team or a major customer's procurement: when security questions come up, you have solid answers. We build in data protection and security from day one and follow the principles of the Twelve-Factor App. That makes approvals and audits easier and gives you the technical foundation to meet requirements under GDPR, ISO 27001 or HIPAA.
Frameworks whose technical requirements we implement in our projects
- GDPR
- ISO 27001
- HIPAA
- NIS2
When Supabase fits – and when we advise against it
Definition
- Backend-as-a-service (BaaS)
- Backend-as-a-service provides ready-made building blocks such as a database, sign-in, file storage and APIs as a platform. Teams use it to build applications without developing the infrastructure themselves.
Supabase is an open-source backend on PostgreSQL: database, sign-in, real-time and file storage from one system, in the cloud or on your own servers. Explained in detail in What is Supabase?
| Criterion | Our pickSupabase | Firebase |
|---|---|---|
| Database | PostgreSQL (relational, SQL) | NoSQL (Firestore) |
| Open source / self-hosting | Yes – full data control, EU hosting possible | No, tied to Google Cloud |
| Vendor lock-in | Low (standard Postgres, clean export) | High |
| GDPR / EU operations | EU region selectable; contracting party Supabase Pte. Ltd. (Singapore), sub-processors in the USA; full data control only self-hosted | Tied to Google, no self-hosting |
| Pricing model | Free tier; Pro from about $25/month; self-hosted only infrastructure costs | Usage-based, hard to plan |
Database
- Supabase
- PostgreSQL (relational, SQL)
- Firebase
- NoSQL (Firestore)
Open source / self-hosting
- Supabase
- Yes – full data control, EU hosting possible
- Firebase
- No, tied to Google Cloud
Vendor lock-in
- Supabase
- Low (standard Postgres, clean export)
- Firebase
- High
GDPR / EU operations
- Supabase
- EU region selectable; contracting party Supabase Pte. Ltd. (Singapore), sub-processors in the USA; full data control only self-hosted
- Firebase
- Tied to Google, no self-hosting
Pricing model
- Supabase
- Free tier; Pro from about $25/month; self-hosted only infrastructure costs
- Firebase
- Usage-based, hard to plan
The full comparison is in Supabase or Firebase: the European perspective.
When we advise against it
- A pure content site without sign-in: a website without login does not need a backend. A headless CMS such as Sanity fits better.
- An app that mainly has to work offline: Supabase relies on a connection to the server. Other tools are stronger for offline-first.
- A requirement for Azure or Google Cloud, or a contractual SLA: hosted Supabase runs only on AWS, and an SLA is only available on the Enterprise plan.
Who works on your project
Our senior team in Berlin, from the first draft to production. You talk directly to the people who write your code.
Meet the teamFAQ
What you always wanted to know about Supabase