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

[mdubakov]

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 for specific problems or use cases without any programming knowledge. You describe what you want to our AI agent, and it builds it. An App can be fully functional and you can see, add, update, and delete data there.

Because an App is just static client-side files, there are no servers to manage and nothing to deploy. It just works. Apps inherit Fibery permission model: create one at the top level in the sidebar and everyone sees it, or inside a Space and it’s limited to people with access to that Space, or in Private section and it will be visible to you only.

Here’s a calendar App we built internally that visualizes our vacations, sick days, and overtime in a way no standard view could.

Basic Apps are extremely easy to build, while more complex can take more time and iterations, but limits are not clear even for us so far. You can try to build custom forms, visualizations, interactive calendars and timelines, and even re-build existing tools UI inside Fibery. And yes, Dark theme is also supported.

Check Custom Apps user guide to learn more.

Apps is an experimental feature, enable it in Settings → Experimental Lab → Apps.

NOTE: If you created some custom Pages, you will have to re-create them with the new Apps manually. In this release we are disabling new Pages addition, but existing Pages will work till 1st Aug 2026. Please handle the migration before that date.

As most companies would say “we’re thrilled to watch what you will build with this technology”. In this specific case we are thrilled indeed .

Introducing AI credits

Historically, we’ve measured AI in the number of calls (aka answers). Well, it made sense in 2024 when 4o told us we were freaking geniuses to choose that metric but not in 2026. With advanced reasoning and the use of tools, AI calls have become widely diverse, both in utility and cost:

That’s why we are transitioning to AI credits, just like the rest of the industry.

Now complex queries like “figure out the product roadmap for Q4 based on all the customer feedback received in Q3” cost more, while simple ones like “does Fibery have an MCP server?” cost less.

All paid plans still include AI, just as credits instead of calls:

The simplest call takes about 5 credits, while a median one takes about 18 credits. Depending on your workspace size and the complexity of you queries, you might be better or worse off with the new limits. You’re welcome and we are sorry .

We are resetting AI monthly limit for all paid customers today, so you’ll have a week to experiment with AI credits before the first proper month of July. Go to the new Settings → Extra usage page (spoiler!) to see how many credits you’ve consumed.

If you’re suspicious or curious about the change, Anton, whose initials are literally A.I., wrote a blog post explaining the context behind it. There are also a couple of teasers for what’s coming next there.

If you have any questions, please shoot!

Extra usage

If you find yourself in the middle of a month no AI credits left, you can now enable extra usage.

The extra AI costs €15/$15 per 1000 credits. Set a monthly spending cap (e.g. €30 per month) and continue your normal operations:

Once a month is over, you’ll be charged only for the amount used (e.g., €20.48), not the entire cap. There will be an extra invoice in your billing settings.

By default, the extra usage is off (we fought off our greed!). Go to the new Settings → Extra usage page to enable it.

Coming next:

1. Extra usage for automations;
2. Extra usage for integrations;
3. Dashboard to help you decide whether you should optimize things or bump extra usage.

Check out our new blog post explaining why we decided to introduce extra usage (and AI credits) now.

Lists and Tables Views now handle large datasets far better (experimental)

Until now, opening a view with a deep hierarchy meant Fibery fetched everything up front. If you had hundreds of thousands of entities buried under a collapsed branch, you paid for all of them on load.

We’ve reworked how hierarchical data loads. Two changes do the heavy lifting:

• We only load what’s open. Collapsed branches aren’t fetched until you expand them.
• We load 100 children per parent at a time. Need to see more under a branch? A “Show more” button pulls the next batch.

The result: views with complex hierarchies open dramatically faster. In our testing, loads that took around 1.5 seconds now come back in roughly 0.1 seconds when things start collapsed.

The yellow “too many entities” banner is gone from Lists and Tables Views. A “Show more” button at the end of a branch replaces it.

This feature is experimental so far, please enable it in Settings → Experimental Lab → Hierarchies Lazy Loading.

Set static default values for basic fields

