Integrations
Supabase
betaUse Supabase schema and project context as a source for product and engineering work — read-first, fail-closed on schema/RLS writes.
Supabase connects as a database context source for product and engineering work. HiveBase can use project metadata and schema shape so specs, tasks, and agents reason about your real tables and policies — not invented structure.
This is not a silent two-way real-time sync that makes HiveBase the system of record for schemas or RLS. Supabase remains authoritative for your database. Writes that change schema, policies, or functions only run on fail-closed, explicitly approved paths when those paths are live.
What you get
| Capability | Behavior |
|---|---|
| Schema-aware context | Eligible schema information enriches PRDs, specs, and coding/product tasks |
| Project grounding | Agents and operators see structure that matches production intent |
| Governed change | Any push of schema/RLS/function changes requires live certification + your approval model |
What we do not claim
- No silent two-way real-time sync of every schema and RLS change.
- No claim that HiveBase replaces the Supabase dashboard or migrations workflow.
- No automatic production DDL without approval boundaries.
- No “manage your entire database only inside HiveBase” promise.
Connect Supabase
Open Data Sources
In HiveBase, go to Settings → Integrations → Data Sources.
Connect Supabase
Select Supabase and complete authorization for the project(s) you intend to ground.
Confirm read access
Prefer least privilege: read schema/context first; enable write scopes only if you need governed push paths that are live for your workspace.
Writeback posture
Schema, RLS, and function writes are fail-closed until certified. When a write path is available, it follows the same receipts and approval rules as other outbound actions — see Trust & safety. Prefer migrations and Supabase-native workflows for production DDL; use HiveBase for context and coordination around that work.
FAQ
Does HiveBase auto-sync RLS policies both ways?
No. HiveBase can use schema/RLS context for intelligence. Bi-directional auto-sync of security policies is not the default posture and is not claimed as always-on real-time.
How does this help AI accuracy?
Agents plan against observed structure instead of inventing tables. That reduces structural hallucination in specs and coding tasks — still review before ship.
Can I push schema changes from HiveBase?
Only on live-certified, approval-gated paths. If a path is not certified, it stays fail-closed.
Disconnecting
From Settings → Integrations → Data Sources, disconnect Supabase to stop future schema/context refresh for that project connection. Existing Brain claims and task context keep history subject to workspace retention.