PostHog vs Supabase

Build vs Buy: Cookie Banner for React/Next.js

This technical guide compares building a custom cookie banner versus using a consent management platform (CMP) for React and Next.js applications. It argues teams should build their own banner only when requirements are narrow and the engineering team is prepared to maintain consent infrastructure over time. The article highlights key responsibilities of production consent systems — script gating, preference storage, withdrawal support, regional behaviour, and durable records — and presents c15t as a developer-first CMP that supports hosted, self-hosted, and browser-only deployments. Inth is named as a managed hosting provider for c15t. The guide stresses that script gating and backend persistence are critical when auditability and regulatory accountability (e.g., GDPR/UK rules) matter.

• The article recommends building a custom cookie banner only if requirements are narrow and the team is prepared to maintain the logic over time.
• c15t is described as a developer-first consent management platform that supports hosted, self-hosted, and browser-only deployments.
• Inth provides a managed hosted deployment option for c15t teams that do not want to operate the backend themselves.

Developer Builds AI Alt-Text Generator for WordPress

A developer built an AI-powered alt-text generator for WordPress to automate descriptive image alt text generation and reduce manual workload. The project evolved into a production-ready plugin with a stack including WordPress/PHP, JavaScript, Node.js, Render, Supabase, Stripe, and PostHog, plus an external AI vision service. Key engineering lessons cover clear telemetry semantics (job-level vs item-level events), deduplication strategies using stable PostHog insert IDs and event ownership, correlation IDs for cross-system tracing, privacy-by-default telemetry (strip PII and content), and controlled internal error taxonomies. The article emphasizes that reliability (authentication, billing, idempotent webhooks, privacy-safe analytics, observability) matters as much as the AI feature itself.

• The author built an AI alt-text generator as a WordPress plugin to automate descriptive alt text creation for images.
• Plugin capabilities include single-image generation, bulk processing of missing alt text, saving generated text into WordPress, usage/quota tracking, and user review before applying text.
• Architecture stack includes WordPress/PHP, JavaScript, Node.js backend, Render for hosting, Supabase for accounts/entitlements, Stripe for subscriptions, PostHog for analytics, and an AI vision service for image analysis.

Supabase is now available in Gemini Enterprise

Connect Supabase to Gemini Enterprise and query your Supabase projects with natural language, right inside the platform.

Build SaaS Apps with Claude Code, Clerk, and Supabase

This technical walkthrough guides product managers on how to build, secure, and monetize a full-stack B2B2C SaaS application using AI agents without writing code. Using a case study called AskOne—a live Q&A alternative to Slido—the tutorial details a universal, multi-step workflow. The process utilizes Anthropic's Claude Code to generate design layouts, establish design system tokens, and implement functional React components. The system integrates Clerk for user authentication and recurring subscription billing configuration, alongside Supabase as the backend database connected securely via Claude's Model Context Protocol (MCP) server framework.

• The author developed Grok Build for VS Code, achieving over 105,000 installations and 37,000 monthly active users (MAU).
• AI agents autonomously wrote 5,094 automated end-to-end integration and unit tests for the software in three months.
• The workflow utilizes a recommended B2B stack consisting of Next.js, Clerk, and Supabase.

Safely Drop All PostgreSQL Tables (2026)

A technical how-to describing safe methods to drop all tables in a PostgreSQL database. The article shows a one-command reset (DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT ...), explains PostgreSQL 15 default changes that revoke CREATE from PUBLIC and set public's owner to pg_database_owner (which can cause permission errors), and details Supabase-specific risks (Dropping public can remove Supabase-managed schemas and extensions). It gives variants to preserve extensions (reinstall extensions or drop tables only via a DO-block loop), recommends wrapping resets in transactions for local dev, and provides a production safety checklist: take backups, confirm connection, block connections, and restore from pg_dump/pg_restore rather than dropping schema in prod.

• DROP SCHEMA public CASCADE removes the public schema and all dependent objects (tables, views, sequences, functions, triggers).
• PostgreSQL 15 defaults: PUBLIC no longer has CREATE by default, and the owner of public is pg_database_owner, which can cause 'permission denied for schema public' after recreating the schema.
• On Supabase, DROP SCHEMA public CASCADE can cascade into Supabase-managed schemas (auth, storage, realtime, graphql) and break the project; use 'supabase db reset' for dev and restore from backups for production.