# reachpad vs Lovable

> Lovable is for creating an app. reachpad is for what happens to it afterwards: running it, changing it with whichever agent you use, and handing the running thing to someone else by link. The first is a product; the second is a machine.

Part of the reachpad comparisons: https://reachpad.dev/compare. Rendered page: https://reachpad.dev/compare/lovable. Last checked 2026-08-23.

## Side by side

|  | Lovable | reachpad |
| --- | --- | --- |
| What it is | A chat that produces a web app, with hosting attached | A Linux workspace where an agent builds and runs anything |
| Which model | Lovable's | Claude Code, Codex, or anything you install, on your accounts |
| What it builds | Web apps in its supported stack, with Supabase as the backend | Anything that runs on Linux: web, API, worker, script, database |
| Where it runs | Lovable's hosting | The workspace, exposed by port |
| Changing it later | Continue the chat, or edit in the code view | Any agent, any editor, a terminal, root on the machine |
| Sharing | Publish to a Lovable URL or your domain | A port link for signed-in visitors, or a per-person workspace grant |
| Persistence | The project lives in Lovable | The disk is sealed and outlives the VM; files, installs and git state come back |

> Note: Lovable describes itself at [docs.lovable.dev](https://docs.lovable.dev). The rows above describe it as documented on 23 August 2026.

## The difference that matters

Lovable optimises the first hour. Describe the app, watch it appear, publish it. The model, the framework and the backend are chosen for you, and for a first version of a web app that is a feature, not a limit.

reachpad optimises everything after the first hour. The app an agent wrote is running on a machine that stays up, its data is next to it, and changing it is the same act as writing it: the agent edits a file. Nothing about the workspace cares which agent, which framework, or whether the thing is a web app at all.

They are not really competitors. An app generated on Lovable can be exported to a repository and cloned into a reachpad workspace, where a different agent continues it. The reverse is not true: reachpad does not generate anything, it runs what an agent generated.

## When Lovable is the right answer

When you have an idea and no opinion about the stack, the model or the hosting. When the person building it is not a developer and does not want a terminal. When the app is a web app and Supabase is a fine backend. If that is the job, Lovable gets to a published app faster than anything on this page, and reachpad is for when you want your own agent to keep working on it.

## Trying reachpad

166 hours 40 minutes of agent work is shared across up to 10 workspaces, with no card required. The [quickstart](https://reachpad.dev/docs/quickstart) is six commands and the last one is a link you can send.