Changelog
Changes you can see in the SDK, CLI, portal and deployment pipeline, newest first. We leave out internal maintenance and fixes that don't change how you work.
Questions about a change? Email hello@backify.dev. Technical details are in the documentation.
· Functions
When a release that includes server functions goes live, your app's runtime picks up the new functions automatically. Browser calls to defineFunction endpoints are routed through your app's own runtime, and the release records which runtime it deployed.
· Customer Azure
The Backify Cloud Agent in a connected Azure subscription now upgrades itself to compatible, signed releases. When a release needs different Azure role assignments, an administrator approves it in place with Azure sign-in.
· AI
ai.extract accepts more schemasSchemas that don't meet strict structured-output rules are now sent in non-strict mode instead of being rejected. Strict mode is still used when your schema qualifies.
· Deployment
Deployment steps now record why a network call failed, so the portal shows a cause instead of a generic error. Deployments also wait briefly while your app's runtime switches to a new revision rather than failing.
· Customer Azure
In a connected Azure subscription, the Backify Cloud Agent now deploys applications into your designated resource group. Application code and AI coding agents still never receive the deployment identity.
· Backify Cloud
Backify Cloud can now provision file storage, server functions and managed AI models for apps in Azure North Europe.
· Coding tools
The Backify MCP connection in Claude Code and Codex now persists across restarts. The permissions you grant to a connection are enforced by the Backify API, not only by the tool. The CLI authorization page also tells you when the CLI has stopped waiting.
· Database · Breaking change
Browser code can now use only tables that declare an access rule in backify.yaml. Server functions and jobs are not affected. backify dev and backify doctor list browser tables without a rule, and the portal warns while a deployment leaves tables server-only. Apps that call db from the browser need to declare their tables and redeploy. Read the database guide.
· AI
ai.generate and a monthly AI cost limitPass up to 64 tool definitions to ai.generate and let the model call them. Each app's monthly AI cost limit is now enforced.
· Deployment
After a release is promoted to production, Backify watches its health and rolls back automatically if it fails. Deleting an app now takes a final database backup first.
· Portal · CLI
Deleting an app, editing production data and removing shared secrets now ask you to type a confirmation. Budgets get confirmations and spend alerts. In the CLI, backify plan and backify ship --dry-run show what a deployment will change before it runs.
· Database
Managed application databases now run on each hosting account's own PostgreSQL server, with each app's database isolated on that server.
· Portal
Portal URLs now follow Organization → Workspace → Application, so links point at the right scope. When you create an app, you choose its organization and workspace up front, and search can cover the current app, workspace or organization.
· Portal
Your home page shows what's waiting on you, such as approvals and app problems, plus recent deployments. The organization dashboard shows spend, apps that need attention and deployment activity. Each app's overview shows traffic, releases, capability usage, AI tokens and cost by service.
· CLI · Domains
Connect a custom domain from the command line with a guided setup page. In the portal, the domain dialog now opens immediately and fetches the DNS verification token in the background.
· Coding tools
The organization-management MCP server for Claude Code and Codex adds tools to look up data-compliance evidence and search your organization's resources.
· Database
The db capability adds query operators for filtering and supports atomic transactions, so related writes succeed or fail together.
· Jobs · Events
Schedule runs have their own tab and link back to the schedule that started them. Webhook deliveries show diagnostics, so you can see why a delivery failed.
· Portal
Users, roles, invitations, devices, audit log, webhooks, schedules, functions, domains and costs now share one table design with filters and copy buttons.
· Customer Azure
Connecting or disconnecting an Azure subscription shows a live activity log. If setup stops, the recovery view shows the last error for each stage and the agent version involved.
· Secrets · Runtime
App secrets are served from a separate vault for each environment, so preview and production secrets stay apart. Running apps also keep routing requests and resolving existing sessions if the Backify control plane is briefly unavailable.
· Customer Azure
Approve and track the Cloud Agent's deployment into your subscription from the portal. Connected clouds show their connectivity status, and you can remove a connection when you no longer need it.
· SDK · CLI
@backifydev/sdk and @backifydev/cli are packaged as public npm packages, so your coding agent can install them in any repository.