LovableLovable
Lovable 是瑞典 Lovable 的全栈 AI 建站平台:自然语言生成带前端/数据库/认证/托管的完整应用, 内置后端基于 Supabase 开源底座,Git 双向同步把代码放进你自己的仓库—— 官方口径「never locked in」,但构建模型不能指定、训练数据政策按计划分层。
Lovable is Sweden's full-stack AI app builder: natural language in, a working app out with frontend, database, auth and hosting — the built-in backend runs on the Supabase open-source foundation, Git two-way sync puts code in your own repo, and the official line is 'never locked in'. But you cannot pick the build model, and the training-data policy splits by plan.
适合与不适合When to use it, when not to
适合:想法到上线一条龙、Git 同步进自己仓库、企业治理(SSO/SCIM/审计/EU inference)。 不适合:要指定构建模型、要免费把代码下载回本地。
Fits: idea-to-launch in one place, Git sync into your own repo, enterprise governance (SSO/SCIM/audit/EU inference). Not a fit: wanting to pick the build model; wanting to download the codebase back for free (a paid-plan feature).
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-22
- 出品属地Origin
- 国外出品foreign-made Lovable(瑞典斯德哥尔摩,2023 年创立,前身 GPT Engineer——官方 FAQ 自述)。Lovable (Stockholm, Sweden; founded 2023, formerly GPT Engineer — per the official FAQ).
- 国内使用Direct access
- 大陆可直连direct OK docs.lovable.dev 大陆直连实测 200;lovable.dev 首页对脚本请求返回 403(bot 防护),浏览器访问路径未由本站实测。docs.lovable.dev measured 200 direct from mainland; the lovable.dev homepage returns 403 to scripted requests (bot protection); the browser access path was not measured by this site.
- 备案状态CAC filing
- 未见于备案名单not in filing list:未见于网信办公示名单(2026-10-22 检索);该产品未面向大陆公众提供服务,备案不适用。not in the CAC public registry (searched 2026-10-22); the product does not serve the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准(按批次滚动更新,本站只抄编号不解读);「大陆可直连」是本站从大陆网络直连实测的结果,不是厂商承诺。GitHub 类站点当日实测有波动,口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
官方 FAQ 明示:构建侧模型由 Lovable 选并自动更新,用户不能为 Build/Plan/Chat 模式指定具体模型; 你自己应用内的 AI 功能可从官方 AI features 页的支持清单选模型(聊天/图像/视频/语音等各有页)。 企业版有 EU inference(模型请求留在欧洲端点)。
The official FAQ states plainly: build-side models are chosen by Lovable and updated automatically; users cannot pin a specific model for Build/Plan/Chat modes. AI features inside your own app can pick models from the supported list on the official AI features page (chat/image/video/audio each have their own pages). Enterprise has EU inference (model requests stay on European endpoints).
- 运行位置Where it runs
网页端为主形态;官方另有桌面应用、iOS/Android 移动应用、Lovable API(发布项目/管理工作区)、 Lovable MCP server(把 Lovable 接进 IDE 与外部 agent)。项目在 workspace 内建, 一个项目对应一个可同步出代码库的应用(官方 welcome 页口径)。
The web app is the primary form; the official pages also list a desktop app, iOS/Android mobile apps, the Lovable API (publish projects / manage workspaces), and the Lovable MCP server (plug Lovable into IDEs and external agents). Projects are built inside workspaces; one project maps to one application whose codebase can be synced out (per the official welcome page).
- 本地文件Local files
项目代码存在 Lovable 平台内;Git sync 与 GitHub/GitLab/Bitbucket 仓库自动双向同步(官方页明示), 也可 Download codebase(付费计划)。内置后端(Cloud)由 Lovable 托管,基于 Supabase 开源底座 (官方 cloud 页明示:数据库/认证/存储/edge functions,无需自建 Supabase)。 官方「部署托管与所有权」页口径「you are never locked in」:可导出代码、迁移数据、自托管部分或全部栈。
Project code lives inside the Lovable platform; Git sync provides automatic two-way synchronization with GitHub/GitLab/Bitbucket repos (stated on the official page), and Download codebase is available (paid plans). The built-in backend (Cloud) is hosted by Lovable, built on the open-source Supabase base (stated on the official cloud page: database/auth/storage/edge functions, no need to self-host Supabase). The official "deployment, hosting and ownership" page stance is "you are never locked in": export code, migrate data, self-host part or all of the stack.
- 关机后的任务Tasks after shutdown
托管面是产品语义一部分:应用托管随流量自动扩、数据库实例可调(官方 cloud 页); project monitoring 按计划检查应用抓 bug 与访客错误;Subagents 把复杂任务的调研/代码探索拆开并行。 关闭浏览器后构建任务是否续跑未核验到官方声明。
The hosted surface is part of the product semantics: hosted applications scale automatically with traffic, database instances are adjustable (official cloud page); project monitoring checks apps on schedule catching bugs and visitor errors; Subagents split research/code exploration of complex tasks into parallel work. Whether build tasks continue after closing the browser has not been verified in any official statement.
- 工具与扩展Tools & extensions
连接器体系官方成页:app connectors(应用调外部服务)、app user connectors(终端用户连自己账号)、 自定义 REST connector、chat connectors(MCP 服务器,含自定义 remote MCP 与 MCP registries); 内置安全扫描 + Aikido/Wiz 集成;Code mode 内置代码编辑器;可把已发布应用反向发布为 MCP server。
The connector system has official pages: app connectors (apps calling external services), app user connectors (end users connecting their own accounts), custom REST connectors, chat connectors (MCP servers, including custom remote MCP and MCP registries); built-in security scanning + Aikido/Wiz integrations; Code mode has a built-in code editor; published apps can be reverse-published as MCP servers.
- 上下文与记忆Context & memory
项目会话三模式:Chat(讨论)/Plan(先写结构化计划再执行)/Build(直接实现并验证); cross-project referencing 跨项目复用实现;可从 Replit/Bolt/v0 等导入项目; 设计系统可接入。跨会话记忆机制未核验到官方声明。
Project sessions have three modes: Chat (discuss) / Plan (write a structured plan first, then execute) / Build (implement directly and verify); cross-project referencing reuses implementations across projects; projects can be imported from Replit/Bolt/v0 etc.; design systems can be plugged in. A cross-session memory mechanism has not been verified in any official statement.
- 权限与限制Permissions & limits
账号 + workspace 体系;企业面官方成页:SSO(Okta/Auth0/Entra/OIDC/SAML)、SCIM 用户开通、 审计日志(可导出 SIEM/云存储)、Action center(审批发布请求)、workspace 安全中心与敏感数据扫描; 项目可见性(私有/内部/公开)与 RLS 行级安全策略控制数据访问;个人 2FA。
Account + workspace system; the enterprise surface has official pages: SSO (Okta/Auth0/Entra/OIDC/SAML), SCIM user provisioning, audit logs (exportable to SIEM/cloud storage), Action center (approving release requests), workspace security center and sensitive-data scanning; project visibility (private/internal/public) and RLS row-level security policies control data access; personal 2FA.
- 适合什么任务Best for
适合:从想法到带数据库/认证/托管的全栈应用一条龙、要 Git 双向同步把代码放进自己仓库、 企业治理叙事(SSO/SCIM/审计/EU inference)。 不适合:要指定构建模型(官方明示不能)、要免费把代码下载回本地(Download codebase 是付费计划功能)。
Fits: one-stop from idea to a full-stack app with database/auth/hosting; wanting Git two-way sync to put code in your own repo; an enterprise governance narrative (SSO/SCIM/audit/EU inference). Does not fit: people who want to pin the build model (the official FAQ says you cannot); people wanting to download the codebase back locally for free (Download codebase is a paid-plan feature).
头号误解Top misconception
- 构建侧模型不能指定(官方 FAQ:Lovable 为 Build/Plan/Chat 模式选模型并自动更新)—— 与 IDE 类工具的「模型选择器」体验完全不同;能选的是你应用内的 AI 功能模型You cannot pick the build-side model (official FAQ: Lovable chooses and auto-updates models for Build/Plan/Chat modes) — a completely different experience from IDE-style model pickers; what you can pick are the AI-feature models inside your own app
- 训练政策按计划分层:官方 FAQ 明示 2026-09-09 起 Free/Pro 的客户数据默认可能用于训练(可在账户设置关闭), Business/Enterprise 默认排除——数据边界别按「一个产品一个答案」推断Training policy splits by plan: the official FAQ states that from 2026-09-09 Free/Pro customer data may be used for training by default (switchable off in account settings), while Business/Enterprise is excluded by default — don't flatten the data boundary into one answer for the whole product
- 「代码可导出」不等于「后端可白拿」:内置后端是 Lovable 托管的 Supabase 开源底座, 数据库迁移与外部托管要走官方迁移路径(deployment-hosting-ownership 页给路径与边界)'Code is exportable' does not mean 'the backend comes free': the built-in backend is Lovable-hosted on the Supabase open-source foundation; database migration and external hosting follow the official migration paths (the deployment-hosting-ownership page gives routes and boundaries)
未知项清单Known unknowns
- 跨会话记忆机制(未核验到官方声明)
- 构建任务离线续跑行为(未核验到官方声明)
- 内置后端的存储区域与数据驻留默认值(EU inference 是企业面,个人/普通计划的区域未逐条核验)
- 当前应用内 AI 功能的完整模型清单(官方页随版本变化,未逐条清点)
- Cross-session memory mechanism (no official statement verified)
- Offline continuation behavior of build tasks (no official statement verified)
- Storage region and data-residency defaults of the built-in backend (EU inference is the enterprise surface; regions for personal/regular plans not verified item by item)
- The complete current model list for in-app AI features (the official page changes with versions; not enumerated item by item)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-22,内容更新日content updated on 2026-10-22。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| official | Lovable 文档 · Welcome(全栈定位/workspace/代码库同步)Lovable docs · Welcome (full-stack positioning / workspaces / codebase sync) | https://docs.lovable.dev/introduction/welcome |
| official | Lovable 文档 · Built-in backend(Supabase 底座/托管边界)Lovable docs · Built-in backend (Supabase base / hosting boundary) | https://docs.lovable.dev/features/cloud |
| official | Lovable 文档 · Git sync 总览(GitHub/GitLab/Bitbucket 双向同步)Lovable docs · Git sync overview (GitHub/GitLab/Bitbucket two-way sync) | https://docs.lovable.dev/integrations/git-sync-overview |
| official | Lovable 文档 · 部署托管与所有权(不锁定口径/导出与自托管路径)Lovable docs · Deployment, hosting and ownership (no-lock-in stance / export and self-host paths) | https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership |
| official | Lovable 文档 · FAQ(模型不可指定/训练数据政策)Lovable docs · FAQ (models not pinnable / training-data policy) | https://docs.lovable.dev/introduction/faq |
| official | Lovable 文档 · Chat connectors(MCP 接入面)Lovable docs · Chat connectors (MCP integration surface) | https://docs.lovable.dev/integrations/chat-connectors |
| changelog | Lovable 文档 · Release Notes(changelog)Lovable docs · Release Notes (changelog) | https://docs.lovable.dev/changelog |
实测记录Measured runs
本档未跑端到端编码任务;能力结论来自官方文档,编码向测量协议见 protocols/coding/_protocol.md。
实测建议(三条,都指向官方可读页没给的东西):
- Git 双向同步在两边同时改代码时的冲突实际行为(官方页讲机制,未给冲突样例)
- 内置后端迁移到自建 Supabase 的实际步骤完整度(官方有迁移页,未逐步走通)
- Build 模式关闭浏览器后任务是否续跑(未核验到官方声明)
This site has not completed measured runs. The test protocol is at protocols/coding/_protocol.md.
Suggested measurement (three items, all pointing at what the readable official pages do not give):
- Actual conflict behavior of Git two-way sync when code is changed on both sides at once (the official page describes the mechanism but gives no conflict example)
- Completeness of the actual steps for migrating the built-in backend to self-hosted Supabase (an official migration page exists but was not walked end to end)
- Whether Build-mode tasks continue after closing the browser (no official statement verified)
相关条目Related entries
- Bolt.newBolt.new同为提示词到全栈应用:Bolt 跑在浏览器内 WebContainers,Lovable 用云端托管后端。also prompt-to-full-stack app: Bolt runs in-browser WebContainers, Lovable uses a cloud-hosted backend
- v0v0同为 Vercel 系:v0 绑 Vercel 部署链与 Next.js 栈,Lovable 自带后端与多 Git 平台同步。also Vercel-adjacent: v0 binds the Vercel deployment chain and the Next.js stack, Lovable ships its own backend and multi-Git-platform sync
- Replit AgentReplit Agent云 IDE+agent 对照:Replit 给你完整云开发环境,Lovable 把环境藏进提示词流。cloud IDE + agent contrast: Replit gives you a full cloud development environment, Lovable hides the environment inside the prompt flow
- Supabase MCPSupabase MCP另一层 · MCP 工具Other layer · MCP tools
本页由This page is generated from the ai-handbook 数据层生成(CC BY 4.0)。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.