Guide
Check Custom Apps guide.
Building apps
Who can build a Custom App?
Any user can build Apps in the Private Space, and any Architect can build an App inside a Space. Admins can create Apps in the main area outside Spaces.
Can I edit code manually?
You can open any custom App's code and edit it directly.
Open an App in Edit mode, go to Code tab, make your changes, press Save. Give it a few seconds while the App rebuilds. You can edit existing files, but adding and deleting files isn't supported yet.
Why does building take so long?
Building runs a full AI agent, so a single iteration can take several minutes. That's normal. Sonnet is faster and cheaper than Opus for most changes, so use it unless you really need Opus.
Can a Custom App reuse Fibery's native features so they work exactly the same as they do natively?
No, not currently. Every Custom App is built from scratch - there's no library of ready-made native components that you can drop into an app. You can use UI JavaScript libraries to build your own version of a feature, but you won't get its native behavior for free - you'd have to build that yourself.
What happens to an App when the underlying schema changes — field renamed, database deleted?
The App will break and you will have to fix it manually. We are working on better survivability of apps for databases and fields renames now.
I have an error when creating an App, what to do?
Just copy the error and paste to AI panel, it should fix the problem.
Can I simplify Fibery UI somehow via many Apps?
Yes, you can build yet another App that will just provide navigation to several Apps. Copy links for every App and create a prompt like this for a new App:
Create a very simple UI that work as a portal to the following Apps
New Product Area https://[yourworkspace].fibery.io/apps/new-app/
Requests Inbox https://[yourworkspace].fibery.io/apps/new-app-20/
Vacations Charts https://[yourworkspace].fibery.io/apps/new-app-16/
I should be able to quickly open any app from another app, so keep navigation somehow
And as a result, you will have an App with UI like this that you can send to users
How to update Custom App's platform?
Fibery can ship new versions of Custom Apps platform. In some cases these versions are not backward compatible, so when working with some old app you can update the platform and the app will be re-build on the new platform version.
Notes:
This operation consumes tokens
🐝 If you create apps via MCP and want to use new apps platform version to some older app, you still have to update platform from Fibery UI
All new apps will use new platform
How does the URL work?
Custom app screens have their own URLs. If your app has several screens, reloading the page, pressing Back/Forward, or sharing a link opens the exact screen instead of the app’s start screen. This works in views, side panels, standalone apps, and public links.
Versioning and undo
Can I create a stable version of an App so I don't break it with experiments?
Fibery creates a version of the app on every build, so no need to do it manually.
Can I undo a change or roll back to a previous version?
Yes, you can revert to any version.
Sharing and permissions
Can I share an App outside Fibery?
It is not possible to Share or Publish an App so far. However, if you Publish Space to Web, the App will be visible to everyone, so you can use this.
Security
Can an app show someone data they shouldn't see?
Not directly. An app runs with the viewer’s permissions, so it only shows that person what they could already see in Fibery. But because it acts as the viewer, an app could be written to copy data the viewer has access to somewhere others can see it, or send it outside Fibery.
What can an app do, then?
Anything the person who opened it can do. An app is code running on your behalf: it can read every database you have access to, create, update and delete entities, and, if it's written that way, send data to services outside Fibery. A shared app is only as trustworthy as its code - including the open-source libraries it uses, which can be compromised even if the person who built it is trustworthy.
Does an app run with the builder's permissions or mine?
Yours. This is the one thing to keep in mind: when an Admin opens an app, its code acts with Admin rights, even if the Architect who built it only has access to one Space. That's why the Architect role should go only to people you trust, the same way you'd think about automation scripts.
Who can put an app in front of other people?
Only Architects of a Space (and Admins, outside Spaces). Any user can build apps in their Private Space, but nobody else sees those. So the people who can share apps with your team are the same people who already see all the Space's data, edit its structure and write its automations.
Does Fibery review the code the AI writes, or the libraries it uses?
Not currently. App code is generated by AI (or written by you via MCP) and may pull in open-source npm libraries. Fibery doesn't review that code or scan those libraries before building. What you can do: open the Code tab and read the code before you share an app (or ask the AI in the panel to explain what the code does and which libraries it uses), and compare versions to see what changed between builds.
Everything Fibery AI generates, including the code of your Custom Apps, is an AI Output under our AI Additional Terms. You’re responsible for reviewing it before you rely on it, share it or use it. If you’re not building with Fibery AI (for example, via MCP with your own AI tool), the code is entirely yours, and your AI provider’s terms apply.
Can an app send data outside Fibery?
Yes, if its code does, and Fibery doesn't currently monitor or block outbound requests from apps. If this matters for your workspace, review the code before sharing and keep the Architect role tight.
Who sees my data when I build an app?
Your app's source code is compiled on Vercel (listed in our sub-processors). Vercel receives the source code, not your workspace data, unless data is written into the code itself. The built app runs in your browser and reads data directly from Fibery.
Is there a record of who built or changed an app?
Yes. Each app has an owner, every build is saved as a version you can inspect and roll back to, and every AI conversation used to build it is stored with its author. There's no page listing all apps in a workspace yet; if you need one, contact support@fibery.io.
Note that changes an app makes to your data are recorded as changes by the person who had the app open, not by the app. AI conversation history is only stored for apps built in Fibery, not via MCP.
Can an Admin turn Custom Apps off?
Not from the UI yet. If your policy requires it, contact support@fibery.io and we'll disable Custom Apps for your workspace. We're also considering an "Allow Architects to create Apps" setting that limits app creation to Admins; tell us if you'd use it.
How do we use apps safely?
Give the Architect role only to people you trust. Review an app's code before sharing it widely. Treat a link to an app the way you'd treat a script someone asks you to run. And if your security policy doesn't allow user-built code at all, ask support@fibery.io to turn apps off.
Credits
I ran out of Credits and I'm not an Admin — what should I do?
Ask your workspace Admin to purchase more credits or use Fibery MCP Server to create Apps, it can do it!
Does using an app cost credits, or only building it?
App usage is free, so you spend credits only on building the App.
Can I build apps in my favorite coding tool?
Yes, you can Build Apps via MCP and it will not cost you any Fibery Credits, so it is a way to go for most cases!
Appearance and mobile
Can I use my custom styles with Apps?
No, you can't use your own styles — Apps match Fibery's UI as closely as possible, including Dark Theme support 🌚.
Do Apps work on mobile?
Yes, but you have to build them to be mobile-friendly.
Data storage and automation
Can I use the data a Custom App returns in automations, or show it as a field on entities?
Not automatically. A Custom app recalculates its data every time someone opens it - nothing gets written down on its own. To use that data elsewhere, you (or whoever builds the app) need to model a database that stores the app's output, then have the app write to it. Once the data lives in a Fibery database, you can use it in automations, formulas, or as a field like any other data.
Can one Custom App pass its results to another app?
No. Apps can't talk to each other directly. The only way to move data between them is through Fibery databases: write the data out from one app, then read it from the other.