[benitav]

Inspired by #701

Our Neon guide looked quite "busy" (e.g. 4 callouts at the top), so I took the opportunity to have Claude test all steps and update anything that was outdated. I also added CLI instructions alongside the web UI instructions, for agents. The guide now follows our writing and style standards better.

While I was at it, I made similar improvements to the Supabase guide: added CLI instructions, removed outdated setup guidance, and moved our "PSAs" to a Troubleshooting section at the end, since they're now edge cases.

Claude did most of the testing and corrected the guides accordingly, with me testing the odd thing in the Neon and Supabase consoles.

Neon guide:

• Replaced the 4 callouts at the top with a short intro and a prerequisites list
• Added Web UI and CLI tabs to every setup step (Neon CLI + PowerSync CLI)
• Fixed the demo path and install steps, and switched to a direct (non-pooled) connection string
• Updated all steps for the current Neon Console (Better Auth, Data API, Logical Replication, Auth URL / JWKS URL)
• Called out that Grant public schema access is required and off by default
• Added a note that the Neon compute doesn't scale to zero while PowerSync is connected
• Removed outdated screenshots, a stray Vercel warning, and the time estimate

Supabase guide:

• Added Web UI and CLI tabs (Supabase CLI + PowerSync CLI) for the project, SQL, instance, connection, Supabase Auth, and Sync Streams steps
• Removed "Before You Start: Project Creation Settings": the default settings work, because the schema SQL grants access and enables RLS
• Updated the Connect steps for Supabase's current Connect dialog
• New Troubleshooting section: upload errors (42501), WAL filling the disk on idle projects, and unused replication slots
• General cleanup: intro, architecture, headings, placeholders, image captions, and simpler key and email-confirmation notes

Shared snippets and other pages:

• New neon-enable-logical-replication.mdx snippet, also used on Source Database Setup
• Split the Supabase connection snippet into connection steps and a new supabase-auth-setup.mdx; the FlutterFlow guides and Source Database Connection import both, with no visible change apart from the updated Connect steps
• Deleted 5 outdated screenshots

Testing:

• Neon: end to end on a new project, using both the web UI and the CLI. The PowerSync instance replicated, accepted a Neon Auth token, and synced the demo app both ways
• Supabase: CLI path end to end on a throwaway project. Schema, role, and publication were created, a new instance was deployed with supabase: true, and a Supabase user's token was accepted. Not tested: the legacy JWT secret option and the framework demo apps
• Vale, pnpm check:links, and a local Mintlify render

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
powersync	🟢 Ready	View Preview	Oct 21, 2026, 1:16 PM

💡 Tip: Enable Automations to automatically generate PRs for you.