Jellyfin vs Teable

Teable ships multiple times a day, and nearly every build in this window touches one of two systems: BYODB health handling and the computed field engine. BYODB now reports read-only, unreachable, degraded, and recovered states with in-app notifications and remediation guidance, returns a 409 on writes to a read-only database, and pauses computed tasks until recovery. The computed field work is a long list of reliability fixes — self-linked tables, deleted source fields, resumable lookup backfills on large tables, and an end to retry storms on unrecoverable failures. Admin observability tracks alongside it, with a task-level queue browser and consolidated anomaly reporting.

This is what a product looks like when it lets customers point it at their own database and then has to live with the consequences. The direction is not new features but making the failure modes of someone else's Postgres legible and recoverable — classify the health state, stop retrying what cannot succeed, resume what was interrupted, and give admins a queue view that survives an incident like a full disk. The permissions and collaborator work in the newest build is the first sign of attention moving back toward the collaboration surface.

Expect the admin recovery tooling to keep expanding toward bulk operator actions, since consolidating anomalies for bulk recovery was already called out as the goal. Computed field work should taper as the reliability backlog clears, with space and permission features taking more of each release.