Supabase trends and comparisons with Appwrite and PocketBase

AI-driven backend management

Supabase AI tooling uses an MCP server and specialized skills to automate monitoring. These agents operate in four defined roles: Health, Security, Performance, and Capacity. Health agents monitor API and Auth error rates, connection pressure, and instance state. Security agents analyze Security Advisor findings, RLS gaps, and Auth 4xx patterns. Performance agents track slow queries, lock waits, and long-running sessions. Capacity agents monitor request, error, storage, and connection growth against established baselines. The guide defines four roles, each with a prepared prompt and setup instructions for Claude Routines, Codex scheduled tasks, or Cursor Automations, and this ensures agents follow a specific scope. Each prompt scopes the agent to a specific job and routes findings through existing integrations like Slack or Linear. The query_logs tool provides structured access to logs for API, Auth, Storage, Edge Functions, and Postgres, which allows an agent to reach any data you would debug with a SQL query against your instance.

Database engines and deployment models

Teams choosing between Appwrite and PocketBase must evaluate the database engine. Supabase uses PostgreSQL. Appwrite uses MariaDB, while PocketBase uses SQLite. PocketBase delivers a single executable file that contains an embedded SQLite database with realtime subscriptions, which allows it to handle 10,000 or more concurrent WebSocket connections on a $4 VPS. You should evaluate if the single-binary simplicity of PocketBase meets your scale needs. However, SQLite has a single-writer limitation that prevents horizontal scaling for write-heavy collaborative tools. Appwrite provides a document model and has a first-class Flutter SDK, which makes it suitable for mobile developers. For self-hosters, Supabase changed the default API gateway from Kong to Envoy in August 2026. This setup provides more feature breadth such as messaging, while Supabase focuses on database, auth, storage, and functions. The Envoy API gateway configuration translates opaque sb_publishable_* and sb_secret_* keys into internal JWTs and manages routing through versioned YAML files located under the volumes/api/envoy/ directory to maintain configuration as code. Will the transition from Kong to Envoy impact existing custom routes in all self-hosted environments?

Predictable pricing and specialized storage

Pricing models determine the total cost of ownership. Supabase Pro costs $25 per month and includes 100,000 monthly active users, $10 in compute credits, 250 GB of egress, and 100 GB of file storage. Additional users cost $0.00325 per MAU. This plan also includes 250 GB of cached egress and daily backups stored for 7 days. The Supabase Free tier includes 50,000 monthly active users and 500 MB of database storage. The Team plan starts at $599 per month and includes SSO, ISO 27001 compliance, 28-day log retention, and 14-day automatic backups. Supabase Enterprise provides a private VPC and regional replication. PocketBase is self-hosted only and has no per-user fees. PocketBase is a lightweight, open-source backend delivered as a single executable file with SQLite, auth, file storage, and realtime, but its documentation carries an explicit disclaimer that it is not recommended for production-critical applications before reaching v1.0.0. Supabase also introduced specialized storage for analytical workloads. Vector Buckets use Amazon S3 Vectors for embeddings in public alpha. Specialized storage buckets built on Apache Iceberg provide columnar storage while maintaining compatibility with the Postgres interface.