| Primary job | Conversation-led websites and data-backed frontend apps, isolated preview and source handoff. | Agent-led full-stack web and mobile app building. Source | AI builder for websites and full-stack web apps. Source | Integrated AI app building, hosted backend and data management. Source | Browser-based AI website and application development. Source | AI UI and full-stack app development by Vercel. Source | Agent-assisted application building and development workspace. Source | AI-assisted coding environment for developer-led software work. Source | Visual website design and managed publishing. Source | Visual website platform, CMS and managed publishing. Source |
|---|
| Paid entry plan | Plus $10/month; individual source unlock $4.99 once per project. | Standard displays $20/month equivalent billed annually; monthly checkout is unverified here. Source | Pro 100: $25 monthly or $250 annually upfront. Source | Starter $192/year; GitHub-listed Builder $480/year, annual billing. Source | Entry Pro $25/month, billed monthly. Source | Plus is advertised at $30/user/month. Source | Core exists; verify its current price at checkout. Source | Plus $8 monthly / $80 annually; Cursor-model allowance, no third-party models. Source | Basic $10/month equivalent, billed yearly ($120 upfront). Source | Basic site $15/month billed yearly ($180 upfront). Source |
|---|
| Free starting point | $0 plan with limited included AI usage; source stays locked until entitled. | Free tier exists; official free-credit descriptions differ. Source | Free plan includes capped daily build grants and limited Cloud/app-AI grants. Source | Free includes 25 monthly message credits and 100 integration credits. Source | Free includes 1M monthly tokens with a 300K daily limit. Source | Free lists seven daily messages, Design Mode, Vercel deployment and GitHub sync. Source | Starter provides limited AI and a time-limited published-app allowance. Source | Free has limited Agent and Chat requests. Source | Free Framer domain, limited bandwidth and trial AI credits. Source | Starter includes two static pages and a Webflow.io domain. Source |
|---|
| Source access | Inspection and raw source require a permanent project unlock. | Code view; GitHub save on Standard and above. Source | Repository sync is available; direct download depends on plan. Source | In-app code editing; repository workflows through Base Code. Source | Code view and a downloadable project are documented. Source | Code viewer, repository integration and export. Source | Development workspace contains editable project files. Source | Read and edit project files directly in the Agent workflow. Source | Work in Framer's visual project and supported code components. Source | Visual designer; code export is a paid Workspace feature. Source |
|---|
| Code export | Unlocked ZIP includes source, project images, bundled fonts and licenses. | Save source through GitHub; copy individual files in Code view. Source | Export source and move hosting; services require separate migration. Source | Advertises ownership and two-way GitHub source export; plan conditions apply. Source | Download a project or use GitHub for source handoff. Source | Source can be exported and deployed outside Vercel. Source | Plan source, dependencies and service data as separate handoff items. Source | Project files are edited in the development workspace; no per-site source unlock. Source | Officially no HTML export for independent self-hosting. Source | HTML/CSS/JavaScript/assets export with important feature exclusions. Source |
|---|
| Technical foundation | HTML/CSS/JavaScript; eligible projects use a Next.js static-export workflow. | Full-stack projects with backend and infrastructure support. Source | New apps use TanStack Start; older projects may use React and Vite. Source | App source plus managed Base44 backend services and developer tooling. Source | Web development environment with supported frameworks and packages. Source | React, Next.js, TypeScript, Tailwind and shadcn/ui workflows. Source | A general development platform with app runtime services. Source | Developer chooses the framework, dependencies and runtime. Source | Framer-managed rendering, assets and hosting infrastructure. Source | Visual site model; exported static assets differ from hosted app services. Source |
|---|
| Design workflow | Describe the audience and brand; add images and visual references. | Prompt-driven app creation and iterative requirements. Source | Prompting with a visual editor and preview environment. Source | AI chat, visual editor, design controls and project references. Source | Prompting, image references and visual edits. Source | Text, screenshots, Figma inputs and Design Mode. Source | Agent-led implementation from natural-language requirements. Source | Developer-led implementation with AI assistance. Source | Visual design canvas, CMS and AI-assisted work. Source | Visual styling, components, CMS and AI features. Source |
|---|
| Refinement | Chat edits, saved versions and mapped Inspect & Edit controls. | Agent changes and follow-up prompts. Source | Chat changes and repository-backed development. Source | AI edits and repository-based changes with a development preview. Source | Plan Mode, Code view, follow-up prompts and restoration. Source | Chat, code edits, versions and GitHub branches. Source | Effort-based Agent work and developer-controlled edits. Source | Agent edits and code review in a development workflow. Source | Edit the design and content within the platform. Source | Edit and publish through Webflow's design and content tools. Source |
|---|
| Preview and review | Interactive preview runs on a separate origin; review desktop and phone layouts. | Build and review an application before deployment. Source | Preview environments before publishing. Source | Preview changes and review branch-based repository work. Source | In-browser preview controls and project review. Source | Branch preview deployments and production review. Source | Development review and published deployment are separate stages. Source | Agent can run terminal commands and inspect applications through its browser tools. Source | Published site workflow; staging/branch features vary by plan. Source | Review a staged site before publishing changes. Source |
|---|
| Hosting | Publish Studio serves an explicitly published version; exported source can also run on another host. Service limits apply. | Managed deployment uses a separate credit allowance. Source | Managed Lovable hosting or your own infrastructure. Source | Apps use Base44 hosting and backend infrastructure. Source | Website hosting is included, with plan-dependent capacity. Source | Publishing deploys to a connected Vercel project. Source | Deployment resources have usage-based billing rules. Source | Plan production hosting independently from editor usage. Source | Managed hosting is part of the site plan. Source | Site plans provide managed hosting; Workspace billing is separate. Source |
|---|
| Custom domains | Verified custom domains are available for entitled projects through Publish Studio; external hosting has its own DNS workflow. | Custom-domain deployment is documented; check deployment charges. Source | Custom-domain workflow is documented; plan and DNS requirements apply. Source | Paid plans list domain connection; check exact plan and DNS setup. Source | Custom domains and branding removal on paid plans. Source | Custom domains are managed through the Vercel project. Source | Production domain setup belongs to the deployment workflow. Source | Configure domains through the selected hosting provider. Source | Paid plans support connecting your own domain. Source | Paid site plans support a custom domain. Source |
|---|
| Database and backend | Typed Uvilno.db collections, persistent CRUD and App Data; hosted services remain a dependency after export. | Backend and database workflows are part of the app platform. Source | Built-in Cloud backend with database, storage and compute billing. Source | Built-in entities, records and a data dashboard; test and production data controls. Source | Bolt Cloud databases and supported external providers. Source | Database and API integrations; provision services as needed. Source | Production databases, compute and network resources are metered. Source | Choose and operate backend/database providers yourself. Source | CMS collections with plan limits; external app services need integration. Source | CMS is in applicable site plans; its database is not included in code export. Source |
|---|
| Visitor authentication | Project-scoped managed visitor identities when enabled; not a portable identity database by ZIP alone. | Generated app login requires configuration and testing. Source | App authentication is part of the backend configuration. Source | App sign-in and role/access settings; data permissions require review. Source | Authentication integrations are part of the app-building workflow. Source | Implement app authentication with the chosen provider. Source | App authentication requires a configured and reviewed implementation. Source | Implement and configure an authentication provider. Source | Site password features differ from a full visitor-account application. Source | User account behavior does not transfer in a static code export. Source |
|---|
| Payments | Stripe test Checkout connector; live use depends on configuration and release availability. | App integrations require the relevant provider setup. Source | Payment integrations require provider credentials and testing. Source | Payments and Stripe setup are documented integrations, not a source-export entitlement. Source | Stripe integration is documented; configure your account. Source | Commerce setup can include Stripe or Shopify; claim/configure services. Source | Payment behavior needs provider integration, secrets and end-to-end testing. Source | Implement provider SDKs, server validation and payment flows. Source | Commerce and payment requirements need a specific supported integration. Source | Ecommerce functionality is excluded from the static source export. Source |
|---|
| Existing code and Git | GitHub import, push and pull for supported frontends; source pushes require unlock. | GitHub source handoff on Standard and above. Source | Two-way GitHub, GitLab and Bitbucket sync; existing-repo import differs. Source | GitHub integration on Builder and above; Base Code edits connected repositories. Source | GitHub import, sync and branch workflows. Source | GitHub-backed branches, pull requests and CI workflows. Source | Development workspace for maintaining application code. Source | Repository-centric work; Premium adds Origin hosting and Bugbot features. Source | Design platform rather than an arbitrary code-repository editor. Source | Static code export is distinct from ongoing repository-based app editing. Source |
|---|
| SEO workflow | Generated page metadata and structure need review; rankings and traffic are not guaranteed. | Review generated content, routes and metadata before launch. Source | SEO tools exist; review crawlability and final content. Source | Review generated pages and published metadata; ranking is not guaranteed. Source | Paid plans list SEO boosting; audit the actual published pages. Source | Framework metadata and rendered routes need your review. Source | Review generated routes, rendered metadata and public access. Source | Developer implements metadata, rendering and crawl controls. Source | Built-in SEO; inspect final metadata, links and content. Source | Platform SEO tools; review content and export behavior. Source |
|---|
| Usage limits | Finite AI usage on every plan. Unlimited source unlocks are not unlimited generation. | Standard includes 100 credits; additional credits can be purchased. Source | A shared credit balance funds build, runtime and supported integrations. Source | Separate message and integration credit allowances with plan-dependent limits. Source | Tokens are limited; large context and changes affect consumption. Source | Plus includes credits; model token rates and extra usage apply. Source | Agent effort and runtime resources are not unlimited. Source | Plan usage is limited; third-party models have separate usage charges. Source | AI credits, bandwidth, CMS and editor limits depend on plan. Source | Pages, bandwidth, AI and CMS limits depend on site/workspace plan. Source |
|---|
| Moving away | Static source can move to your host; managed auth, data, forms and payments may need migration. | Exported code excludes secrets and application data; migrate those separately. Source | Code and data can move; replace or reconfigure backend, AI and connector calls. Source | Source ownership is documented; migrate backend data and connected services separately. Source | Source can be self-hosted; migrate database and service dependencies too. Source | Exported code can move; reconfigure framework runtime and service integrations. Source | A migration must include runtime, environment variables and production data. Source | Project source remains yours; infrastructure and licenses still matter. Source | Independent source hosting requires rebuilding rather than native HTML export. Source | Static export can move; CMS, ecommerce, forms and other services need replacement. Source |
|---|
| Declarative data and studio | data/schema.json declares typed collections; App Data manages actual owned and shared records. | Database Viewer and generated backend; export records separately from code. Source | Built-in backend with database tables and record editing in the project tools. Source | Typed entities and visual record management are part of the built-in backend. Source | Bolt Cloud creates databases and provides a data table, logs and user tools. Source | Database integrations provision a chosen provider; generated application code uses that service. Source | Managed database development and deployment are documented platform capabilities. Source | Works with databases in your project; a managed app database is not established by this pricing page. Source | CMS collections organize published content; they are not a general app-record ORM. Source | CMS content records and APIs; a static code export excludes the hosted CMS backend. Source |
|---|
| In-app AI | Uvilno.ai.ask/json runs real owner-funded inference; 600-token replies and admission limits apply. | One-click LLM integration is listed; app configuration and usage still apply. Source | Managed app AI connector provides real model calls and workspace usage billing. Source | invokeLLM and app agents use supported managed model presets. Source | AI integrations can be implemented in the project; this review did not measure an app-AI proxy. Source | App AI can be implemented with model/provider services; verify runtime billing separately. Source | Agent-generated application integrations need their own runtime and provider configuration. Source | Coding-agent model access is distinct from app visitors' inference infrastructure. Source | AI design agents are listed; app-user inference is a separate integration question. Source | Webflow AI supports building/content workflows; visitor AI needs an app integration. Source |
|---|
| Database automations | Bounded create/update/remove rules and notifications commit atomically; inspect Automations & Logs. | Custom backend logic can be generated; an equivalent atomic rule contract was not measured here. Source | Backend functions and scheduled jobs are documented; execution differs from Uvilno's bounded atomic rules. Source | Scheduled, data-event and connector triggers; workflows are replacing automations. Source | Server functions and connected services can implement workflows; no atomic-rule equivalence is claimed. Source | Generated server code can implement workflows; no Uvilno-style rule parity was tested. Source | Application code and deployment services determine background-work behavior. Source | Cloud agent automations concern development; app database workflows remain project code. Source | Publishing and content tooling differ from arbitrary transactional app database rules. Source | CMS APIs and application integrations differ from a bundled per-record transactional rule SDK. Source |
|---|
| Role views and authorization | Guest/Member/Admin previews change presentation only; real visitor permissions remain server-enforced. | Emergent Auth supports visitor accounts; generated authorization needs testing. Source | Backend users and sign-in tools; actual access follows configured permissions. Source | App access and role settings; data permissions remain a separate security configuration. Source | Cloud authentication and user management; verify app-level authorization. Source | Application roles and authentication depend on generated code and connected providers. Source | Generated app authentication and access checks must be configured and tested. Source | Your application implements visitor roles; editor/team permissions are a different boundary. Source | Editor roles and site password protection are not per-record visitor authorization. Source | Site/Workspace governance is distinct from generated app visitor permissions. Source |
|---|
| Focused edit context | @file, @page, @db and inspected-element references guide bounded source retrieval with a repo map. | Agent chat and Code view provide project editing; no edit-time benchmark was run. Source | Chat, generated modules and repository sync; no same-brief timing benchmark was run. Source | Base Code edits connected repositories with branch previews and commit history. Source | Code view, prompting and GitHub version control; no fixed edit latency established. Source | Code changes and GitHub branches support precise development; no edit-speed ranking established. Source | An editable development workspace and Agent operate on the project codebase. Source | Repository-aware coding and agent tools in your development environment. Source | Visual design, components and overrides; native HTML source export is not supported. Source | Visual designer, code components and export rather than a source-first chat-only workflow. Source |
|---|
| Repair and interaction cost | Mapped visual edits cost 0% usage. Limited reproduced static-runtime repairs are platform-funded; ordinary AI edits are metered. | Testing, debugging and troubleshooting consume credits in the published credit model. Source | Build/chat and app runtime use the documented credit balance; check action-specific charges. Source | Building and live integration work use distinct message/integration credit allowances. Source | Reading and modifying project files consumes model tokens under its usage model. Source | Messages consume model-priced tokens/credits; Design Mode is a separate editing workflow. Source | Agent work uses effort-based billing; operating resources have their own charges. Source | AI pool and separately billed third-party model usage depend on the selected subscription. Source | Agents consume credits; editor/hosting charges follow their respective plan rules. Source | AI and hosting allowances vary by plan; verify the action and service being billed. Source |
|---|