Build and host an application using the data you already have in Knowi. Create a sales review, a customer portal, or an app for tasks and approvals. Each App has its own pages, branding, and access settings.
You can build through an AI assistant, use the Builder in Knowi, or write the code yourself. Review a preview, then choose which version goes live.
| Guide | What you can do |
|---|---|
| Get Started with Apps | Build, preview, publish, and roll back an App. |
| Manage Apps | Set access, share an App, add images, configure actions, and review activity. |
| Copy and Move Apps | Make a development copy, copy between accounts, or move an App to another installation. |
| Develop Apps | Work in Git, build locally, use MCP, and connect App code to data and services. |
| Install and Administer Apps | Set up repositories, install Apps services, and configure a customer environment. |
Before you begin
Apps must be enabled for your account. If it is unavailable, select Request access on the Apps page or contact your Knowi account representative. Your administrator assigns permission to create and edit Apps; publishing requires a separate permission.
Knowi's Builder also needs AI access and a configured AI provider. You do not need Knowi AI access to write code locally, build existing source, or import and run a packaged App. An external assistant using MCP writes the code itself.
To create an editable App, you need a writable Git repository. Knowi can create one for you when Knowi-managed repositories are available. To install an App someone has already built, use Import package.
Check access before publishing. Choose Knowi sign-in required for an internal App. If App sign-in is not configured, the form selects Public, and anyone with the published URL can open the App. Ask your administrator to enable App sign-in before publishing private data. See Access and security.
Build through MCP (recommended)
MCP connects an AI assistant, such as Claude or Codex, to Knowi. You describe the App; the assistant uses the knowi_app tool to create it and submit code. You can open the same App in Knowi to review its versions and settings.
Connect and check setup
Follow the MCP Server connection guide for your client and Knowi installation. Sign in with your Knowi account. Connecting does not grant extra App or dataset permissions.
Start with:
Use Knowi's knowi_app tool to check whether I can create an app. Show any missing setup and whether Knowi sign-in is available.
The setup action lists available repositories and missing configuration. If Knowi-managed repository creation is available, the assistant can create one. Otherwise, ask your administrator for a writable repository.
Describe and generate
Find suitable data first:
Find datasets I can access for a sales review App. Check which fields contain order dates, regions, and revenue. Ask me to confirm the dataset before building.
Review the suggestion, then ask for the App. Adjust this example to your data:
Create a Knowi App named Sales Review with an available URL slug. Use the dataset and fields we agreed on. Create a Knowi-managed repository if available. Require Knowi sign-in and use no database. Show total revenue, revenue by region, and an orders table, with date-range and region filters. Make it work on desktop and mobile. Build it and give me a preview. Do not publish yet.
The assistant creates the App, reads its source, submits the files, and checks the build. When the version is Ready, it requests a preview and returns a short-lived link. Checking build status alone does not start a preview.
If the link expires, ask for a fresh preview of that version.
Refine and publish
After reviewing the preview, request a change:
In my Sales Review App, add a monthly revenue trend above the orders table. Keep the existing filters and dataset. Build the change and give me its preview.
When satisfied, name the version you reviewed and explicitly request publication:
Publish the Sales Review version I just reviewed. Confirm its version number and live URL.
Creating or changing an App does not publish it. If you edited the source directly in Git, ask the assistant to build the latest commit on the App's branch. See the MCP action reference for tool details.
Build in Knowi
Use the Builder to describe an App and review changes without leaving Knowi. If you already have code, use Create from repository instead.
Create your first App
- Open Apps from the left menu and select New app.
- Enter a name, such as Sales Review, and an available URL slug. The slug becomes part of the live address.
- Under Data, select a dataset you can access. For this example, use one with order dates, regions, and revenue.
-
Describe what you need:
Build a sales review app using my selected dataset. Show total revenue, revenue by region, and an orders table. Add date-range and region filters that update all three. Make it work on desktop and mobile.
-
Open Advanced settings > Repository. Choose an existing repository, or choose Knowi-managed, enter a repository name, and select Create repository. Knowi saves the code there. To give GitHub users access to a Knowi-managed repository, see Share App code.
- Under Access, confirm Knowi sign-in required. Leave Database as No database for this example; reading Knowi data does not require App storage.
- Select Build app.
Progress appears in the Builder. You can leave and return while it runs, or select Request cancellation. If a setting is missing, Knowi identifies it. A failed or cancelled generation keeps unused uploaded images available for retry; reopen its conversation to recover the request.
Review and refine
An editable App has these sections. On a small screen, use the App view selector.
| Section | Use it to |
|---|---|
| Builder | Request changes, follow builds, and manage data, write actions, and images in App resources. |
| App settings | Set access, repository, storage, embedding, secrets, and the App's address. |
| Preview | Run a selected Ready version and publish it when approved. |
| Commits | Review source changes. Select Versions to see builds and publication details. |
| App activity | Review recorded usage and sign-ins. |
Imported Apps show Data & actions and Versions instead of source editing tools. Update them by importing another package.
Each person has a private Builder conversation for the App. Commit summaries, build details, and assistant-provided notes are shared with other App editors; external assistant chats are not imported. Unsent text is not saved after you close the App.
App resources saves changes as you make them. Not built yet means an addition will be included in the next build. Removed means the latest build still uses the item until you rebuild; select Undo to restore it. Off marks a disabled write action. A new build uses the current resource list.
Select Preview on a Ready result or version. Opening the Builder or completing a build does not start a preview. Check totals against your data, try the filters, and review the layout at the screen sizes your viewers use.
To refine the App, enter a request in Ask for a change and select Build changes:
Add a monthly revenue trend above the orders table. Keep the existing filters and show the selected date range and region.
You can also use Build changes with no text to build pending resource changes. Each successful build creates a saved version. Changes start from the latest Ready version, even if you are previewing an earlier one.
Use Refresh to load versions created through MCP or Git. Search history searches the loaded records; load older records to search further back.
Preview versus live
Preview lets you review a version without replacing the live App. If a preview expires, select Retry preview or ask your assistant for a fresh link.
| Feature | Preview | Live App |
|---|---|---|
| Knowi data | A sign-in App uses the previewing editor's permissions. Public and App-managed Apps use their App-level data grant. | A sign-in App uses each viewer's permissions. Public and App-managed Apps use their App-level grant. |
| AI inside the App | Returns a dry-run result; does not call the provider. | Calls the configured provider when permitted. |
| Email and report schedules | Does not send mail or save schedules. | Sends or schedules reports when permitted. |
| Storage, secrets, and integrations | Does not use the live managed database or App secrets. State writes and HTTP calls return dry-run results. | Uses configured storage, secrets, and permitted integrations. |
| Write actions | Returns a dry-run result without changing the destination database. | Permitted signed-in users can run enabled actions. |
A successful preview does not prove a live integration is configured. Test live actions with controlled data after publishing, and use a development copy when you need to test changes separately.
Publish and share
Select the Ready version you reviewed, then Publish vN. Check the version in the confirmation. Publishing changes the version served at the live URL; it does not happen automatically after a build.
Open the live App and check its data and actions with the intended users' permissions. For a sign-in App, share the App with those users or groups and give them access to the underlying data. You can also add the App to the Knowi menu.
Update or roll back
Build and preview a change, then publish the new Ready version. To roll back, open Commits > Versions (or Versions on an imported App), preview an earlier Ready version, and publish it. The confirmation identifies the rollback.
Rollback restores code, not saved App data. A live App keeps running if its Git host is unavailable; generating or building another version needs the connection restored.
| State | Meaning |
|---|---|
| Queued or Building | The version is being prepared. |
| Ready | You can preview or publish it. It is not live yet. |
| Failed | The build or startup failed. Read its error; the live version is unchanged. |
| Live | This version serves the live URL. |
Troubleshooting
- Apps or New app is unavailable: ask your administrator to check Apps access and your create permission. An installation configured only to serve imported Apps does not offer source editing.
- Build app is unavailable: check the repository and, for the Knowi Builder, AI configuration. Code written locally or by an MCP assistant does not need Knowi's AI generator.
- A build fails: open its details in Versions and correct the reported source or configuration problem. See technical troubleshooting.
- The preview will not open: select Retry preview. If it still fails, check the version's error with your administrator.
- A viewer sees no data: check App sharing, dataset permissions, and row-level restrictions. Sharing the App does not grant dataset access.
- An import or copy fails: see copy and move troubleshooting.