LoginSign Up
← Back to all sparks
T

Teable

COLLAB
Velocity5.0

Open-source no-code database and Airtable alternative

teable.io ↗

A daily release train grinding on BYODB reliability and large-table performance.

byodbself-hostedadmin-toolingapp-builderperformancerelease-train
◆Current state
Teable ships a numbered release most days, and the current run is dominated by operational hardening rather than new surface. The recurring subject is bring-your-own-database: health statuses for read-only, unreachable and degraded connections, 409 conflicts on read-only writes, paused-and-resumed computed tasks, and tightened validation that now rejects private or internal network addresses. Alongside that sits a steady stream of large-table performance work — bulk deletes across tens of thousands of records, view duplication, lookup and cascade chains, field conversions.
◆Where it's heading
The centre of gravity is self-hosted and admin-operated deployments: the Admin Outbox anomaly tooling, bulk incident recovery, license checkout fixes and BYODB remediation guidance all serve an operator, not an end user. The App Builder is developing in parallel, picking up publishing metadata and an instance-wide control over whether platform-managed AI keys reach apps. The new 10-minute floor on scheduled automations is the first sign of the platform imposing cost discipline on its own execution surface.
◆Prediction
Expect the automation interval floor to be followed by further execution quotas or tiering, given it was introduced with existing configurations grandfathered in. BYODB looks close to feature-complete on health and recovery, so the next visible work is likelier on the App Builder.

◆Recent moves

  1. 1d ago

    Teable sets a 10-minute floor on scheduled automations

    Scheduled automations and email polling now require a minimum 10-minute interval for new or updated configurations, with existing ones grandfathered in. The rest is performance work on bulk deletes, view duplication and computed-field cascades — the same large-table reliability theme running through this train.

    View source ↗
  2. 2d ago

    Teable adds App Builder metadata and an instance-wide AI key control

    Published App Builder apps gain custom favicons, page titles and descriptions, automation script nodes get a 180-second ceiling, and admins can now stop platform-managed AI keys from being handed to apps. The AI key setting is the notable one — it lets operators force apps onto their own approved credentials.

    View source ↗
  3. 3d ago

    Teable reworks collaborator management and space row-count handling

    Space collaborators are grouped and paginated by person with Base-level permissions shown inline, and record-creation latency improves under high concurrency by reforming space row-count calculations. BYODB connection validation also tightened against internal network addresses.

    View source ↗
  4. 4d ago

    Teable adds BYODB health statuses and read-only conflict handling

    Explicit health statuses, notifications and remediation guidance for read-only, unreachable, degraded and recovered databases, with writes returning 409 and computed tasks pausing until recovery. This is the core of the BYODB reliability arc.

    View source ↗
  5. 4d ago

    Teable consolidates repeated database errors in the admin Outbox

    The Admin Outbox anomaly page now consolidates repeated database errors with changing details, making bulk recovery from incidents such as full disks practical. Operator-facing incident tooling rather than end-user capability.

    View source ↗
  6. 4d ago

    Teable fixes admin Outbox task counts and field naming conflicts

    Corrects inaccurate failed-task counts when underlying tasks no longer exist and prevents rare field naming conflicts from disrupting computed updates. Small corrections inside the same admin-reliability push.

    View source ↗