Now you can set default static values for checkbox, basic text fields, number fields and date fields. For example, you can set 19% default for VAT field or 0 for some number field, or 1 for Currency Rate field. You can find default value setting in Edit Field area.

Automations history

The history of changes for automation buttons or rules is available in Activity Log now. Use Automation Rule or Automation Button values for Schema Change filters to see them.

Deleted rules or buttons can be restored in Activity log or in Trash as well.

Fibery AI is now permissions-aware

Fibery AI now understands your permissions across the entire workspace, and is able to answer what spaces/databases/entities you have access to, and why you have access to these things (via access template, manual sharing or assignee-based sharing).

What’s not included yet:

• The Agent can’t set up permissions for you
• Admins can’t use it to check what access other users have

Any user can manipulate data in Fibery AI

Previously, non-Admins were limited to asking questions in Fibery AI, now any user can actually change things: manipulate data, views and schema, according to users permissions. Fibery AI knows your access level, and always respects it.

Improvements

• Rich text. Now you can move rows and columns in text Table via Move row up / down and Move column left / right actions in … menu.
• Embed View: Now you can insert Embed View to Dashboard, Document and Whiteboard. So users are able to embed things into embed view and embed this embed view into dashboard to open it full screen as other views .
• Merge entities. Current entity is hidden now from a list of entities available for merge
• Filters. Added a confirmation dialog before “Clear all” removes filters across databases, preventing accidental loss of filter setups.

Fixed Bugs

• Automations: Clicking Enter in Rule ‘Name’ field we submit entire rule
• Reports:
  • Outdated Fibery logo is used in Report setup screen
  • Warm theme is not applied to report sync loader, ‘Add field’ and “Swap axes” controls
• Home Page: View description gets erased after visiting Home page
• Form View:
  • Default value is not linked for hidden relation when Form is triggered from specific place
  • Locked Forms affects counter but not unavailable in Forms menu
  • If full layout is set to the default form, it does not apply to the in-line entity creation
  • Forms duplicating in the sidebar menu
• Access:
  • Empty source is shown in User access audit if access was granted via “Automatically share Database with People” toggle
  • ‘Import’ button should not be displayed for Users
  • Group Members can’t see newly added members if auto-access to Users is enabled
• Gantt View: UI issue with dependency arrows on Gantt view
• Fields: Ugly error on changing relation cardinality if one of the ends has ‘required’ flag
• Fibery AI Agent:
  • Agent should include files of entity selected in context
  • Validate images’ sizes to be less than 2,000 pixels
  • Fibery AI does not see contents of PDF files somehow

P.S. Your feedback is welcome, as always.

[timothy]

A wonderful & value-packed release! So looking forward to custom apps. Been playing more with pages – this is great.
AI credits makes sense – and we much prefer you keeping a competitive seat cost and allowing us to fluctuate our AI usage!
Really happy about the loading improvements.
The AI improvements with permission awareness and user manipulation is great.
The automations history -AND- the confirmation before clearing filters is VERY MUCH appreciated.

[Tommy_Hedley]

Another huge release! Thank for all of this and for managing to fix an outage on the same day as a release . I’m really excited about Custom Apps, I think this might eliminate another separate app or two from the stack. I noticed a few things reading the Custom apps user guide:

1. No way to edit the code other than AI - is there any plan to change this at some point? As much as I enjoy and use AI, it is sometimes nice to build something exactly how you want it, rather than prompting in circles.
2. It would be cool to be able to share Custom Apps. I think it would be really cool to see what people come up with in the Fibery Showcase and share with the community, which is already an awesome reason to use Fibery. I’m assuming you guys probably have plans for this, but if we could edit, we could share apps in the meantime.

Awesome work, thank you Fibery team!

[Sergey_Truhtanov]

Both are exactly next things we will be working on.

Sharing is easy to add.

Editing may take some time to implement properly. We plan to add some version control to Apps as well, to enable undo. Maybe those features will come together.

[Jonathan1]

@mdubakov

