Lovable

HostedAI app builder

Build something Lovable

Homepage Docs Pricing

Scanned 14 Oct 2026 · Schema v5 · features v21

From: €25/mo
Per-workspace credit subscription with one balance for build, chat, Cloud, app AI and connectors; usage-specific grants applied first. Unlimited collaborators, not per-seat.
Free tier: Yes
No card required.
Isolation: Not disclosed
the public docs do not say
Regions: 3
Lovable Cloud data hosting · Lovable Cloud data hosting · Lovable Cloud data hosting
Capabilities: 25 / 61
9 partial · 12 fail · 0 not assessed
Agent readiness: 10/10 · 8/11
read · drive, pre-login surface

Advertised for

AI generated web apps · AI generated websites · Internal tools · Dashboards · Interactive prototypes · Mvps · Landing pages · Shopify storefronts · Lightweight saas

Built for

Non-technical users, then technical

· Plain-language generation; no technical knowledge needed on current pricing page.
· Workspace-shared credits and private projects support non-developer teams.

01 Pricing Per-workspace credit subscription with one balance for build, chat, Cloud, app AI and connectors; usage-specific grants applied first. Unlimited collaborators, not per-seat.

Tier	EntryFree	Pro	Business	TopEnterprise
Price	€0	€25/month	€50/month	Contact sales / platform fee

workspace subscription plus heterogeneous usage credits·Card required: No·docs.lovable.dev

Overages: Top-ups and auto top-up use shared credit balance; build/Cloud/AI/connector rates differ by workload and plan. Storage charges continue while backend paused.

02 Website design Desktop public website · assessed 14 Oct 2026

Partial assessment — some pages could not be captured.

Documentation uses a white, spacious three-column layout with restrained sans-serif hierarchy, blue navigation accents and a colorful product screenshot. Fresh anonymous landing and pricing coverage was unavailable.

Corporate

Landing page: unavailable
Pricing: unavailable
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

Persistent managed database and object storage; project version history, remix, and two-way GitHub/GitLab/Bitbucket sync.

Snapshots / forks

Project history/revert, remixes and drafts; application copies, not running-instance snapshots.

Resources & limits

Storage

Managed Cloud object storage and database disk; storage billed while Cloud paused; separate export required for stored files.

Limits & quotas

Unified credits for building, chatting, hosting/Cloud, app AI and paid connectors. Free grants: 5 build credits/day capped at 30/month, 20 Cloud/month, 4 AI/month, 1 connector/month. Pro/Business start at 100 general credits/month plus uncapped daily build grants.

GPU

Access

Deploy interface

dashboardmcpapitemplate

SDK languages

None

Network & secrets

Egress controls

No documented user-configurable outbound firewall on default managed apps; connector stable outbound IP allowlisting and Enterprise AWS VPC connectivity are separately scoped.

Secrets

Cloud secrets encrypted at rest and scoped by role/environment; gateway connector credentials stay outside project behind opaque connection keys.

Bring your own cloud

Enterprise private preview: deploy app data plane into your own AWS account.

Placement & use

Jurisdiction

AmericasEuropeAsia Pacific

Advertised workloads

AI generated web appsAI generated websitesInternal toolsDashboardsInteractive prototypesMvpsLanding pagesShopify storefrontsLightweight saas

04 Capabilities 25 pass · 9 partial · 12 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 1/4

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not applicable

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Partially supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not applicable

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Partially supported

GPU computeGPU-backed instances available.

Not applicable

Multi-regionCompute placeable in more than one geographic region.

Partially supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not applicable

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not applicable

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not applicable

Networking & delivery 5/7

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not applicable

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Partially supported

Email send / receiveSend and/or receive email from the workload.

Supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not applicable

Developer access 1/6

Public APIDocumented programmatic API.

Partially supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Not supported

SDKOfficial client library/libraries.

Not supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Partially supported

Private container registryHosted private image registry.

Not applicable

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not applicable

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 8/11

Built-in coding agentShips a first-party AI coding agent in the product.

Supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Partially supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not applicable

Data 2/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 3/5

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not applicable

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 5/9

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Workspace Security center (scans generated apps for vulnerabilities / RLS / secrets)app-security-scanner
“Basic security scan on each publish; on-demand deep scans; dependency checks; security center and publishing controls.” docs.lovable.dev
Connect-your-own-backend (bring an existing Supabase project instead of Lovable Cloud)byo-backend-connect
“'Connect to Supabase' — new projects choose Lovable Cloud OR Supabase; existing Supabase projects continue unchanged.” docs.lovable.dev
Chat connectors / curated app-integration catalog (Stripe, Mailgun, Google Maps, Snowflake, Semrush, Microsoft 365, WordPress, Ashby, GSC)app-integration-catalog
“A catalog of first-party connectors the generated app can use (payments, email, maps, data warehouse, CRM, CMS).” docs.lovable.dev

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10/10

7 full · 3 partial · 100% of applicable checks

