Blink vs Lovable (2026)

Every app Blink generates comes wired to a Turso database, Blink Auth sign in, file storage and a live web address with SSL. Beyond that core, 63 connectors across email, calendars, team chat, CRM, projects, payments, analytics and social media are connected once by a workspace admin, most with a single sign in, and each project then picks which accounts it may use.

When a builder describes an app, the agent checks which connectors are live and writes the code that reads and sends data through them, and every call is routed through Blink's connector service so no token sits in the app's code. A few tools, among them Meta Ads, ElevenLabs, Perplexity and Firecrawl, take a pasted key instead. Claw agents reach Notion, Google Drive, HubSpot and Slack and send email, and outside assistants can list, authorize and disconnect connectors through Blink's MCP server.

Sourceblink.new/integrationsread 2026-10-09

Connectors sit in a single catalog, with Lovable handling authentication, credentials and requests. There are three connection types, app connectors, chat connectors and app user connectors, where each person using the published app connects their own account, and each connector's page says which types it supports.

About ninety integrations have their own pages, spanning Salesforce, HubSpot, Pipedrive and Zoho CRM, Snowflake, BigQuery, Databricks, Redshift, ClickHouse and Microsoft Fabric, Shopify, WooCommerce, PrestaShop and Lightspeed, Stripe, Chargebee, QuickBooks and Xero, Slack, Twilio, Telegram and Resend, Workday and Ashby, Aikido and Wiz, Notion, Airtable and Contentful, and AWS S3. An any API route, a create connector path, custom MCP servers and MCP registries cover anything not listed.

Sourcedocs.lovable.dev integrations introduction, app-connectors, chat-connectors, app-user-connectors, any-api, create-connector and integration catalogread 2026-08-31

The build agent runs one multi step loop per request. It plans the change, writes the frontend and backend, sets up the database and sign in, lints and builds the app, and saves a version when the task is done.

An outside assistant can start the same loop through the blink_build_prompt tool, follow it with status and wait calls, and answer the agent when it stops on a question, since a new prompt is refused until that question is answered or the build is stopped.

Claw agents each run alone on their own machine and can be paused, resized or deleted without touching the others, so several can work in parallel, though they do not hand work to one another or share a plan.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

Build mode, formerly Agent mode, works on its own and takes a task end to end. It understands intent, explores the codebase for context, applies changes across files and resolves issues during development, with visible tasks showing progress and results reviewed before moving on.

Plan mode handles decisions, and the user can switch between the two at any time. Subagents are a separate feature, and cross project referencing lets one project draw on another. Skills apply reusable instructions, code mode and the project editor expose generated files for direct editing, and drafts and project history support iteration.

Sourcedocs.lovable.dev agent-mode, plan-mode, subagents, cross-project-referencing, skills, code-mode, projects/editor, drafts and projects/history pagesread 2026-08-31

Blink Claw agents run around the clock on a private cloud machine and act on their own schedule, with examples such as a 6:45 AM summary, a 3am inbox check and a Friday report, and on events, such as a follow up sent within ten minutes of a signup.

They take messages from Slack, Telegram and Discord, with WhatsApp also listed in the automation docs, can be chatted with inside Blink, and message the user first when something needs attention. How a schedule is set up is unclear.

The app builder itself starts work when someone sends a prompt, in the Blink workspace or from Claude, Claude Code or ChatGPT over MCP.

Sourceblink.new/clawread 2026-10-09

Lovable can check a project on a schedule, daily or weekly at a chosen time and optionally only after a minimum number of edits, reviewing the app code for broken functionality and recent visitor errors, then alerting by email and listing findings to fix in the project chat. So the builder agent wakes on a schedule without anyone asking. Other routes in are the web chat, a Slack app, mobile and desktop apps, a Telegram route, the Lovable API and the Lovable MCP server. Monitoring is in beta, on Pro, Business and Enterprise.

Sourcedocs.lovable.dev project-monitoring page and llms.txt indexread 2026-09-29

