Postgres extensions, worker containers, object storage and TCP ports

Postgres extensions, enabled per project from the Topology tab: pgvector (vector search), pg_trgm, pgcrypto, uuid-ossp, unaccent, citext, btree_gin. Pierrr creates them for you with the privileges required, without ever widening your database's own.
Worker containers: a queue consumer or a scheduled job no longer needs to ship a pointless HTTP server just to be considered healthy. Pick the type when creating the container; no subdomain, no HTTP probe.
Managed object storage, S3-compatible: a dedicated instance per project, its bucket created up front, publicly reachable so your presigned URLs work. Credentials are injected like the database's and the cache's, in the STORAGE_* variables.
Per-container CPU and memory bounds, with a guaranteed share separate from the ceiling: the share is what protects a container from a hungry neighbour on the same machine.
Raw TCP ports published on the server's public address, single port or contiguous range, for protocols HTTP routing cannot serve. Available from the Starter plan.

Managed add-on volumes (Redis, object storage) are now included in project backups. They were missing, while the archive presented itself as complete.