AnalysisNew

    Lovable Got Markedly Better in September. At Building, Not at Launching.

    Four Lovable releases in sixteen days shortened the loop between an idea and a working preview. None of them shortened the list between a working preview and a published app.

    Between 8 and 23 September 2026 Lovable shipped four changes in sixteen days: follow-ups, drafts, login-aware browser testing and a workspace API. Every one of them is a real improvement, and if you are building on Lovable today you should turn all of them on.

    They also share something worth naming. Each acts on the loop between an idea and a working preview. None acts on the surface between a working preview and a published product that stays up. That is not a complaint - it is a boundary Lovable draws itself, and the clearest sentence about it is Lovable's own description of drafts: your published app changes only when you publish, not when you accept a draft.

    What actually shipped

    8 September - follow-ups and login-aware testing. You can send a correction or a new idea while Lovable is still working, instead of waiting for the run to finish. The same release taught Lovable's browser testing to sign in to your app and check the pages behind a login, such as dashboards and account pages, rather than stopping at the login screen.

    9 September - drafts. A draft is a separate copy of your project with its own chat, preview and edits, so you can compare two approaches without touching the version your team is looking at.

    17 September - the Lovable API. From your own scripts and services you can list and update projects, publish and unpublish them, embed a project preview in your product, and read analytics and security scans. It needs an API key created in account settings, a Business or Enterprise plan, and an owner or admin role. Apps built on Lovable can also connect back to the workspace itself, which is what makes internal dashboards and client portals on top of your workspace possible.

    23 September - Claude models for in-app AI features, alongside five new cloud connectors: AWS API, Azure Cloud API, Azure Graph and Entra API, Google Cloud API and Looker.

    Taken together, that is a strong month. Drafts in particular close a gap that used to cost founders real money, because the only way to try an idea was to change the project everybody was watching.

    Where September moved the line

    The jobWho owns it after September 2026
    Iterating without disturbing the live appLovable - drafts, 9 Sep
    Exercising the pages behind your loginLovable - browser testing, 8 Sep
    Publishing and unpublishing from a scriptLovable API, 17 Sep - Business and Enterprise plans only
    Pulling analytics and security scan resultsLovable API, 17 Sep
    Deciding when your Postgres version changesYou
    Reindexing after that changeYou
    Patching your framework's security releasesYou
    Per-route titles, canonicals and real sitemap datesYou

    The three things the API cannot reach

    Your database's calendar

    On 25 September Supabase announced the PostgreSQL 15.19 / 17.11 minor release, bundling five upstream security cycles and closing 44 CVEs. Four of its changes may require action: a case-folding fix that affects ltree indexes on multibyte and ICU databases, pgcrypto refusing to decrypt data written with the bf, blowfish or cast5 ciphers - data Supabase says was effectively stored unencrypted - btree_gist indexes on float columns that can contain NaN, and custom operators whose non-built-in selectivity estimators are now superuser-only. New projects default to 15.19/17.11 from 28 September; existing projects upgrade when their owner decides to. Supabase publishes detection queries for all four cases. Running them is a person's job, and reindexing afterwards is a person's job. No API call schedules that work for you.

    Your framework's release cadence

    If you have migrated to Next.js, the last two weeks were busy. On 22 September Next.js published an out-of-band security update - 16.3.6 on the Active LTS line, 15.5.26 on Maintenance LTS - for a critical remote code execution issue in the Node.js ImageResponse implementation in next/og, caused by improper escaping in Satori's SVG output. Versions 16.2.0 up to 16.3.6 were affected; applications using the Edge implementation were not. The next day Next.js gave notice of a scheduled release on 30 September carrying nine further vulnerabilities - one critical, two high, five medium and one low - shipping as 16.3.7 and 15.5.27. Two security events in nine days, on one dependency, both needing somebody to run the upgrade and redeploy.

    The routes a crawler reads

    Nothing in September's releases writes a per-route canonical, puts a real lastmod on a sitemap entry, or turns a card-shaped div into a link a crawler can follow. Those remain decisions somebody makes about your project once, and then maintains.

    What this changes about staying or migrating

    The honest read is that September strengthens the case for staying on Lovable longer than most founders assume. A platform that can branch, test behind a login and be driven from a script is a platform you can run a real product on. What it does not change is the list you inherit the day you take payment: a database whose upgrade window is yours, a dependency tree whose security calendar is yours, and a set of routes that either are indexable or are not. Those were never on Lovable's side of the line, and the API's arrival does not move them. Three questions worth asking before your next sprint: who ran the detection queries, who is on the hook for the 30 September Next.js release, and does your sitemap carry dates anyone would believe?

    Where we come in

    IdeaFlo has completed 80 jobs on Upwork, and this is the list we work through. The $499 Strategy Audit is the cheapest way to find out which of the items above apply to your project - one scoping call, a written technical roadmap and a stack recommendation, credited in full toward any build. If the answer is that the app needs to ship properly rather than be patched, the Publishable MVP is $4,999 and ships ready to publish, and the Founding Client tier is $2,999 with a 14-day build guarantee and a full refund if we miss the deadline. Both carry the same revenue guarantee: first paying customers within 90 days of launch, or a full refund.

    Book your free 20-minute intro call

    Sources

    Related posts