Each build works from the project itself: its source tree, database schema, backend functions and saved versions. Blink's MCP server exposes the same material to outside assistants for reading, including file contents, the schema and a diff between any two versions, while secret files such as .env are never returned. Claw agents draw on the workspaces they are connected to, such as Notion and Google Drive. The Knowledge Base in Blink's docs is a retrieval feature for the apps Blink builds, so the build agent keeps no searchable index of a company's wider documents.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

Knowledge holds persistent instructions and context for the agent, defined once and always included, at two levels. Workspace knowledge holds shared rules across all projects, such as coding standards, preferred libraries and naming conventions, and project knowledge holds the app's purpose, database schema, architecture decisions and domain terminology. Workspace knowledge is a text field, unlike Skills, which load on demand.

Project and workspace knowledge plus the customer's code and components are the main context sources, and Lovable does not describe reading instruction files from the repository or from outside sources. Design systems are Lovable projects that export reusable components, colors, fonts and styling rules, which other projects connect to and inherit, with immediate propagation, an order of precedence across several connected systems, and no versioning. Cross project referencing and about ninety integrations supply more material for each request.

Sourcedocs.lovable.dev features/knowledge, design systems FAQ and knowledge context-sources FAQread 2026-08-31

Claw agents keep 1 GB of storage and memory that survives restarts, so preferences, goals and context carry from one conversation to the next, and pausing an agent stops its machine while keeping its data. How that memory is stored, reviewed or cleared is unclear. In the app builder, continuity comes from the project rather than from the agent: every finished task saves a version with a screenshot and a generated description, and the agent rereads the project's code and schema on each request instead of carrying memory of its own across projects.

Sourceblink.new/clawread 2026-10-09

Projects are durable objects with a history page recording changes, drafts keep unfinished work, and project chat persists. A Knowledge feature holds project configuration, and cross project referencing lets one project draw on another. Build mode explores the codebase for context on each task instead of carrying learning between tasks, and skills apply reusable instructions the customer writes, which the agent does not update.

Sourcedocs.lovable.dev projects/history, drafts, projects/chat, knowledge, cross-project-referencing, agent-mode and skills pagesread 2026-08-31

Plan mode lets a builder think a change through with the agent, which only analyzes and replies and does not run tools, write files or deploy, and moving from Plan to Agent asks for confirmation before implementation starts. Agent mode then makes the changes.

Production stays apart from the work: each finished task updates a private preview and saves a version, the live app changes only when someone clicks Publish, and any earlier version can be restored and republished. Outside assistants change code only through a full Blink agent turn, since the MCP server has no file write tool, and a viewer's connection is read only. Claw agents act on their own, with the secrets vault setting what each one can reach.

Sourceblink.new/docs/reference/modesread 2026-10-09

Plan mode investigates the project and writes a plan the user reviews, edits and approves before any code is written, and Lovable says Plan mode never modifies code. It is one of three modes the user picks, and Build mode applies changes directly, so the approval sits in an optional mode, not in the build path. Project monitoring findings are fixed only when the user asks. Workspace admin controls, integration admin controls, groups and project visibility settings limit who can do what.

Sourcedocs.lovable.dev plan-mode and project-monitoring pagesread 2026-09-29

SOC 2 is in progress and not yet complete. The DPA sets out TLS 1.2 or higher with HSTS in transit and AES 256 or equivalent encryption at rest, and, for the company's own production systems, role based access, single sign on, mandatory multi factor authentication, central application and access logs and audit logging on privileged operations, with breach notice within 72 hours.

Inside a project, one Owner controls visibility, Admins and deletion, Admins edit with the AI, invite people and publish, and Users can only view. Both roles can be invited on every plan, Free included, with no cap on numbers, and Business adds access levels set per project. None of the plans lists single sign on for logging in to Blink.

Sourceblink.new/dparead 2026-10-09

Platform controls include a trust center, SAML single sign on, SCIM provisioning, two factor authentication, workspace identity and identity reuse, groups and people access controls, integration admin controls, project visibility settings and Enterprise audit logs.

Enterprise materials describe centralized identity, granular access controls and security oversight across the workspace. Business tier has a data opt out setting, and secrets and build secrets are kept separate from generated code.

