ReachInbox vs Twenty

Twenty releases through a rapid tag train, often several patch tags in a day, each carrying a single commit. The 2.37.x line is four consecutive server fixes: three performance repairs to message import, full-sync delete diffing and the field-metadata query path, followed by an S3 socket leak that had been hard-failing workspace creation — 101 users at sign-up and roughly 80 more at activation over thirty hours. Beneath them, the paired 2.37.0 server and SDK releases carry the real feature load: breaking dependency and workflow changes, batched direct upload for application files, an editable object default layout, and usage limits modelled as an entity with API rate limiting driven from them.

The direction was set by the ORM v2 migration and the 2.35.0 SDK release, and this run is the bill arriving — the paths ORM v2 made hot are being optimised one at a time. What distinguishes the notes is how much evidence each fix carries: a production CPU profile attributing 29% of worker time to jsdom, a benchmark where 1.14M rows go from not finishing in 60 seconds to 1.5, a 1.2GB per-pod cache that a projection was supposed to shed. The app-platform thread continues underneath, extending the marketplace permission primitives with usage limits and per-layer writability.

Expect message sync to keep absorbing optimisation work, and the usage-limit entity to grow the admin-facing surfaces that make a configured limit visible and adjustable rather than only enforceable.