# Managed Postgres

Nizhal's provisioning uses ordinary DDL + triggers — no `wal_level = logical`, no replication slot, no superuser grants for logical decoding.

## Neon

```bash
DATABASE_URL="postgresql://..." nizhal migrate --config nizhal.config.js
pnpm --filter credit-ledger example:neon
```

`apps/credit-ledger/examples/neon-smoke.ts` runs against `NEON_URL`. Chaos suite accepts `NEON_URL` for managed-Postgres verification (`pnpm chaos`).

## RDS / Supabase / other managed PG

Requirements:

- CREATE TABLE / CREATE TRIGGER permissions on your schema
- Standard Postgres — not Aurora logical replication features

If you can run migrations, you can run Nizhal.

## Why this matters

WAL-tailing sync engines (Electric, Zero, etc.) often cannot run on managed tiers you do not control. Nizhal trades their hosted convenience for **cursor pull on any Postgres you already have**.