Security scanning of the generated app is separate, through a security center, security insights, sensitive data scanning and Aikido and Wiz integrations.

Sourcedocs.lovable.dev trust-center, saml-sso, business/sso, business/scim, two-factor-authentication, workspace-identity, groups, people, admin-controls, business/data-opt-out and secrets pagesread 2026-08-31

Every finished task saves a version with a screenshot, a generated description of the change, a timestamp and, for projects connected to GitHub, a commit SHA, so a builder can see what the agent changed and when a problem first appeared, then restore a working state. Outside assistants can read the version list, the source tree and a diff between versions over MCP.

For apps with a Blink Backend, the Backend tab shows every request live with its route, status code, response time and any error, and function logs can be pulled over MCP. Whether the build agent's individual tool calls are kept as a trace, or a workspace keeps an audit log of agent activity, is unclear.

Sourceblink.new/docs/launch/publishread 2026-10-09

Enterprise audit logs record actions taken by workspace members and which client each came from (Web, Desktop, iOS or Android), filterable by client or by member, with earlier entries marked Unknown. Dedicated pages cover project monitoring, logs, project usage, analytics and security insights. Build mode shows tasks as work proceeds, and project history records changes to a project. Audit logs are listed among Enterprise workspace capabilities, alongside security oversight across the workspace.

Sourcedocs.lovable.dev audit-logs, project-monitoring, logs, project-usage, analytics and security-insights pages, changelog and lovable-for-enterpriseread 2026-08-31

Core platform data, app databases on Turso, sign in and the build sandboxes sit in the United States on a hosted service. API servers run in the US, the Netherlands and Singapore with requests handled by the nearest one, and Claw agent machines run on Fly.io in US cities, Amsterdam, Frankfurt or London, with each agent's data stored where it runs. Customers do not pick a region.

The way off the platform is the code: web apps are standard React and TypeScript on Vite and mobile apps are React Native with Expo, a code download costs 5 credits on Starter and Pro and nothing on Max, and projects sync both ways with GitHub, with the agent's own Git operations coming on Pro, so the code can be taken elsewhere.

Sourceblink.new/dparead 2026-10-09

A default hosting region is set in Settings, under Security and compliance, Privacy and security, choosing Americas, Europe or Asia Pacific. On Business and Enterprise workspaces, admins can require a default region for every new project, after which members cannot choose a different one, and existing projects keep their original region.

Country regions including Germany, Japan and United States East are available on Enterprise by request, and Enterprise materials list regional code hosting. Lovable Cloud hosts apps with custom, verified and transferable domains, and two way GitHub sync and external deployment guidance let the app be hosted elsewhere.

Sourcedocs.lovable.dev privacy-and-security-settings, cloud, hosting, custom-domain, github and external-deployment-hosting pages, lovable-for-enterpriseread 2026-08-31

Blink Claw ships four named agents, each with its own role, instructions and recommended model. Gerald works as a chief financial officer on financial models, books and taxes, and Jamie as an executive assistant on morning briefings, tasks and email drafts.

Alex researches prospects and handles outreach and follow ups as a sales development rep, and Maya triages an inbox and drafts replies.

For apps, step by step tutorials walk through building a CRM, an analytics dashboard, a project manager, an online store, a course platform and several AI tools, and any public project can be remixed as a starting point.

Sourceblink.new/clawread 2026-10-09

Business tier includes design templates, alongside a managed registry, a remix path for starting from an existing project, a prompting library, skills with reusable instructions, and design systems supplying customer components. Video tutorials and an idea to app guide cover getting started. There is no catalog of finished apps published by Lovable.

Sourcedocs.lovable.dev business/design-templates, managed-registry, projects/remix, prompting-library, skills and design-systems pagesread 2026-08-31

Auto, the recommended setting, routes simple interface changes to fast models, complex features to advanced ones, debugging to reasoning models and design work to models that read images.

A builder can switch Auto off and pick the build agent's model directly from Google (Gemini 3 Pro and Flash), OpenAI (GPT-5.2 and GPT-5.1), Anthropic (Claude Opus, Sonnet and Haiku 4.5), xAI (Grok Code Fast) and Z.ai (GLM 4.6), with advanced models included from the Pro plan and costing more credits per request.

