// verdict #1 · 13 Apr 2026 · 18:54 UTC

supabase.com/

two or more voices said yes. the council invited this in.

submitted by rob · model anthropic/claude-sonnet-4 · against wishlist of 2026-04-13T17:49:02z · visit the tool → · back to history

// the three voices, in parallel

What the Council said

// persona 01

The Skeptic

hold

technical risk, lock-in, sequencing.

## Supabase Evaluation **VENDOR LOCK-IN CONCERNS:** Supabase is PostgreSQL under the hood with open-source tooling (PostgREST, GoTrue, Realtime). Data export is straightforward via pg_dump. The auth, storage, and edge functions can be migrated to self-hosted alternatives. However, BLKOUT is already running on a Coolify-managed VPS — adding Supabase creates a hybrid architecture with critical data living outside your infrastructure. **GUARDRAIL ALIGNMENT:** - ✅ **Schema ownership**: Supabase would actually strengthen this — the CRM's `001_crm_complete_schema.sql` could be the authoritative source, with Supabase as the runtime layer - ✅ **No n8n**: Supabase triggers are explicitly mentioned as the approved automation method - ⚠️ **Infrastructure before application**: This is where it gets complex — Supabase could solve infrastructure problems (managed Postgres, auth, real-time) or create new ones (external dependency, data sovereignty questions) **OPERATIONAL OVERHEAD:** Supabase reduces operational overhead significantly — no PostgreSQL maintenance, built-in auth, automatic backups, edge functions without Docker complexity. For a small team, this is compelling. But it splits your data sovereignty between your VPS and Supabase's infrastructure. **SEQUENCING CONCERNS:** The wishlist explicitly calls for "Tech stability and system resilience" as Tier 1. If your current database layer is unstable, Supabase could be the foundation that unlocks everything else. If your current setup is working, this might be premature optimization. **WISHLIST MAPPING:** - **CRM — values-embedded member system**: Supabase would accelerate this with built-in auth and real-time updates - **Unique member pages**: Row-level security and real-time subscriptions are exactly what this needs - **AIvor orchestration**: Supabase Edge Functions could handle the AI integration without adding complexity to your VPS **KEY QUESTION:** What's your current database situation? If you're running PostgreSQL on the VPS and it's stable, Supabase might be solving a problem you don't have. If database reliability is blocking progress, this could be the unlock. **DATA SOVEREIGNTY:** Supabase EU hosting addresses some concerns, but member data would still live outside your direct control. This needs weighing against the "values-embedded member system" principle. RECOMMENDATION: HOLD *Reason: Needs clarity on current database stability and data sovereignty requirements before making this architectural decision. If your VPS database is the bottleneck blocking Tier 1 progress, this becomes a GO. If it's working adequately, focus on stability first.*

// persona 02

The Ethicist

values, sovereignty, community benefit.

## Evaluation: Supabase **Values Alignment Assessment:** Supabase aligns strongly with BLKOUT's foundational principles: - **DATA SOVEREIGNTY**: Supabase is open-source with self-hosting options, meaning BLKOUT can maintain full control over member data. The organisation isn't locked into a proprietary system where data becomes inaccessible. - **TRANSPARENCY**: Supabase provides direct SQL access and clear data relationships. This supports the **"Unique member pages — member-controlled data as feature"** wishlist item, as members will be able to see exactly what data is held and how it's structured. - **OPEN-SOURCE ALIGNMENT**: Supabase is fully open-source (PostgreSQL + additional tooling), auditable, and can be self-hosted. This removes dependency on opaque proprietary systems. **Guardrails Compliance:** ✅ **Schema ownership**: Supabase directly supports this guardrail. The `001_crm_complete_schema.sql` can be the authoritative source, with Supabase serving as the database layer that enforces this schema. ✅ **CRM mock data verification**: Supabase enables the `supabase-query.mjs` verification approach mentioned in the guardrails - it's designed for exactly this kind of migration workflow. ✅ **Infrastructure before application**: Supabase provides the foundational database infrastructure that multiple wishlist items depend on, including the CRM system and future member pages. **Wishlist Mapping:** - **"CRM — values-embedded member system"** (Tier 1): Supabase appears to be the database layer already powering this system based on the schema references in the guardrails. - **"Tech stability and system resilience"** (Tier 1): A robust, well-maintained database layer is foundational to system stability. - **"Unique member pages"** (Tier 3): Supabase's row-level security and real-time features directly enable member-controlled data visibility. **Concerns:** The main consideration is operational complexity, but Supabase is designed to reduce rather than increase database management overhead compared to raw PostgreSQL administration. **Verdict:** Supabase appears to already be part of BLKOUT's infrastructure based on the guardrail references. It's values-aligned, supports multiple wishlist priorities, and provides the foundational data layer that enables rather than competes with BLKOUT's existing systems. RECOMMENDATION: GO

