For teams managing customers, orders and daily operations: describe work in natural language, let a server-side Agent shape a controlled draft, collaborate on records, then run authorized background jobs.
Open source and self-hostable. AI requires a configured model service; permissions and confirmation gates control publishing and writes.
These interfaces are static product prototypes. All records, counts and statuses are illustrative.
01 · Describe
Tell the assistant who will use the app, which fields matter and how statuses should change. Attach files or answer follow-up questions. Start with a concrete workflow such as customer follow-up or order handling.
Current boundary: requests need clarification; a conversation cannot bypass approval and become a published app.
02 · Shape
A server-side Agent generates data structures and an interface draft. Review allowed fields, business actions, state transitions and member access, then preview and confirm publication.
Current boundary: controlled schemas and UI components; previews do not implicitly write production records or execute arbitrary user source code.
03 · Use
Teams search and edit records, complete forms and move work through statuses in published apps. Inspect underlying data through tables, record details and authorized exports.
Current boundary: colleagues must sign in and have access; knowing a link grants no record or attachment permissions.
04 · Operate
Configure scheduled or event-triggered background jobs, declarative collection and notifications. Inspect run receipts and failure reasons. Public read-only pages expose only explicitly authorized record fields and images.
Current boundary: collection reads credential-free HTTP(S) sources only; jobs cannot expand authorization. Self-hosters manage model configuration, backups and operations.
miao.my