Jaah Can Copy Lovable. Lovable Can’t Copy Jaah.

Lovable turns a sentence into a working web app, and its own docs say plainly where that app stops. Jaah runs the agents, machines and checks that build whole systems: the app, and the services, servers and cloud setup behind it. Both halves come from Lovable’s own documentation and from Jaah’s own record.

Here is a claim in two halves, as both products stood in October 2026. Jaah could build a copy of Lovable, a service where you describe a web app in plain words and get a working one back. Lovable could not build a copy of Jaah. The reason is what each one builds. Lovable builds web apps, one app per project. Jaah runs agents that build whole systems: services, the software that runs their machines, installable programs and the cloud setup under them, and an app builder is one such system.

What Lovable does well

Lovable’s documentation, as of October 2026, calls it a full-stack AI development platform for web applications. You describe the app and, the same docs say, it generates a working application: screens, a database, sign-in and connections to other services, all as code you can edit. Its quick start promises a first app live on the web with about ten minutes of hands-on time, with nothing to install and nothing to configure. For a founder with an idea and no engineers that is a real gift: a prototype to show people the same day.

Lovable is plain about ownership too. Its Git sync, as of 2026, keeps your code in a repository you own on GitHub, GitLab or Bitbucket, synced in both directions. Its ownership page says Lovable runs on infrastructure certified to SOC 2 Type 2 and ISO 27001, two security standards. The same page says Lovable wants you to stay by choice, never by necessity, and then explains how to leave. It is a good page.

Where Lovable’s docs say it stops

The same docs are as clear about the edges. A Lovable app, they say as of October 2026, has three independent parts: the code, the front end people see, and a backend that stores the data and signs users in. That backend is built on Supabase’s open-source foundation (a hosted database with sign-in and file storage), and Lovable manages the hosting and backend for you. The code you take away, by Git sync or by download, leaves out the records in your database and the files in storage; those move separately. Moving the database alone, the docs say, does not move sign-in, storage, live updates or server functions, the small pieces of code that run on the server. AI features and connections to other services, the same docs add, run through Lovable until you replace them.

The ownership page, read in October 2026, also lists what changes if you stop using Lovable. You take on the build pipelines, meaning the steps that test and release a change; production servers; databases and backups; sign-in; secrets, meaning passwords and keys; monitoring; and compliance. The same page says the Lovable platform itself, the editor and the AI agent, cannot be self-hosted, so you cannot run it on your own machines. The apps can be hosted anywhere, and the thing that builds them runs only at Lovable. In Lovable’s introduction, each project represents a single application.

What building Jaah took

Jaah is the other kind of product. It runs AI agents on real codebases, and each one works as a full-stack engineer: it owns a change across the whole system, from the screen to the servers, machines and cloud setup underneath, and checks its own work. Playbooks, a team’s own list of stages with an agent for each stage and what it hands back, put the same agents on the work that comes before the code, such as researching a market or writing the requirements. Jaah’s main repository was created on 25 June 2026, and by October 2026 it held 6,507 merged pull requests. A pull request is one proposed change, and merged means it was accepted into the product. Jaah’s own agents do that work, and the site’s Live view shows them at it. Here is some of what those changes built, described by what each part does. Very little of it is a screen.

First, a control plane, the one service every other part reports to. As of October 2026 one deployment can serve many organisations, which engineers call multi-tenant, and its database keeps each organisation’s tasks, machines and secrets apart. It keeps the credentials and hands a running agent only the ones its task may use. Its web console has single sign-on, so a company’s staff log in with the company login they already have.

Second, a fleet of machines, which Jaah calls nodes. A node can be a computer the customer owns, joined with one pasted command, a cloud machine that Jaah starts in the customer’s own AWS account, or one rented from Jaah. A node, in October 2026, updates itself and cleans up after every job, and with MicroVM turned on it gives each task a small virtual machine of its own.

Third, the servers behind all this are written down as code. As of October 2026 Jaah’s cloud setup is a set of files for Terraform, a tool that builds cloud servers from a written description, and those files have tests of their own. A change to production is a reviewed change like any other, and once it is accepted the agents run the deploy, watch it in production and roll back a bad release. The same holds on your own projects: a sensitive operation waits for your approval, or for a security review of its own when you run it unattended.

Fourth, a program that runs outside the browser. The node software, released in 2026, ships as an installable program for Linux, macOS and Windows, built, tested and released from the same repository as the rest. (Corrected in November 2026: an earlier version of this paragraph said the console had a phone app of its own. The console runs in the browser, laid out for a phone as well as a desktop.)

Fifth, the checks. Every project names a quick check that an agent runs before each change it saves, and a full set of tests that runs before a change is accepted. A merge lane tests finished changes together in batches, and when a batch fails it splits the batch until it finds the change that broke it. Separate reviewer agents read each change without seeing the reasoning of the agent that wrote it. A change is done when those checks and reviews pass, whatever the agent that wrote it reports. The change that put this essay on the site, in October 2026, went through the same lane.

Why the copying runs one way

Set Lovable’s parts beside Jaah’s, as both stood in October 2026. Lovable has the editor and AI agent, and Jaah has a web console and agents that write code. Lovable’s hosting gives each app a fully managed backend, databases, and infrastructure. Jaah’s agents built their own control plane, with its database, sign-in and secrets, wrote the cloud under it as Terraform, and deploy, watch and roll back every release. Each part Lovable runs has a counterpart Jaah’s agents have already built. A copy of Lovable, here, means a product of the same kind. Lovable’s users, its scale and its polish are another matter, and no amount of code reproduces them.

Now try it the other way round. To copy Jaah, Lovable the product, rather than its engineers, would have to produce a service that runs other people’s machines, installable software for three operating systems, and cloud servers written as tested Terraform files. Its docs in October 2026 say it makes web applications, one project to one app, and the installable program and the Terraform files are not web apps. A crane can build a house. A house has yet to build a crane.

One app, taken the rest of the way

In 2026 a client brought Jaah an app made with a prompt-to-app builder. It worked, and now it had to run in production on a public cloud. Jaah’s agents did the move as ordinary tasks, each one a reviewed change. They kept a read-only copy of the original as a reference and mapped it feature by feature, then packed each part into a container, a sealed bundle that runs the same on any server. They removed the parts that only worked inside the builder, wrote the cloud setup as Terraform, made every service require sign-in, and built the pipeline that tests and releases each change. That covers the servers, the sign-in and the pipelines on the list a builder’s exit page hands you.

Who answers for the system

The agents report to Jaah, and Jaah reports to you on the whole system, the moved app above included.

  1. Welcome to Lovable, Lovable Docs, 2026-10.
  2. Quick start: build and publish your first Lovable app, Lovable Docs, 2026-10.
  3. Sync your Lovable project code with GitHub, GitLab, or Bitbucket, Lovable Docs, 2026-10.
  4. Deployment, hosting, and ownership options with Lovable, Lovable Docs, 2026-10.
  5. Built-in backend, Lovable Docs, 2026-10.
  6. Deploying and hosting outside Lovable, Lovable Docs, 2026-10.

All posts