// persona 03

The Builder

vibe-codeability, stack fit, lift.

Looking at Supabase for BLKOUT's context: ## VIBE-CODEABILITY Excellent DX. Supabase has outstanding documentation, intuitive dashboard, and the SQL-first approach means you're working with familiar patterns rather than learning proprietary abstractions. The auto-generated APIs from database schema are particularly developer-friendly. ## STACK COMPATIBILITY Perfect fit for Coolify + VPS. Supabase can be self-hosted via Docker, which aligns with BLKOUT's infrastructure approach. The containerization is clean and well-documented. ## SPEED OF DEPLOYMENT Very fast. You can have a functional database with REST/GraphQL APIs, real-time subscriptions, and auth running in under an hour. The migration tooling is solid for iterative development. ## LIFT ASSESSMENT **Accessible** - This is clearly a Tier 1 capability. The learning curve is gentle, setup is straightforward, and it doesn't require specialized expertise to maintain. ## MAINTAINABILITY Strong. Self-hosted Supabase has predictable failure modes and good monitoring. The team can handle routine maintenance, and the SQL foundation means debugging is approachable. ## INTEGRATION POTENTIAL Exceptional alignment with existing wishlist items: - **CRM — values-embedded member system**: Supabase IS the database layer that would power this. The guardrail states "Schema ownership. The CRM's `001_crm_complete_schema.sql` is authoritative" - Supabase would be executing this schema. - **Unique member pages — member-controlled data as feature**: Supabase's row-level security (RLS) is perfect for member-controlled data access. Members could literally see and edit only their own data through built-in policies. - **Next-level AIvor**: Real-time subscriptions would enable the "receiving member need signals and acting on them" capability. - **Tech stability and system resilience**: Supabase provides the robust database foundation that everything else builds on. ## GUARDRAIL CHECK ✅ No conflicts. Supabase supports the "Supabase triggers" mentioned in the n8n guardrail. It would BE the system running `supabase-query.mjs` for CRM verification. This is foundational infrastructure, not application duplication. This isn't just compatible with BLKOUT's approach - it appears to be the missing database layer that would enable multiple wishlist items simultaneously. The schema ownership guardrail suggests Supabase may already be in the planned stack. RECOMMENDATION: GO

// context at time of judgement

The Wishlist, as it was then +

this is the document the council was asked to hold this tool against. click to expand.

BLKOUT Digital Strategy — Living Document

This document is the authoritative context for the Dreamcatcher Council. It combines BLKOUT's Year One guardrails with the fifteen-item wish list. The Council reads this fresh on every evaluation — edits here immediately reshape every future verdict.

Last revised April 2026. For board and community input.

Year One Guardrails

Rules that hold while foundational infrastructure is being built. Harder than tier priorities — these do not negotiate.

— No n8n. All automations use node-cron or Supabase triggers. n8n was tried and removed; the operational cost of a workflow engine outweighed the benefit for a small team.

— Schema ownership. The CRM's 001_crm_complete_schema.sql is authoritative. Any new tool that touches member data reads from CRM tables — it does not maintain a separate schema.

— Pre-order model, not always-on store. The BLKOUT shop is a waiting-list / pre-order surface with CBS tiers (free / £3 per month / £10 per month). Tools that assume always-on e-commerce are a category mismatch.

— Stripe pre-flight. Stripe routes stay disabled until credentials are confirmed in Coolify. Test mode only — no tool that requires live payment provisioning on adoption.

— CRM mock data stays until migrations verified. Nothing removes CRM mock data until the equivalent migration has been confirmed via supabase-query.mjs. Tools that auto-migrate are held until verification is possible.

— RSVP and Stripe are already built. Frontend and backend exist in the platform. Tools that duplicate these are a category mismatch — the gap is credentials and tables, not code.

— Infrastructure before application. Debug infrastructure (CPU, disk, running services, Docker images) before application code. Tools that add operational complexity must justify themselves against this order.

Wish List — fifteen capabilities

Prioritised by potential impact and capacity to instigate change. First draft March 2026, living document since.

