Releasesby GlyphSwitch Between App Endpoints in the Dashboard Playground
Deployed Serverless apps now include Testing > Playground in the app dashboard. Select an available endpoint, fill in its generated input form, and run a request without leaving the app. Multi-endpoint apps have one place to test their endpoints, using the existing Playground authentication and billing behavior. Open the guide
Also shipped Sep 9, 2026fal in September 2026 →
Configurable retention for system tables is in Beta
Account admins can now set an account-wide retention period from 30 to 3,650 days for supported system tables. See Configure system table data retention .
External secrets in Unity Catalog (Beta)
External secrets connect a Unity Catalog schema to AWS Secrets Manager. The secrets appear in Unity Catalog as read-only securable objects that you govern with Unity Catalog privileges. Databricks reads their values from AWS Secrets Manager on demand. See External secrets in Unity Catalog .
Celigo connector (Beta)
The Celigo connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests audit log events, such as create, update, and delete operations on resources, from Celigo (integrator.io) into Databricks. Authentication uses a Celigo integrator.io API token.
Anysphere Organization connector (Beta)
The Anysphere Organization connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector uses the Anysphere (Cursor) Organization Admin API to ingest organization members, groups, and group members into Databricks as daily snapshots.
Anaplan connector (Beta)
The Anaplan connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests audit trail events and user account records from your Anaplan tenant into Databricks. Authentication uses an Anaplan CA certificate and its paired private key. See Anaplan connector .
Openflow gen 1 deployment creation retired
You can no longer create new first generation (gen 1) Openflow deployments (BYOC or Snowflake). All new deployments are second generation (gen 2), created with CREATE OPENFLOW DEPLOYMENT or the Openflow UI. Existing gen 1 deployments continue to work unchanged, and you can still create new gen 1 runtimes on an existing gen 1 deployment.
More from falEvery fal release →
Billing Headers for WebSocket Endpoints
Shared WebSocket endpoints can now declare billing on their 101 upgrade response. Set x-fal-billable-units when the unit count is known at connect time. Set x-fal-billable-units-webhook to 1 when the count is only known at the end of the session. Then report the total with POST /requests/billable-units/{request_id} .
Platform MCP Server
fal's second MCP server , the Platform API MCP , is now available at https://api.fal.ai/v1/mcp/platform . Where the Run MCP lets your AI assistant build with models , this one lets it operate your fal account : connect Claude Code, Cursor, or any MCP-compatible client with your API key and ask "why did my last request to my-app fail?" , your assistant walks...
Key Presets and Custom Policies
Keys now use permission presets instead of the ADMIN and API scopes. When you create a key, select one of seven presets: API , SERVERLESS , DEPLOY , COMPUTE , BILLING , READONLY , or FULL . If no preset matches your case, select the exact permissions the key needs. You can also limit a key to specific models and set it to expire.
Rate Limits for Runner and App Management
fal now limits how often you can list, inspect, shell into, stop, and kill apps and runners. The limits apply to the CLI, the Python SDK, and the REST API. When you exceed a limit, the REST API returns 429 Too Many Requests , and the CLI and SDK return the gRPC status RESOURCE_EXHAUSTED . Learn more about the limits
GPU Utilization in Runner Telemetry
Runner telemetry now includes a dedicated GPU Utilization chart alongside the existing CPU, memory, and VRAM charts, so you can see how much compute your GPUs are actually doing -- not just how much memory they hold.
Deploy Messages and Annotations
You can now attach a freeform message and custom annotations to each revision when deploying: Messages and annotations are set at deploy time and stay with the revision. View and search them on the app's Versions page in the dashboard, or fetch them via the revisions API .
Fallback Chains
fal introduced Fallback Chains, allowing requests to configure a primary model and up to two fallback models that trigger automatically on specified errors.
App-Level Retry Configuration
Apps can now register a default per-condition retry budget at deploy time with the new retry_config deployment option, using the same format as the X-Fal-Retry-Config request header. Set it as a class attribute on fal.App or under the app's table in pyproject.toml .