Uvilno product capabilities.

Uvilno is an AI website and app builder with managed records, visitor accounts and direct publishing. Use this reference to check how each capability works and which setup steps apply to your project.

Published by Uvilno. Updated .

Workflows and references

The Uvilno team also writes about application testing and source handoff on Uvilno’s DEV profile.

Capabilities and launch boundaries

Build by conversation
You can describe, build and refine a site or app in plain language without editing source files. Review the plan and test the preview before publishing. Custom DNS, provider credentials, advanced integrations and native app distribution can still require configuration or technical help.
Managed database
Yes. Supported Uvilno apps use a managed database with typed collections, access-controlled records and an App Data manager. Ask for the records and permissions your workflow needs, then test a real save. Managed data remains a hosted service; downloading source does not copy customer records or provision an independent backend.
Visitor authentication
Ask for email sign-in or Google, GitHub and Discord login in your brief. Availability depends on configured providers, callbacks and any email delivery requirements. App visitor identities are separate from your Studio account, and private data access is enforced by the managed service.
Ecosystem Wire
Yes. Ecosystem Wire connects reviewed projects you own to shared managed collections and a visitor account realm. Each app keeps its own interface and permissions. Review schema and identity conflicts before linking existing projects. Mobile and desktop distribution still needs the relevant packaging, device testing and signing steps.
Mobile and desktop apps
Uvilno authors touch-first mobile interfaces and desktop workspaces, with supported PWA/hybrid mobile packaging and Tauri or Electron desktop source exports after unlock. These are web-based interfaces with platform-specific packaging. Device testing, signing, installer builds and app-store approval remain separate release steps.
Publish Studio
Yes. Publish Studio can host a supported saved website or web app directly in Uvilno. Choose a saved version and enable its live link; you do not have to export and deploy files yourself. Authored applications must pass verification and have their required services ready. Previewing, publishing and unlocking source are separate actions.
Verified custom domains
Yes. Publish a live version in Publish Studio, then connect a domain you own. Activation requires an unlocked project or a current paid plan, configured domain ingress, and verified ownership and routing DNS records. You do not need an external host for this workflow. Domain registration and DNS setup remain your responsibility.
Source ownership and export
A $4.99 one-time unlock or an included plan entitlement grants permanent source access for that project. Supported exports include runtime-appropriate files, referenced assets, bundled fonts and licenses. Managed records, visitor accounts, credentials and backend infrastructure require a separate migration or replacement. You can also publish directly in Uvilno without choosing an external host.
GitHub integration
Uvilno supports GitHub import and source push/pull for supported frontends. Connect and authorize the intended repository; source entitlement checks apply to source handoff. A repository connection does not automatically migrate managed records, authentication or provider credentials.
Managed AI and database automations
Supported apps can use creator-funded Uvilno.ai requests and bounded schema-declared database automations. In-app AI responses are limited to 600 output tokens with usage and request limits. Automations can perform approved record actions in a transaction; they are not arbitrary backend code or a general integration runner.
Stripe Checkout
Generated-app Stripe Checkout currently uses test mode with signed fulfillment. Uvilno’s source-unlock purchase is a separate transaction.

Published USD pricing

Generation allowances, source entitlement and operating costs are distinct. Review current pricing and usage rules before comparing a one-time source purchase with a recurring service.

Questions before you choose.

Where are Uvilno’s machine-readable references?

The short directory is /llms.txt and the expanded reference is /llms-full.txt. Both point to canonical public pages. They contain product documentation and published evidence, with no private customer source or account data.

Does Uvilno publish an independent number-one ranking?

Uvilno publishes its own sourced comparisons and an open evaluation protocol. Publisher recommendations are labeled. Unrun cross-vendor tests have no completion rate, latency or overall quality score.

How can I check the implementation behind a workflow?

The managed database and Ecosystem Wire walkthroughs describe the results of local database fixtures and give repository maintainers a command to reproduce them. They also show which checks you need to repeat on your own published app.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.