Cloudflare Basin: a guide to the serverless data platform
Cloudflare Basin went GA on 1 October 2026. What its pipelines, Iceberg catalogue and SQL engine do, how to set it up, and the limits to plan for.
Monitoring coverage is about the gaps: the service with no alerts, the cron job nobody watches, the connection pool that fills up quietly until it doesn't. The outages that take hours to find usually hide in one of them.
These guides are for engineers running an app on a managed platform who need to know what to watch and how to wire it up. Each one takes a real stack, such as Supabase, Convex, FastAPI on Railway or Django on Render, and walks through health checks, structured logs, metrics, traces and the alerts worth having on day one. They start with the platform's own tools and show where a third-party tool adds something. You finish each guide knowing which signals you collect, which you are missing and what to add next.
How Polylane works on these platforms: Supabase, Cloudflare, Convex, Render and Railway.
Cloudflare Basin went GA on 1 October 2026. What its pipelines, Iceberg catalogue and SQL engine do, how to set it up, and the limits to plan for.
Monitor a Convex app in production: use the Health page and CLI, stream logs to Axiom or Datadog, report exceptions to Sentry, and alert on failures.
Monitor a Django app on Render: JSON logs, a real health check, failure alerts, log and metrics streams, OpenTelemetry under Gunicorn and Celery checks.
Monitor a Supabase app in production: scrape the Metrics API into Prometheus, drain logs, run SQL health checks, trace requests and alert on what matters.
Monitor a vibe-coded app in production: surface swallowed errors, add a health route, tag deploys, watch cron jobs and alert on what users feel first.
Set up health checks, JSON logs, OpenTelemetry traces, monitors and crash alerts for a FastAPI service on Railway, with the commands and config to copy.