llms.txt
Supported
“Substantive apex llms.txt and 65358-byte docs index fetched.”
llms-full.txt
Supported
“Comprehensive docs.lovable.dev/llms-full.txt fetched, 4082178 bytes; pointer retained.”
robots.txt AI policy
Supported
“robots.txt explicitly ALLOWS AI UAs (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, Applebot-Extended) with Allow: /”
JSON-LD
Partially supported
“Rendered homepage HTML includes WebSite and Organization; no rich Product/SoftwareApplication offers.”
Sitemap
Supported
“GET /sitemap.xml 200 — a sitemap index of 11 locale sitemaps (en, pt-br, de, fr, es, it, hi, id, th, ko, ja)”
Meta tags
Supported
“Descriptive <title> + meta description + og:title/og:description/og:image + twitter:card”
Markdown negotiation
Supported
“https://docs.lovable.dev/introduction/welcome Accept: text/markdown returns clean markdown; .md content also fetched.”
Content efficiency
Not assessed
“Direct homepage HTTP 403. Recovered rendered DOM ratio 1.779% is not the raw server HTML measurement; probe unavailable, excluded.”
Docs discoverable
Partially supported
“Current landing Resources/Learn docs links found in footer, not first-class header documentation nav.”
Machine-readable pricing
Supported
“Structured pricing tiers with prices + credit allotments (some detail in RSC, but tiers/prices are clearly parseable)”
No anti-bot wall
Partially supported
“Direct landing HTTP 403; foxcrawl markdown and HTML recovered content. Other public docs and pricing fetched successfully; intermittent public block.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

8/11

6 full · 2 partial · 73% of applicable checks

Public API
Supported
“https://docs.lovable.dev/integrations/lovable-api.md: documented stable /v1 projects/deployments/workspaces/security API; Business/Enterprise gated.”
OpenAPI spec
Supported
“https://api.lovable.dev/v1/openapi.yaml fetchable linked specification; full artifact pointer.”
MCP server
Supported
“Hosted MCP server documented at mcp.lovable.dev (OAuth; tools create_project/deploy_project) + .well-known/mcp at the docs subdomain”
SDK packages
Not supported
“No official client SDK”
Auth documented
Supported
“https://docs.lovable.dev/api-reference/introduction.md: Lovable-API-Key header, scopes, verified email, OAuth and versioning documented.”
Self-serve credentials
Partially supported
“https://docs.lovable.dev/features/api-keys.md: Business/Enterprise owners/admins create workspace keys in dashboard; human approval not programmatic issuance.”
Webhooks
Not supported
“No documented first-party platform webhooks (app-level Stripe/integration webhooks aside)”
CLI tool
Not supported
“No official CLI”
Error model
Supported
“https://docs.lovable.dev/api-reference/introduction.md: JSON type/title/status/request_id/detail/errors/props error envelope.”
Rate limits documented
Supported
“https://docs.lovable.dev/api-reference/introduction.md: sliding windows, X-RateLimit-Limit/Remaining/Reset and Retry-After headers.”
Agent config files
Partially supported
“https://docs.lovable.dev/features/skills.md: one reusable markdown skills surface; no agents.md or well-known agent found.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 2

Claude Code Anthropic
Supported
“Lovable MCP server 'Supported AI clients: ChatGPT, Claude (Claude Desktop ... and claude.ai), Claude Code, Cursor, VS Code' — the agent can 'create projects, send messages to Lovable, inspect code, deploy apps' via create_project/deploy_project.”
Source docs.lovable.dev
Cursor Anysphere
Supported
“Lovable MCP server lists Cursor among the supported OAuth clients that can manage Lovable projects through natural language.”
Source docs.lovable.dev

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 4

ISO/IEC 27001
certifiedhosted
“ISO 27001:2022 - Certificate of Registration”
Source trust.lovable.dev
SOC 2 Type II
certifiedhosted
“SOC 2 Type II; completed observation period February 1 to August 1, 2026; release October 5, 2026.”
Source trust.lovable.dev
SOC 2 Type I
certifiedhosted
“SOC 2 Type I - 2026 audit report listed.”
Source trust.lovable.dev
GDPR
self-attestedhosted
“GDPR listed in rendered Compliance section; privacy policy and DPA available.”
Source trust.lovable.dev

Regions 3

Lovable Cloud data hostingAmericas
Lovable Cloud data hostingEurope
Lovable Cloud data hostingAsia Pacific

Data residency, not full compute placement map. Country-specific Enterprise regions on request; private-preview BYOC workload regions selected through customer AWS account.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: Stockholm, Sweden
Founded: 2023
Team size: Not disclosed
Hiring: Actively hiring

Notable people

Anton Osika (co-founder and CEO)
Fabian Hedin (co-founder)

Activity

Last release: 2026-10-13 docs.lovable.dev
Last blog post: 2026-10-14 lovable.dev

Presence 12

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from lovable.dev's unauthenticated pages, docs, pricing and repository on 14 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All AI app builder products →