October 2026 Summaries

Serverless Postgres services such as Neon, Supabase, and Prisma Postgres retain standard PostgreSQL capabilities, including SQL, connection strings, ORMs, and database tools, while adding features such as compute suspension, connection pooling, branching, and serverless or edge-oriented access. Their pooled transaction-mode connections can limit session-dependent features, so direct connections are generally recommended for migrations, dumps, replication, and persistent session state. Neon emphasizes copy-on-write database branches and scale-to-zero compute, Supabase combines Postgres with Auth, a Data API, row-level security, storage, and preview environments, and Prisma Postgres targets TypeScript applications with pooled TCP access and HTTP or WebSocket options for runtimes without TCP support. None of these systems automatically performs AI media processing when rows are inserted; applications requiring video extraction, transcription, embeddings, or indexing typically need external compute services and explicit triggers or calls. Pixeltable is presented as a complementary multimodal data table rather than a Postgres host, allowing media-derived computations such as audio extraction and transcription to be defined as schema columns that run on insertion. Convex is also described as an adjacent but non-SQL reactive JavaScript backend, while a cited benchmark suggests Pixeltable requires less application and infrastructure code for one video-intelligence workload, without positioning it as a general database-host ranking.

Pixeltable Cloud, currently in limited beta, lets users deploy the same `app.py` used locally to a hosted database and separate HTTP service runtime, configured through a Pixeltable project entry in `pixeltable.toml` or `pyproject.toml`. Deployment generally proceeds by updating the database and project files with `pxt db update`, applying table schema changes with `pxt schema update`, and starting or refreshing routes with `pxt service update`; the database handles catalogs, table operations, and indexing, while the service handles FastAPI routes. Configuration controls included project files, Python version, dependencies, system packages, database resources, and local media-cache disk, while source-only changes upload quickly and dependency changes trigger slower image rebuilds. Cloud databases provide a default home storage bucket for media, with options for local-to-cloud transfers or external S3, GCS, and Azure destinations. Provider credentials are stored as organization or database secrets and require process restarts to take effect, whereas Pixeltable API keys authenticate CLI use, backends, and hosted service requests, with optional scoped grants in preview. Operational commands support status checks, logs, restarts, stops, image rebuilds, and deletion, and the platform emphasizes keeping service URLs dynamic, retaining API keys on servers rather than browsers, and using the same application file across local and hosted environments.