Compare Uvilno and Webflow across site publishing, CMS, code export, workspace versus site billing, and practical source portability limits.
Uvilno provides conversation-led frontend generation, schema-declared app data and a $4.99 permanent source unlock for one project. Plus costs $10/month; Pro costs $20/month with unlimited source unlocks during the subscription. Generation and hosted services have separate limits.
The five criteria below allocate 100 possible points. Available documentation and recorded Uvilno checks establish some conditions; they do not establish equivalent performance across products. Overall scores remain unmeasured. Unknown evidence is not treated as a failed capability.
Published by Uvilno. Uvilno appears first as the publisher’s presentation order, not a measured rank. The weights express this publication’s engineering priorities.
| Criterion & weight | UvilnoPublisher | WebflowDocumented comparison |
|---|---|---|
| Code ownership & export cost25 possible points | 5 of 5 conditions documented An owned, unlocked project can export its runtime-appropriate source and referenced media. Inspect conditions0 unmeasured
| 2 of 5 conditions documented HTML/CSS/JavaScript/assets export with important feature exclusions. Inspect conditions3 unmeasured
|
| Database, accounts & app AI25 possible points | 5 of 5 conditions documented Uvilno.db CRUD and App Data use schema-declared, persistent app records. Inspect conditions0 unmeasured
| 0 of 5 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions5 unmeasured
|
| Targeted edit precision & speed20 possible points | 2 of 4 conditions documented @file, @page, @db and bounded repository retrieval supply explicit context. Inspect conditions2 unmeasured
| 0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured
|
| No-usage editing & recovery15 possible points | 3 of 3 conditions documented Mapped direct text, link and color changes use 0% model usage; unsupported computed elements use the normal scoped-edit path. Inspect conditions0 unmeasured
| 0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured
|
| Multi-page & interactive applications15 possible points | 2 of 3 conditions documented Contract-first route plans and reusable modules support multi-page frontends; saved legacy and eligible Next.js projects retain their respective runtimes. Inspect conditions1 unmeasured
| 1 of 3 conditions documented Visual website platform, CMS and managed publishing. Inspect conditions2 unmeasured
|
| Comparable overall score | Not measured | Not measured |
Drag the slider, use the arrows, or scroll within the table.
Each listed condition has a five-point allocation. This page records evidence, not awarded performance points. “Documented” identifies a stated capability with its requirements. “Recorded Uvilno check” identifies a named first-party fixture; it is not independent comparative testing. “Unmeasured” leaves the condition open. Source-access purchases, annual subscriptions and operating services are different costs.
Build the same app, obtain its complete source, record the actual purchase, and rebuild on a separate host. Test continued source access and document the backend services that still need migration.
Create, edit and remove the same records; reload; repeat with another account; check record permissions; run a real app-AI request and inspect a triggered automation. Record each managed or external dependency.
Apply the same specified changes to matched projects. Compare exact file deltas, verify the rendered target and unchanged routes, and record end-to-end timings including verification. Publish failures as well as successes.
Make the same direct edit and introduce the same reproducible fault. Inspect actual usage ledgers, repair limits and saved-version behavior. A limited free path must not be described as unlimited free coding.
Build and navigate the same route plan, exercise state across pages, then measure frame time and input response on named devices. Framework support or an attractive screenshot does not establish a universal 60 FPS result.
A published 4–8 second edit claim needs timing data. A 60 FPS claim needs a named workload, device and frame-time record. Neither is inferred from feature availability, code export or a screenshot. The recorded checks and open evaluation protocol describe the current measurement boundary.
Key takeaway, October 2026. Uvilno combines typed hosted data, app AI and bounded transactional automations with a permanent $4.99 source unlock. Choose it when that frontend-and-managed-services contract fits your app; compare Webflow's runtime, service limits and handoff against the same requirements.
Where Webflow fits. Choose Webflow when a visual website system, structured CMS content and an ongoing managed publishing workflow are the main requirements.
Where Uvilno fits. Choose Uvilno when you want to build by conversation and purchase a permanent source entitlement for an individual project.
Webflow separates site hosting plans from workspace features such as code export. Price the specific combination you need rather than assuming every paid site can export all its services.
Feature summaries reflect the linked documentation. “Requires configuration” is a responsibility to plan for, not a claim that the other product cannot do it.
| What to compare | Uvilno | Webflow |
|---|---|---|
| Primary job | Conversation-led websites and data-backed frontend apps, isolated preview and source handoff. | Visual website platform, CMS and managed publishing. [1] |
| Paid entry plan | Plus $10/month; individual source unlock $4.99 once per project. | Basic site $15/month billed yearly ($180 upfront). [1] |
| Free starting point | $0 plan with limited included AI usage; source stays locked until entitled. | Starter includes two static pages and a Webflow.io domain. [1] |
| Source access | Inspection and raw source require a permanent project unlock. | Visual designer; code export is a paid Workspace feature. [2] |
| Code export | Unlocked ZIP includes source, project images, bundled fonts and licenses. | HTML/CSS/JavaScript/assets export with important feature exclusions. [2] |
| Technical foundation | HTML/CSS/JavaScript; eligible projects use a Next.js static-export workflow. | Visual site model; exported static assets differ from hosted app services. [2] |
| Design workflow | Describe the audience and brand; add images and visual references. | Visual styling, components, CMS and AI features. [1] |
| Refinement | Chat edits, saved versions and mapped Inspect & Edit controls. | Edit and publish through Webflow's design and content tools. [1] |
| Preview and review | Interactive preview runs on a separate origin; review desktop and phone layouts. | Review a staged site before publishing changes. [1] |
| Hosting | Publish Studio serves an explicitly published version; exported source can also run on another host. Service limits apply. | Site plans provide managed hosting; Workspace billing is separate. [1] |
| Custom domains | Verified custom domains are available for entitled projects through Publish Studio; external hosting has its own DNS workflow. | Paid site plans support a custom domain. [1] |
| Database and backend | Typed Uvilno.db collections, persistent CRUD and App Data; hosted services remain a dependency after export. | CMS is in applicable site plans; its database is not included in code export. [2] |
| Visitor authentication | Project-scoped managed visitor identities when enabled; not a portable identity database by ZIP alone. | User account behavior does not transfer in a static code export. [2] |
| Payments | Stripe test Checkout connector; live use depends on configuration and release availability. | Ecommerce functionality is excluded from the static source export. [2] |
| Existing code and Git | GitHub import, push and pull for supported frontends; source pushes require unlock. | Static code export is distinct from ongoing repository-based app editing. [2] |
| SEO workflow | Generated page metadata and structure need review; rankings and traffic are not guaranteed. | Platform SEO tools; review content and export behavior. [1] |
| Usage limits | Finite AI usage on every plan. Unlimited source unlocks are not unlimited generation. | Pages, bandwidth, AI and CMS limits depend on site/workspace plan. [1] |
| Moving away | Static source can move to your host; managed auth, data, forms and payments may need migration. | Static export can move; CMS, ecommerce, forms and other services need replacement. [2] |
| Declarative data and studio | data/schema.json declares typed collections; App Data manages actual owned and shared records. | CMS content records and APIs; a static code export excludes the hosted CMS backend. [2] |
| In-app AI | Uvilno.ai.ask/json runs real owner-funded inference; 600-token replies and admission limits apply. | Webflow AI supports building/content workflows; visitor AI needs an app integration. [1] |
| Database automations | Bounded create/update/remove rules and notifications commit atomically; inspect Automations & Logs. | CMS APIs and application integrations differ from a bundled per-record transactional rule SDK. [1] |
| Role views and authorization | Guest/Member/Admin previews change presentation only; real visitor permissions remain server-enforced. | Site/Workspace governance is distinct from generated app visitor permissions. [1] |
| Focused edit context | @file, @page, @db and inspected-element references guide bounded source retrieval with a repo map. | Visual designer, code components and export rather than a source-first chat-only workflow. [1] |
| Repair and interaction cost | Mapped visual edits cost 0% usage. Limited reproduced static-runtime repairs are platform-funded; ordinary AI edits are metered. | AI and hosting allowances vary by plan; verify the action and service being billed. [1] |
Drag the slider, use the arrows, or scroll within the table.
Uvilno source: plans and source entitlement, with implementation boundaries described on this page. Always review the actual exported project and configured services.
Uvilno's October 27 integration run exercised real hosted services with a code-authored fixture. It was not an independently scored CRM-generation contest or a test of Webflow. We publish the boundary so a passing SDK check cannot be mistaken for a universal build-completion rate.
| Check | Uvilno: observed result | Webflow |
|---|---|---|
| Saved data | A task was persisted through the actual SDK and recovered after an iframe reload. | Not measured in this run. Official capability documentation is linked separately. |
| Database effects | Task creation wrote an activity record and notification in the same transaction. | Not measured in this run. Official capability documentation is linked separately. |
| Account boundaries | Guest/Member/Admin view changes preserved the real visitor and creator identities. | Not measured in this run. Official capability documentation is linked separately. |
| Targeted recovery | A reproduced static ReferenceError was repaired in app.js and browser-checked without a customer usage-ledger entry. | Not measured in this run. Official capability documentation is linked separately. |
Drag the slider, use the arrows, or scroll within the table.
Real free-model text and JSON app inference also passed locally; the production replay verified persistence, automations and isolation without additional inference. No cross-vendor latency, aesthetic score, completion percentage or total operating cost was measured. Read the machine-readable evidence and methodology.
Webflow's pricing distinguishes a site's hosting capabilities from workspace capabilities. A Basic site subscription should not be presented as if it automatically includes every code-export feature. Uvilno uses an individual permanent source unlock or included subscription entitlements. Compare the purchase that supplies your actual deliverable: a hosted site, a CMS workflow or exported source.
Webflow documents exclusions from exported code, including its CMS database and ecommerce functionality. A static frontend can still be a useful deliverable, but editorial publishing and application services require another solution after migration. Uvilno's source exports have a related boundary: calls to managed auth, collection or payment services need configuration or replacement.
Webflow may fit a team that expects non-developers to maintain structured content and publish repeatedly through a visual system. Uvilno may fit an owner who wants conversational website changes and a source handoff. Write down who updates the site, how often, what content is structured and how release approval works. Those needs can matter more than an initial subscription difference.
Published plan prices are a starting point. Add the costs your actual website needs; this is a budget worksheet, not a price quote or a measured savings claim.
Zero in an optional field means that cost is excluded from this worksheet. It does not mean unlimited or free generation, provider usage, hosting or domains. Taxes, currency conversion and labor are excluded.
Source unlocks persist. This worksheet models new projects at an even monthly pace; Plus's two included unlocks must be used in their paid month. Existing unlocked sites do not require another unlock.
Configured monthly AI capacity: Pro is 2.5× Plus; Ultra is 5× Pro. These are usage-capacity ratios, not a guaranteed number of builds.
Basic site: $15/month billed yearly ($180 upfront). This models hosted publishing, not a paid export workspace. Code export requires a qualifying paid Workspace plan. Core Workspace is separately advertised at $19/month billed yearly; CMS and other services are not exported as a working backend. Pricing checked 2026-10-27. See the official pricing source.
A paid Site plan does not by itself grant code export. Webflow documents export as a qualifying paid Workspace feature, billed separately from site hosting.
No working Webflow CMS database or ecommerce service is included in the static code export. Other platform features and localized content also have exclusions; review the official export policy for your project.
The checked Basic Site price is $15 per month billed yearly. That is $180 upfront for hosted Basic publishing, before tax, add-ons or a separate export-enabled Workspace plan.
Publish Studio can serve an explicitly published version, and entitled projects can connect a verified custom domain. Every plan still has finite AI usage and service limits. A permanent source unlock grants source access, not unlimited hosting or generation. External hosting and managed-service migration need separate planning; payments currently use test workflows.
A product comparison can narrow the options. Your own content, constraints and review decide the fit.
The brief is preloaded for you to review. AI generation starts only when you send it. Included usage is limited; source access requires unlock.
Official vendor documentation checked on 2026-10-27. Billing conflicts and unavailable prices are disclosed above. Uvilno prices follow our current plan configuration; our implementation is the source for its documented boundaries.
Follow the data model, account boundary and source handoff before choosing a builder.