How does Uvilno's declarative database work?
A direct answer, the limits that matter, and a practical way to check the workflow.
Direct answer
Uvilno declares collections, typed fields, references and optional rules in data/schema.json. Generated interfaces call Uvilno.db for hosted CRUD, and the creator inspects rows through App Data. The schema is validated with the saved version; it is not permission to execute arbitrary SQL or server code.
45-word answer · Reviewed 2026-10-27Begin with field meanings and ownership, not merely table names. Mark required values, supported options and references to other declared collections. A schema change can affect existing records, so inspect compatibility instead of assuming a new preview automatically migrates every old value.
The hosted service validates operations independently of the generated interface. A disabled button or hidden section is not an access-control mechanism. Keep real orders, bookings and lead collections empty initially; only explicitly disclosed fictional demonstration records should be seeded.
What to verify.
| Area | Documented behavior | Your verification |
|---|---|---|
| Definition | data/schema.json declares supported typed collections. | Compare the declaration with App Data fields. |
| Access | Private rows follow real app visitor ownership. | Try retrieving a record with another identity. |
| Execution | The service validates bounded CRUD operations. | Submit a missing required value and inspect the error. |
Drag the slider, use the arrows, or scroll within the table.
Try the workflow yourself.
Use this checklist in your own disposable project. These marks record your review; they do not run tests or certify an application.
0 of 3 review steps marked by you.
Read the editable test brief
Plan a personal inventory application with private items and locations collections. Define required names, quantity as a number, supported status options and a valid location reference. Use actual hosted CRUD and a visual list/detail interface. Include field validation, revision conflict handling and an App Data verification checklist without arbitrary SQL or invented server functions.
Preparing a brief does not start generation. Review and send it explicitly; builds use the normal allowance, and source access requires entitlement.
Sources and scope.
Published by the Uvilno editorial team on . This is product documentation and editorial guidance, not an independent ranking or a promise that every application will pass. Vendor plans can change; official sources establish their own terms.
Does opening this test use my allowance?
Preparing the test brief does not invoke a model or create a billable build. Review the draft and explicitly send it to generate; normal usage and source entitlement rules apply.
Check the architecture. Compare the tradeoffs.
Follow the data model, account boundary and source handoff before choosing a builder.
Compare builders
Plan a full-stack app
Review the evidence
- Full-stack builder buyer’s guide
- Four full-stack workflows compared
- Plan data, sign-in and checkout
- Machine-readable evidence and methodology
- Remixable app blueprints
- Direct answers to builder questions
- Free planning and migration tools
- 108 full-stack engineering prompts
- Public SDK documentation
- Recorded checks and open evaluation protocol
- RSS updates for guides and comparisons