Claw agents choose separately from 13 models, Claude Sonnet 4.6 by default alongside GPT-5.4, Gemini 3.1 Pro, DeepSeek, Kimi and GLM, and can switch at any time. The AI Gateway's models serve the apps Blink builds rather than the builder.

Sourceblink.new/docs/reference/modelsread 2026-10-09

The builder has no model selection, model picker, bring your own key or provider setting, including in advanced settings, workspace admin settings and account settings. The model related integrations, Fireworks, Replicate, Perplexity and Gemini Enterprise, and an AI feature among the Cloud backend pages give model access to the app being built, not a choice over the model that powers Lovable.

Sourcedocs.lovable.dev sitemap inventory, advanced-settings, workspace-admin-settings, lovable-account-settings and features/ai pagesread 2026-08-31

A remote MCP server at blink.new/mcp, signed in with OAuth and bound to one workspace, carries scopes for reading the workspace and projects, writing projects and running builds.

Its 37 tools cover projects, the database, backend logs, builds, source and versions, publishing, and skills and connectors, so an assistant can start a build, answer the agent's questions, roll back to an earlier version and publish, and setup is laid out for Claude, Claude Code and ChatGPT.

Billing, workspace deletion and ownership transfer stay out of reach, and adding secrets or switching models has to happen in the browser. Separately, the AI Gateway API, reached with workspace API keys, gives code chat completions, media generation, web search and file upload.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

Lovable has its own API and MCP server. Agent integrations turn a published Lovable app into an MCP server that ChatGPT, Claude and other assistants can use, with configurable tools, sign in, permissions and access. Custom MCP servers, MCP registries, a create connector path and an any API route cover other services. Two way Git sync with GitHub and GitLab, including self managed and dedicated GitLab, exports the full codebase, and desktop, mobile and Slack surfaces extend access to the platform.

Sourcedocs.lovable.dev lovable-api, lovable-mcp-server, agent-integrations, custom-mcp, mcp-registries, create-connector, any-api and git-sync-overview pagesread 2026-08-31

Each finished task runs a lint check and a build before the preview updates and a version is saved, and preview errors are surfaced to the agent and, over MCP, to outside assistants. When something breaks, the agent investigates in chat before changing code, and an earlier version can be restored. In mobile apps, features such as the camera, health data, push notifications and haptics only behave correctly on real hardware, so Blink points builders to testing on a phone through Expo Go. Whether the agent writes and runs its own tests for the app is unclear.

Sourceblink.new/docs/launch/publishread 2026-10-09

Browser testing has the platform use the customer's app in a real browser running in a virtual environment, clicking buttons, filling forms, navigating pages and checking real user behavior with screenshots across screen sizes. It returns a verdict.

A Details view shows the steps taken and summarizes what worked and what did not, and the pattern is reproduce, fix, then verify. Where test and live environments are turned on, it runs against the project preview in the test environment, so the check happens before the change reaches anyone. The check is Lovable's own, run against the customer's app before release.

Sourcedocs.lovable.dev browser-testing page and test-and-live-environments documentationread 2026-08-31

Claw agents come with a web browser beside Python, Node.js and bash, and browsing is part of the jobs they take on, such as prospect research, morning briefings and inbox work. Whether they can click through pages, fill in forms or work inside sites that need a login is unclear. The app build agent works through code, its preview and the build tools rather than operating a browser or a desktop.

Sourceblink.new/clawread 2026-10-09

Browser testing and the preview toolbar run and display the app the agent has built, which checks the agent's own output, not third party software. Firecrawl and Apify integrations retrieve web content over HTTP, which is scraping, not computer use. All outside actions run through connectors, the any API route, custom MCP servers or MCP registries, all programmatic interfaces. There is no browser navigation, form filling, screen control or computer use.

Sourcedocs.lovable.dev browser-testing, preview-toolbar, projects/preview, firecrawl and apify pages plus sitemap inventoryread 2026-08-31