3. Dashboard to help you decide whether you should optimize things or bump extra usage.

Does it mean you are going to add a widget for dashboards in order to see the stats of the workspace ? Or is it a separate dashboard ?

Would be interesting to have a widget for that.

@mdubakov

• A “Show more” button pulls the next batch.

Will it be possible to add an “auto Show more” using the scroll function ?

@mdubakov

Set static default values for basic fields

Excellent !

@mdubakov

Automations history

That’s also great. I hope activity can also be tracked on Views at some point. I already had some surprises while moving Task on Gantt view. I needed to re-work the dates of my tasks because most (all ?) of them moved in a manner I was not expecting and it was not possible to undo the action.

@mdubakov

Introducing AI credits

@mdubakov

Any user can manipulate data in Fibery AI

Should be great to be able to limit who can use AI.

@mdubakov

• Rich text. Now you can move rows and columns in text Table via Move row up / down and Move column left / right actions in … menu.

Cool ! I often had to cut and paste to move a line .

Great update overall, thanks !

[Tommy_Hedley]

Amazing, I should have guessed

[mdubakov]

@Jonathan1

Or is it a separate dashboard ?

Separate dashboard in Settings

@Jonathan1

Will it be possible to add an “auto Show more” using the scroll function ?

Unlikely, but I suggest to try it and see how it works now

@Jonathan1

That’s also great. I hope activity can also be tracked on Views at some point.

Yes, we are going to add history to all the things.

[bear]

Amazing @Sergey_Truhtanov - I really look forward to seeing Custom apps develop over time and all of these features you mention coming out!!!

[helloitse]

@mdubakov

• Rich text. Now you can move rows and columns in text Table via Move row up / down and Move column left / right actions in … menu.

Small line. Huge win!

[Tommy_Hedley]

Ok, I was cautiously optimistic about the Custom Apps and figured there might be some big limitations. There still might be, but this is crazy . I did a single, crappy, two sentence prompt to see if I could get it to pull up a camera feed for scanning QR codes. 60s later, I get this:

I gave it a QR code from an entity id in a specific, prompted DB and it pulled it up instantly.

A bit more tweaking and you could (and I will) build an insane inventory management tool that could easily replace some very expensive software. My mind is completely blown! Fibery team, you guys f*cking rock!

Also, could we get QR support on the mobile apps for this purpose? I had to do the scanning on my computer.

[RonMakesSystems]

What a fantastic release. Looking forward to playing around with all of this.

@mdubakov

A “Show more” button at the end of a branch replaces it.

I’m a little worried about this one, considering the complaints here: Embedded List View "Show all" is very hard to notice and it causes confusion

Personally never had an issue with a bit of longer loading times in tables with more data, but this probably came from complaints from others…

@mdubakov

Set static default values for basic fields

Wondering if this can also be shown as default in the UI when creating? Technically possible when creating a form to make it default, maybe just setting it automatically on new form creation? Not sure how this should be handled, as the default value is then being controlled in two different ways. (the fact you mentioned static default values means dynamic default values down the line? )

[alex]

@Tommy_Hedley

Also, could we get QR support on the mobile apps for this purpose?

Will check what we can do here

[misha]

I’m a little worried about this one, considering the complaints here: Embedded List View "Show all" is very hard to notice and it causes confusion

I’d say this is a bit different problem. The “show all” on relation views is sort of detached from the data so it’s hard to even notice this button.
With the lazy-loading implementation, “show more” buttons are inserted right next to your entities on the same level. So hopefully there will be less ambiguity

Also please note, that previous limit was flat, 3k for the database until yellow banner with “show all” appears. This equals to just 30 entities with 100 children and there were no hints if other entities have any children.
After the improvement the limit is per parent so it can easily be 100 entities with 100 children and you always know which one have children and where there are more

[Eva_Folch]

@mdubakov

Set static default values for basic fields

THIS!!! is fantastic! It’s going to save me plenty of clicks! Thank you!

Looking forward to trying the custom apps as well