Studio: build and change apps by chatting

The Studio is where apps are created and evolved. You describe; Nibor designs the data model, security, pages and logic, and shows a live preview as it works.

Creating an app

Press + New and either pick a template (CRM, Project Manager, HR, E-commerce, Accounting, Marketing, CMS, Healthcare, ERP, Feedback Tool, API Key Manager, SaaS Manager, Asset Library, Team Hub; the full list is at nibor.io/templates) or describe your own idea. Nibor answers with a plan card: the modules it intends to build and a few concrete choices for you (for example how alerts should be delivered). Adjust, then press Build this app. Generation runs seven steps — design, database, sample data, server-logic compilation, tests, self-healing and a security check — so the backend works the moment the app opens. It takes a few minutes; apps with many server functions take longer. If a build fails, the chat offers Fixa med AI: one press sends the failure back to the agent, which repairs the spec and rebuilds; the failed draft is kept so nothing is lost.

Build mode and Plan mode

The chat has two modes, switched with the toggle above the input:

• 🔨 Build changes the app. The agent inspects your app, picks the right tool for the request (edit a page section, change a model, seed data, manage users, publish) and reports exactly what it did.
• 🧭 Plan never changes anything. It thinks the request through with you and produces a plan you can send in Build mode when you are ready.

Speak naturally, in any language. "Create an admin user" creates an account; "make the dashboard heading bigger" edits just that heading. If a request is ambiguous the agent asks before acting.

The workbench

• Views: every page of your app; open one to preview or select an element for a scoped edit.
• Data: your models and rows; edit records directly.
• Theme: colors, fonts and branding for this app.
• NAS Editor / Code View: the app's underlying spec and compiled output, for when you want to see exactly what exists.
• Operate: your data at a glance — model row counts and analytics. Server functions, scheduled jobs and webhooks are managed in chat and monitored in the App Hub.

Publishing and versions

Use Deploy to publish: your app goes live at yourapp.nibor.io with TLS included. Custom domains are added under Portal → Domains (verify a TXT record, point an A record, the certificate is issued on first visit; the number of domains depends on your plan). Every generation and edit is versioned; ask the chat to restore a previous version at any time. You can also download the whole stack, see App Hub & export.

Templates you own: clone and update

Any app can serve as a template. Clone makes an independent copy (data model, pages, server functions, no data) that remembers where it came from. When the source app changes, the copy's Workspace tile shows From <source> with an Update from template button for organisation admins: a dry run first lists what would change (documents, functions, columns to add), then you apply. Functions you edited in the copy are left alone unless you choose force. Columns are only ever added, never dropped.