April 23, 2026 / Experimental UI pages creation via AI, Sort improvement

[mdubakov]

Pages were transformed to Fibery Apps in new release. Check them out.

June 25, 2026 / Custom Apps, AI credits & extra usage, Better performance for large tables, Set static default values for basic fields, Automations history

Yesterday we had a very long degraded performance incident for integrations, reports and automations. We still didn’t identify the root cause (and even AI feels helpless here). The incident has nothing to do with today’s release, but if things will go south again, blame the heatwave and Amazon DocumentDB. Custom Apps (experimental) Fibery now lets you build your own Apps — custom, client-side UI that runs on top of your workspace data. Now any user can build custom solutions tailored…

[mdubakov]

@rabrunos

Version history would also be very important. Since the AI can change a lot of code at once, being able to restore a previous version would make experimentation much safer.

Versions added to Apps

August 6, 2026 / Custom Apps improvements, Convert Select field to Database, Update small part of rich text and add comments via MCP

Custom Apps improvements (still in experimental mode) There is a very good chance that Custom Apps will be publicly released next week, we are nailing the last problems and overall the experience is very stable already. Today we’ve released several improvements that will make architects life a bit easier. Visual edit: click element, describe changes Now you can select apps elements and ask AI to update these specific parts. It speeds up iterations and make Apps creation process less painful. Us…

[mdubakov]

@rabrunos

It would be very useful to have the option to edit HTML, CSS, and JavaScript separately, in their own tabs or sections, while still keeping the option to write everything in a single file for those who prefer that. This would make larger pages more organized without limiting different workflows.

Now you can do it August 27, 2026 / Usage dashboard, manually edit custom apps

[kathrin_Infanta]

It’s interesting, I try this…

[rabrunos]

I’m speechless, everything changed the day I could edit manually! You guys are the best, Fibery is now my religion.

[bear]

Haha prepare to get quoted in Fibery ads!

[AdVhPkgKad]

False.

Religion is for Sunday. Fibery is forever.

[bear]

Well actually he is pretty spot-on:

1. religio (Latin) is the source of English “religion.”
2. One ancient explanation, associated especially with Lactantius and later influential writers, derives it from re-ligare:
   • re- = again
   • ligare = to bind, tie
   • → “to bind again” / “to reconnect”

Fibery is all about connecting ideas, data, people, workflows. You can one hub for your company for all your company processes, instead of having a bunch of disconnected tools and data.

Most software creates silos. Fibery reconnects them. In that sense, Fibery is religion: it binds together what has been separated.

Edit: BTW I see a cake next to my name - apparently it’s my cake day, I signed up for these forums 6 years ago! Thank you, it’s been a lovely time!

[mdubakov]

@drew

public portals and reasonably/attractively price licensing for external users, this could soon be the unicorn I’ve been treasure-hunting for years… Let’s ride!!

We’ve started to collect requirements for this use case. How would you use Apps if it would be possible to share them?

[christamae]

I currently have a third-party front end built in Zite that uses magic link authentication and allows our customers to log in and upload CSV files with their order details (sometimes a single record, sometimes hundreds). The app parses the CSV and sends each record to Fibery as an individual Client Request entity for processing.

The UI also lets customers view requests in that database that belong only to their company, based on the logged-in user. This allows them to know what’s been ordered by others on their team and monitor progress.

I’d love to reduce the number of tools in my stack, so I’d definitely be interested if Fibery supported external-facing use cases like this natively.

The key consideration for me would be pricing. Zite doesn’t charge per external user, only per builder & for AI build credits, so Fibery’s pricing model for external users would need to be reasonable enough that consolidating actually makes sense.

[mdubakov]

@christamae

Zite doesn’t charge per external user

This is what we will do for sure.

@christamae

The app parses the CSV and sends each record to Fibery as an individual Client Request entity for processing.

Aha, so you also need some AI Agent that does the parsing and adding entity?

[christamae]

My understanding is that the Zite AI App builder wrote code into my app that does the parsing & dispatching to Fibery, rather than making that process agent-based. I am not consuming AI credits whenever customers submit new orders.

[timothy]

However, we do have use cases for agentic AI in a workflow that we are incorporating through N8N and other platforms — if there was a world where this made sense in Fibery, it would be great.