March 2026 Summaries

Supabase, an infrastructure provider for developers, has faced multiple regional network blocks due to regulatory actions by governments and ISPs, which often target entire domains or IP ranges due to the actions of a single abusive tenant on multi-tenant platforms. These blocks, occurring in the UAE, Yemen, and India, were resolved through engagement with local authorities and sometimes required direct intervention by customers. The company highlights the challenges of operating a global platform amid local regulatory environments and emphasizes the importance of establishing proactive communication with regulators to prevent and swiftly address such issues. While workarounds such as VPNs can temporarily circumvent blocks, Supabase continues to refine its abuse response procedures and communication channels to minimize disruptions. They also acknowledge the role of the Public Suffix List in mitigating some risks, though it hasn't completely prevented blocks. Supabase is committed to maintaining openness for developers while ensuring compliance with local laws, recognizing the critical role of customer relationships in navigating these regulatory challenges.

Stripe Projects provides a streamlined, deterministic workflow for provisioning infrastructure for AI agents and humans, facilitating account setup, resource provisioning, and credential delivery with a single command. This integration, co-designed with Stripe, ensures that the process is repeatable and consistent, whether executed by a human or an AI agent. Users maintain full control over their Supabase accounts, allowing them to access the dashboard and manage their data independently, with the assurance that their setups are neither proxied nor white-labeled. The platform supports credential rotation, keeping stored secrets updated automatically in Stripe Projects, and includes a comprehensive suite of features such as a Postgres database, Auth, Storage, Edge Functions, and Realtime. The provisioned credentials are synchronized to local environments and stored in Stripe Projects for agent access, with feedback mechanisms available via Discord and GitHub for ongoing development and support.

Supabase has introduced Log Drains for its Pro tier, enabling users to send Supabase logs to their own logging backends, thereby integrating Supabase logs with existing debugging tools and eliminating the need for context switching during incident resolution. This feature provides comprehensive log visibility across various infrastructure layers, such as Postgres, API Gateway, Auth, Storage, and Edge Functions, which is not typically offered by other platforms. Users can configure log destinations like Sentry, Grafana Loki, Datadog, AWS S3, Axiom, or any generic HTTP endpoint, allowing them to correlate logs from different layers in a single dashboard for better observability and incident management. The log drains are particularly useful for growing startups, AI application developers, platform teams managing multiple projects, and organizations with compliance requirements, as they offer centralized logging, real-time search capabilities, and long-term log retention at economical costs. The pricing for using log drains is set at $10 per drain per project, with additional costs per million events and gigabytes of data egress.

Supabase Storage has undergone significant updates aimed at enhancing performance, security, and reliability, which are now active across all regions. The improvements include a complete overhaul of the object listing system, replacing the old prefixes table with a skip-scan algorithm that enhances write performance and accelerates deep pagination by up to 14.8 times on large datasets. Security has been bolstered by closing path traversal vulnerabilities and introducing measures to prevent accidental deletes via direct SQL. Reliability enhancements include idempotent migrations and fixes for issues like TUS zombie locks and orphan object scanning. Additionally, observability has been improved with the adoption of OpenTelemetry for metrics, and various bug fixes have been implemented to address issues such as URL formatting and S3 response handling. No code changes are required for users to benefit from these updates, although switching to the listV2 endpoint is recommended for further performance gains.