A function that verifies a user its own way, with an SMS code or another identity provider, can now sign them in: call createSession(userId), or ctx.auth.createSession(userId) in a sandboxed function. Backenly signs the session, and the token is the same one password sign-in issues, valid for seven days.
// An http functionimport { createSession } from'@/lib/auth/session'// Call it only after your own check has passed,// such as a code sent by SMS.const { token, user } = awaitcreateSession(userId)
// A sandboxed functionconst session = await ctx.auth.createSession(userId)
ImprovedAutonomy
Index repairs no longer block writes
Backenly builds its index repairs with CREATE INDEX CONCURRENTLY on a separate connection, so writes keep flowing. Autopilot also builds indexes for queries PostgreSQL measured as slow, and partitioning advice appears only for tables larger than the database’s cache.
03:07Index added on its own, without blocking reads or writes
03:08Re-checked: fixed. All 27 checks pass.
03:12Waiting on youyour agent asked to drop a column on movies
Rows read to find one movie's watchlist entries, per minute. At 03:06 a check found no index on watchlist_items.movie_id; at 03:07 Backenly added it on its own; at 03:08 it was re-checked and all 27 checks passed. At 03:12 your agent's request to drop a column on movies waited for you.
Minute
Rows read
Checks
03:05
4,120
all 27 checks pass
03:06
4,120
26 of 27 checks pass
03:07
3
index added, re-checked next minute
03:08
3
all 27 checks pass
03:09
3
all 27 checks pass
03:10
3
all 27 checks pass
03:11
3
all 27 checks pass
03:12
3
all 27 checks pass; one request waiting on you
03:13
3
all 27 checks pass
03:14
3
all 27 checks pass
03:15
3
all 27 checks pass
03:16
3
all 27 checks pass
03:17
3
all 27 checks pass
FixedAuth
Magic links and verification emails are sent
On Backenly Cloud, magic-link and resend-verification emails for projects on Backenly's built-in email were being logged instead of sent. They are delivered now.
auth.signUp and auth.signIn send the project key, create() returns the new row, and a filter the SDK cannot send in full is refused instead of quietly dropped. storage.getUrl() returns an address that serves the file, and the supabase-js shim’s realtime and storage calls work.
When a function fails after it has started, Backenly no longer runs it again, so rows it inserted and emails it sent are not repeated. A failed HTTP function keeps its logs, and /fn answers 402 when a plan limit blocks the call.
Stripe counts as connected once its webhook signing secret is saved, and the Integrations page shows the endpoint to add in Stripe. Stripe events update the project’s tables and report anything they could not apply. ctx.integrations.anthropic.complete() uses a current Claude model and accepts a model name.
The tool list an agent session starts with is 36% smaller for read-write keys and 31% smaller for read-only keys. Each tool now states its required arguments, which actions wait for approval and which docs topic to read.
apply_migration, branch migrations and merges create each column with the declared type, and CREATE TABLE no longer adds unique, check or foreign-key rules guessed from column names. On tables built earlier, Backenly offers to remove the rules it guessed.
Agents can drop an index, a constraint or a column, or change a column’s type, on a preview branch or with a person’s approval; apply_migration used to refuse all of these. It also installs allowlisted extensions with CREATE EXTENSION.
A branch merge card says what the merge will do to production’s rows, and a merge that would fail on them is refused before anyone is asked to approve it. Branches carry production’s foreign keys, renamed columns show as renames, and an agent can discard its own preview branch.
A row-update function can name the columns it watches and runs only when one of them changes, and row-event runs are queued a few at a time. HTTP functions return the status and body your handler wrote, and can read the project’s environment variables.
Password reset emails link to a page where your user sets a new password, and GET /api/v1/{projectId}/auth/me returns the signed-in user. Auth emails sent without your own SMTP carry your app’s name, and the Auth page says who sends them.
Every v1 error has a top-level code and message, and /api/v2 errors use PostgREST’s shape. A refusal names its cause, such as row-level security, a value of the wrong type or a body over the size limit, and an unknown field in a query body gets a 400 instead of being ignored.
Autonomy has a Review-only or Autopilot switch in its header, and every row is titled in words with at most two buttons. History groups changes by day and shows whether a person, your agent or Backenly made each one.
Approve several of an agent’s waiting requests at once, from cards that say what approving does.
Realtime sends a large row change with its primary key, and no longer drops events in a burst.
A browser key’s rate limit applies to each visitor separately: 300 requests every 10 seconds by default.
on_signup functions also fire for Google, GitHub and magic-link sign-ups.
The portable export keeps row-level security policies.
October 2026
15 changes: 10 new, 5 improved
NewPlatform
One History for every change
History lists every change, from your agent, Backenly or a person, across schema, auth, storage, functions, integrations, webhooks, environment and API keys. Restore one change, or everything after a point, on every plan; restore points are kept 7 days on Free, 30 on Pro and 90 on Enterprise.
Kept in its vault: 1,284 valuesRestored by you at 12:15
runtime is back with its 1,284 values.
The 4 movies added since have no runtime.
The posters bucket, created after it, stays.
Backenly autonomyDatabase
Claude CodeDatabase
Every step, as recorded
Removed column runtime from movies
You, approving Claude Code’s request
Checkpoint taken
Applied
Verified
Restore started
Restore verified
Choose any change to read its steps.
Removed column runtime from movies: Checkpoint taken at 09:14:06, Applied at 09:14:06, Verified at 09:14:07, Restore started at 12:15:40, Restore verified at 12:15:41.
NewAutonomy
Restructure a table with one approval
When columns that belong in a table of their own grow inside another, such as refund_* on orders, Backenly can move them out without breaking existing clients. It rehearses on a copy, asks you once, makes the change in steps and never drops the old columns itself.
Each mark is a sample row. These three are filled in together.
review_moderationplanned
review_id
flagged_at
flag_reason
moderated_by
Your apps read and write it now. The reviews table keeps working too.
Waiting on you
Move moderation data out of reviews into its own table
Changes to these three columns locked all of reviews 5 times in the last 30 days.
30 days on: changes to these columns locked reviews 0 times, down from 5. It helped.
Rehearsed on a copy of reviews, then rolled back
Set up review_moderation
Keep it in step with reviews
Copy the existing moderation data
Check that it matches reviews
Open it to your apps
Agents can read this plan. Only a person can approve it.
ImprovedMCP and agents
backend_chat keeps working after the call returns
A backend_chat request can run for up to ten minutes. The call waits up to 45 seconds, then returns what has landed so far with status running, and backend_chat status collects the rest. It also builds up to about six tables per response instead of planning first.
Every production schema change, from an agent, the console, a branch merge or self-healing, takes a checkpoint and runs a verification the caller cannot weaken. A failed change rolls itself back when nothing would be lost, otherwise a person decides, and dropped tables and columns are kept so the change can be restored.
Create a project in Mumbai, N. Virginia, Oregon, Frankfurt or Singapore. Its database, files, snapshots, function logs and agent conversations stay in that region, and Connect and Settings show that region’s API address.
Connect → Agents lists the agents you authorised by signing in from the browser, and lets you disconnect them. The console also issues read-only MCP keys, and requests waiting for your approval are counted on the Overview and in the top bar.
When Backenly’s checks cannot explain a finding, Claude investigates it from the evidence and the schema’s names, never your rows. It can propose one exact repair, which runs only after a person approves it, counts as fixed only when three checks agree, and can be undone.
Projects now live in an organization with its own members, settings, plan, invoices and AI credits; your account became your personal organization and kept what you had paid for. Free has 2 seats and Pro has 5, and invitations are accepted in the console.
Each preview branch has its own endpoint, key and test users, and its traffic stays out of production’s monitoring and autonomy. Agents build on a branch with apply_migration { branchId }, and a merge replays the branch’s migrations on production after a person approves.
No plan limits API requests, so Free no longer stops at 100,000 in total. Free stays bounded by monthly active users, database size, file storage, egress, function runs and AI credits.
Startups can apply for free Pro at /startups/apply by confirming a work email at their company’s domain. The founding team reviews every application, and an approved pass moves the account to Pro and ends on its own.
The console is rebuilt on one design system: hairline borders, sentence-case headings and status shown as a coloured dot beside its text. Members, Billing and the organization switcher share the same frame.
An agent’s deploy rollback asks a project admin to approve the restore it would run.
Connect gives one install command per coding agent, and adds Antigravity.
The startup pass is now three months of Pro, up from two.
New Cloud accounts get a welcome email, and the critical-issue email says why each issue is waiting for you.
Foreign keys from apply_migration keep their declared column, name and ON DELETE rule, and cron ranges such as 1-5 fire on every day in the range.
September 2026
15 changes: 12 new, 2 improved, 1 fixed
NewSelf-hosting
Self-host with one command
npm run selfhost takes a fresh clone to a ready deployment, filling in missing secrets without rotating existing ones. Running it again upgrades the deployment through its migrations.
git clone https://github.com/backenly/backenly.git
cd backenly
npm install
npm run selfhost
ImprovedStorage
Storage follows your plan
File storage is limited by your plan, so Pro’s 100 GB applies where every project had been capped at 1 GiB. Uploads accept files up to the bucket’s limit, at most 100 MB, and a larger body gets a 413 instead of a 500.
Pro checkout runs on Stripe, and Stripe’s customer portal handles your payment method and invoices. A cancelled plan stays on Pro until the end of the period you paid for.
functions { action: "deploy_code" } stores an agent’s code exactly as written, once the runtime has checked it. Runs keep their logs whether they succeed or fail, and agents read them with functions { action: "logs" }.
apply_migration refuses CREATE TABLE on a table that already exists, with TABLE_EXISTS, and no longer creates a missing table on ALTER TABLE. ADD COLUMN keeps the NOT NULL, DEFAULT, UNIQUE and REFERENCES it declares.
Agents get auth, storage, functions, realtime, integrations, monitoring, autonomy, webhooks, deploy and connect tools. Each runs the same operation and permission check as the console, and a call held for approval runs exactly as requested once a person approves it.
The remote endpoint and @backenly/mcp-server 0.4.0 run on the official MCP SDK and serve hosts on older and current versions of the protocol, with the same results over stdio and remote. The package needs Node.js 20 or newer.
Signing up to Backenly with an email and password confirms the address with a six-digit code before the account exists. Password reset uses a code too, and now works for accounts created with Google or GitHub.
Webhook endpoints receive row.inserted, row.updated, row.deleted and auth.user.created events. Row changes are captured in the database, so writes through the data API trigger them too, and every delivery is signed and retried.
Database → Snapshots takes and restores one project’s tables, rows, indexes, constraints and row-level security policies. A self-hosted deployment can export everything from Settings → Recovery and restore it with npm run recovery -- restore.
A project can send its users’ email through its own SMTP server and replace any built-in template. The settings show the result of the last real send, and Send test reports your provider’s reply.
Install allowlisted PostgreSQL extensions from the Database page, or get the exact command where the database does not allow it. Create enums and domains; each type lists the columns that use it and cannot be dropped while any do.
The Database page has a SQL workspace that runs every query as the project’s read-only role, inside a read-only transaction. It says when results are truncated and names any columns it redacted.
Without Cloud configuration, Backenly runs single-tenant: one deployment serving one project. npm run bootstrap provisions it and, when rerun, completes only what is missing, and the web and runtime servers build as containers.
Also this month
New API keys start with proj_live_, svc_live_, mcp_live_ or dk_admin_; older sk_ keys keep working.
Daily project backups run on Backenly Cloud.
A fresh self-hosted deployment is claimed from the sign-up page with its setup token.
The project console works on phone screens.
August 2026
11 changes: 7 new, 3 improved, 1 fixed
ImprovedAutonomy
Self-healing every minute, on every plan
The repair loop, the contract sweep and the infrastructure scan now run every minute on every plan. The sweep had run every 15 minutes and the scan once a day, so a fixed problem could stay listed for up to 24 hours.
One hour of checks on one project60 min
Contract sweep
Before
Every 15 minutes
Now
Every minute
Infrastructure scan
Before
Once a day
Now
Every minute
NewAutonomy
Undo for automatic fixes
Fixes Backenly applied on its own show an Undo button wherever they can be reverted, and undoing a change to row-level security asks you to confirm twice. Each fix records the exact SQL it ran, with a copy button in the Changes panel.
ImprovedAutonomy
Foreign keys and index drops wait for you
Backenly asks before adding a missing foreign key, naming the target table and the exact ON DELETE rule, instead of adding one with CASCADE itself. It reports an index only after 14 days without a scan, and drops it only when you approve.
NewAutonomy
Repairs for bloat and failed migrations
Backenly rebuilds bloated indexes with REINDEX CONCURRENTLY and runs VACUUM ANALYZE where autovacuum has fallen behind. It also finds an unfinished concurrent index or a constraint left NOT VALID by a failed migration, fixes each with one approval, and reports abandoned prepared transactions.
NewAutonomy
Each backend measured against itself
Every hour, Backenly records query latency, sequential scans, table size and connections for each project. When one moves well away from its two-week median, it reports the numbers and what changed just before, and never fixes these findings on its own.
NewMCP and agents
Connect an agent by signing in
The remote MCP endpoint supports OAuth, so a host that supports it opens your browser to sign in instead of needing a key pasted into a config file. The consent screen starts with read-only selected.
NewMCP and agents
Read-only keys for agents
An MCP key can be issued read-only: its agent is offered only read tools, every write is refused with READ_ONLY_KEY, and backend_chat is withheld. A key’s mode is fixed when it is issued.
ImprovedDatabase
Branches as isolated test environments
A branch gets its own sequences and production’s row-level security policies, and starts without production data unless you ask for a copy. An API key bound to a branch sends its requests there.
NewAutonomy
Indexes for the columns slow queries filter on
Backenly reads slow queries from pg_stat_statements, checks the filtered column against the catalog and creates the index, and only advises when it cannot verify the column. New checks flag optional foreign keys the data says are required, unique columns without a constraint, enums kept as free text and money stored as a float.
NewPlatform
Responses say which layer decided them
Data API responses carry x-backenly-request-id and x-backenly-layer headers, naming the layer behind the result: client, auth, api, database or platform. An empty result from a table with row-level security, read without a user’s token, is attributed to auth.
FixedDatabase
Generated tables accept the rows they need
Tables Backenly generates no longer make every column NOT NULL. A column is required only when it is a primary key, a foreign key, an email or a username, or when you ask.
Also this month
Backenly no longer reports its own internal tables as findings.
Connection health is reported per project instead of for the whole database server.
generate_function over MCP draws AI credits for each call.