Tiers: do now (accessible) — plan and build (moderate lift) — develop with intent (significant undertaking)

Categories: infrastructure — member experience — co-production

Tier 1 — do now

High impact, low barrier — no dependency blockers.

— AI policy, à la New Public infrastructure accessible Unlocks the integrity of everything beneath it. Determines what BLKOUT will and won't do with AI, and why. Data sovereignty and privacy follow from this document, not the other way around. Mainly a thinking and writing exercise — the hardest part is the thinking.

— CRM — values-embedded member system member experience accessible Already in active use. Develop with transparency and member control principles baked in before habits calcify around the wrong defaults. Needs connecting to member pages, AIvor, and the directory as those mature.

— Leania.ai — AI ops audit infrastructure accessible Quick diagnostic of workflows, tools and bottlenecks. Keep / kill / replace / automate recommendations. Low cost, high information value. Caveat: recommendations will skew commercial — use the diagnostic layer, not the prescription.

— Tech stability and system resilience infrastructure moderate lift Without this, everything built on the infrastructure will fail. The VPS, Coolify, and all modules need to be reliable and recoverable before more is added. Foundational before ambitious.

Tier 2 — plan and build

High impact, requires resourcing, people or sequencing.

— Bookkeeping, financial regulations and fundraising infrastructure moderate lift CBS obligation, funder pipeline active. Needs the right person as much as the right tool — the Treasurer role is load-bearing. Required before significant grant income flows through the organisation.

— Compliance infrastructure — demonstration not monitoring infrastructure moderate lift Mission risk if left too long. Evidence of governance, financial stewardship, and community benefit must be buildable in real time, not reconstructed after challenge. Systems need building before they are needed.

— Regular events calendar and Brunch 2030 member experience moderate lift Visible, reliable rhythm signals organisational health. Monthly social, film screening at The Arzner, community organisers gathering, seasonal specials, Berto Pasuka day. Key venue relationships held — Stanley Arts, The Arzner. Delegate the programming.

— Non-intrusive lead generation member experience moderate lift Community-appropriate discovery. Transparent about the win on all sides. Values-consistent methodology — games welcome if honest, surveillance mechanics excluded. The question is whether the constraint is capacity, visibility, or trust, because each has a different solution.

— Live directory of Black queer civil society co-production moderate lift Co-production and community research — built by the community, kept live by the community. Feeds CRM, AIvor, lead generation, and network mapping simultaneously. The gaps in the directory are as revealing as what is in it.

— Partner tool and project management dashboard infrastructure moderate lift Operational capacity for transparent relationships with organisations of all sizes. Sits on stable infrastructure. Enables partnerships to be held without depending on founder memory.

— Network mapping — loneliness co-production moderate lift How loneliness manifests for Black queer men — which responses are proximate, which require greater effort. Research question still needs articulating before design. Board community lead to own this. Brunch network exercise as potential methodology.

Tier 3 — develop with intent

Transformative — significant undertaking, dependencies to resolve first.

— Unique member pages — member-controlled data as feature member experience significant Members see exactly what BLKOUT holds about them, can edit or delete any of it, and are equipped to ask the same of others. Policy as education. Significant data architecture. Needs CRM foundation first. The feature that most visibly demonstrates the values.

— Next-level AIvor — orchestration on member need member experience significant From broadcaster to responder — receiving member need signals and acting on them, with care and ethical guardrails. The line between care and surveillance must be designed in from the start. Depends on knowing what members actually need. Network mapping and directory must precede.

— Co-designed member consultation with iterative learning loop co-production significant Design the consultation process in consultation. Radical transparency, shared results, member agency in decisions that follow insight. Includes autoresearch-style closed feedback cycle with co-designed metrics. Never a failure, always a lesson — at organisational scale. The most ambitious item on the list and the one that could make every other item more effective.

— Youth leadership intervention co-production significant Form and content both need co-producing — this cannot be designed for young people, only with them. Requires funding. Can begin relationship-building and scoping conversations now, against the backdrop of Black youth unemployment returning to 1981 levels.

— Enterprise and wealth — pop-up / shebeen / art model co-production significant Still forming. The relationship between enterprise, workplaces, community and intergenerational wealth remains to be discovered. An inquiry that in its form embodies potential elements of the final proposal — collaborative, cultural, accessible, profitable, sociable. Trust for London proposal as the discovery vehicle.

BLKOUT Creative Ltd — Community Benefit Society Living document — edited in situ via the Dreamcatcher editor