> ## Documentation Index
> Fetch the complete documentation index at: https://helloluciallc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supabase

<Note>
  Supabase is Lucia's data platform direction. Lucia Core development now uses Supabase for durable Stripe financial ledger truth, while some operational state still relies on Engine-side state files.
</Note>

***

## Current Role

Supabase is part of the Lucia stack for structured persistent data.

Current implemented Development use:

```text theme={"dark"}
Lucia Core development durable Stripe ledger
Project name: lucia-core-dev
Project ref: jgnxomyzqotnqsmlxlsz
```

Eval Labs Supabase remains separate and was not touched by this Lucia Core payment truth work.

***

## Current Reality

Some current runtime state is still file-backed in the Engine.

Examples include:

```text theme={"dark"}
guest state
maintenance inbox state
```

Durable Stripe movement truth is now implemented in Lucia Core Supabase Development:

```text theme={"dark"}
stripe_financial_records
stripe_financial_events
```

Current security posture:

```text theme={"dark"}
RLS enabled on both durable ledger tables
No anon read policies
No authenticated-user read policies
Engine uses service-role-only access
Admin never talks directly to Supabase
```

Engine Stripe ledger storage modes:

```text theme={"dark"}
file
dual
supabase
```

Current Render Engine Development configuration:

```text theme={"dark"}
SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY
LUCIA_STRIPE_FINANCIAL_LEDGER_STORE=dual
LUCIA_STRIPE_LEDGER_DURABLE_REQUIRED=true
```

Tested Development proof:

```text theme={"dark"}
Harper Quinn #29110012 completed a $500.00 Stripe sandbox checkout
Durable record/event were written
Engine restarted via Render
payment-status still returned known=true and financialTruthState=confirmed_paid
```

***

## Future Direction

Supabase should eventually own more durable operational data:

```text theme={"dark"}
bookings
guests
tasks
maintenance inbox
audit logs
operator actions
```

Payment policy truth remains future/deliberate:

```text theme={"dark"}
Durable Stripe movement truth = implemented
Durable property payment policy truth = not yet implemented
Property Payment Policy v0 = Admin-visible draft/read-only baseline only
```

***

## Migration Principle

Do not migrate data storage blindly.

Move to Supabase when:

```text theme={"dark"}
schema is clear
workflows are stable
audit requirements are known
UI behavior is validated
```

***

## Canon Rule

Docs must distinguish:

```text theme={"dark"}
current file-backed runtime
current durable ledger-backed runtime
future database-backed architecture
```

Do not collapse Lucia Core Supabase, Eval Labs Supabase, Admin rendering, and Engine service-role access into one vague "database" claim.

***

## See Also

* [Lucia Payment Truth Foundation](/lucia/system-architecture/lucia-payment-truth-foundation)
* [01 - Render](/lucia/infrastructure/render)
* [11 - Domains and Live Routing](/lucia/infrastructure/domains-and-live-routing)
* [02 - Task Creation and Routing](/lucia/operations/task-creation-and-routing)
* [01 - Maintenance Workflow](/lucia/operations/maintenance-workflow)