🐌 Fibery Product Report: May 2026

[mdubakov]

May 2026 was one of the least productive months in terms of new releases. Four (4) developers enjoyed vacations, but even with this taken into consideration the progress was not stark.

• Granular Access. Good progress..
• Fibery Apps. Some progress, but only a single person worked here.
• Make AI Agents happy. Average progress.
• Growth. Not much planned, not much done.
• Other.

Granular Access

Access to Users

The major release happened in May as planned, plus we shipped a couple of smaller complimentary pieces:

• Configure who can see Users
• Extend access to Users via access templates
• Automatically provide User Group members access to each other

We will fix the remaining non-critical Bugs, and continue with the remaining smaller Features:

• Allow users with the same email domain to see each other (with Dima in core!)
• Configure who can manage Users

Unless something goes awry, we are looking to finish with access to Users in June.

Adoption

• Share with users with a particular email domain have been used to share mainly Spaces and Databases across 37 workspaces
• Configure access to Users has been already used across 3% of all collaborative workspaces within 10 days of the release:

• We expect the number to plateau around 10%, similar to Guests: not every customer needs either, but those that do need it badly.
• Most paid customers that opt for custom visibility, choose Everyone with a trusted domain, so it looks like it wasn’t a stupid idea to introduce such a concept.
• Introduce custom access templates for Databases access has expectedly proved to be a niche Feature. On the bright side, the decision to allow to re-use a custom DB access template across multiple DBs was the right one, since almost all of them are re-used.

Deprecations

Last autumn, we sunset two pieces of legacy access controls:

• Sharing entities to web that depended on who shared the entity → access templates.
• Contributor Space access → Database access + automatic sharing via People Fields.

In May, as previously announced, we fully discontinued both.

Next

No changes from Product: April 2026

The next big thing is to rethink what everyone in the workspace can see in the age of AI: Do not allow Users to see IDs of entities they don’t have access to. This might also bring a significant performance boost.

In parallel, we’ll start Allow to hide Space data (entities) from Admins with Dima as the primary developer .

Custom Apps

We’re working on Experiment: Custom Apps and with some polishing will release it as quite ready solution in June (main thing to finalize is App UI styles).

We will introduce new View type called App, and it will work similar to other views (belong to space or top level, can be created in left sidebar, etc). Architect will be able to create custom UI App right there via vibe-coding (or real coding in the future). Maybe also in the future we will allow more control about who can see Apps and how they are presented to users outside Fibery, but not now.

We will also introduce a new Credits system for tokens, so users will be able to purchase credits and use them to create custom Apps or interact with Fibery AI: Make AI pricing sustainable.

Make AI Agents happy

Quite slow progress here, we improved MCP Server stability and added Send web request action into automations, that is it.

As a side quest, we’re researching how to re-write Fibery AI based on Anthropic agents. Max implemented a prototype of our Fibery AI based on Managed Agents. It allows Fibery AI to work as MCP client and gives us other benefits, like memory, chat compaction, etc, but results are inconclusive so far, since it is quite slow for chat use case. Most likely we will not go for it in June.

We’ve also decided to Sunset Video/Audio transcription feature, since the usage is extremely low (fewer than 5 workspaces use it).

Done

• MCP Server reliability improved
• MCP and AI agent tool: Add comment
• Send web request (post to webhook) action in automations.

Next

Rich text should be ready for agents. First two things we will focus on are when Konstantinas is back from vacations:

• Suggestion mode for documents
• Update small part of rich text via MCP tools or API

MCP Server improvements and other things

• AI Agent should access Files content (+ attach file into chat)
• Open Agent: Build for Architects (not only admins) + make agent permissions-aware
• Create & Update Whiteboard View with AI
• Automations history

In parallel, we are thinking about AI in automations and external AI agents, but no concrete solutions here yet.

Growth

Themes

Reports now adapt to the chosen theme:

• Adjust reports (vizydrop) palettes based on theme
• Apply custom theme in vizydrop reports (& import from CSV)

We might do a few minor tweaks here and there, but overall the themes functionality is considered finished. The only thing left is to promote the warm theme among existing users who haven’t tried it yet.

New AI pricing

We finally started working on Make AI pricing sustainable that includes these three major pieces:

1. Use credits instead of calls in AI limits
2. Allow workspaces to go beyond plan limits
3. Add usage dashboard for metered services

This is timely, given the upcoming release of Experiment: Custom Apps. Even Experimental: Create UI pages via chat produced a noticeable bump in AI costs.

Other

Search improvements →

While we wanted to stop this theme, we decided to add a few filters, including filter by People and Modification Date Search results: Filter by People fields (Created By, Assigned To, etc.). This should be released in June.

Rich Text improvements →

Bullet and checklist improvements were the last thing we did here. We’ve fixed many problems with bullet lists and checklists in this release, including tabs behavior, list items deletion, etc.

No other improvements are planned so far.

Whiteboard

We’ve added more icons and are now working on Whiteboard: Templates.

Other done features

• Fibery steps in Slack Workflow Builder
• Redesign Database: Data header
• Optional deep copy on Entity Duplication

Some in progress and near future features

• Handle Large Datasets in Tables
• Customize load limit (aka page size) for embedded View (Table, List)
• Have own columns for nested items and do not merge columns to include more fields without changing width
• Allow user to override default sorting in Views

[Lee_Denny]

@mdubakov

Sunset Video/Audio transcription feature

Wil you be providing a proper transcription option on file attachments instead? There have been lots of requests for this. I think the reason the usage is low is the way it is implemented, not that people dont need and want transcription.

[ccollins]

@mdubakov

We’ve added more icons and are now working on Whiteboard: Templates.

Super excited for this! Really hoping that we can create custom templates

[myg_ge]

@mdubakov

We’ve also decided to Sunset Video/Audio transcription feature, since the usage is extremely low (fewer than 5 workspaces use it).

This one would be a disaster for me - I use this feature a lot and it was one of the main reasons I went for Fibery - killed 2 other apps doing this and saved nearly $30-40 of extra monthly costs by replacing them with Fibery. Please-please-please keep this feature!!! It’s a winner one for my biz dev and even business analysis activities! I’d only ask to add Claude to AI models.

@mdubakov

We’ve added more icons and are now working on Whiteboard: Templates.

@mdubakov

• Fibery steps in Slack Workflow Builder

@mdubakov

• Handle Large Datasets in Tables

@mdubakov

• Customize load limit (aka page size) for embedded View (Table, List)

These ones are awesome to me!

[Bronn]

@mdubakov

Sunset Video/Audio transcription feature

I’m surprised only 5 workspaces use it. I’ve used it quite a bit in the past and I found it very useful. I still use it occasionally on the new business account and, once we’re setup fully, we might end up using it much more again. I’d be very sad to see it go.

@mdubakov

We will also introduce a new Credits system for tokens

Understandable decision, though it might mean it’s hard for some to get the green-light to use AI. Will there be any credits included in the subscriptions, or will they be completely separate?

[antoniokov]

@Bronn

Will there be any credits included in the subscriptions, or will they be completely separate?

Sure, the credits will be included in the plans in the same way calls currently are.

If you have a workspace with 25+ paid seats, the amount of AI included will actually be roughly the same as it is today, i.e.

[number of calls you currently have] × [median call complexity in credits] ~ [credits included]

For smaller workspaces the number would be less, though, since we’ll scale the number of credits included with the number of paid seats.

Most likely, I’ll write a more detailed blog post on the AI pricing change. Please let me know if there are some questions you’d like to see answered.

[Ryan_Dejaegher]

Not sure how much Fibery is willing to share but I would love if Fibery could share their thoughts on AI pricing models (subscriptions/credits) etc.

Separate from Fibery I’ve been trying to pullback my usage of AI tools/features because I’m worried about the cost and becoming dependent on a tool where the cost is unpredictable.

[Renato_Carvalho]

@mdubakov

We’ve also decided to Sunset Video/Audio transcription feature, since the usage is extremely low (fewer than 5 workspaces use it).

Oh, I use this all the time and it’s going to be missed a lot.

[Renato_Carvalho]

@mdubakov

We’ve also decided to Sunset Video/Audio transcription feature, since the usage is extremely low (fewer than 5 workspaces use it).

It looks like 4 of the 5 workspaces using this feature already commented here

[Renato_Carvalho]

@myg_ge

This one would be a disaster for me - I use this feature a lot and it was one of the main reasons I went for Fibery - killed 2 other apps doing this and saved nearly $30-40 of extra monthly costs by replacing them with Fibery. Please-please-please keep this feature!!! It’s a winner one for my biz dev and even business analysis activities! I’d only ask to add Claude to AI models.

Same here!

[mdubakov]

@myg_ge

This one would be a disaster for me

OK, we will keep it so far and see what we can do to make it better and improve usage

[webinit]

I didn’t even know that feature existed.

[timothy]

As far as improving usage, if we could have it run on a file field instead of having to manually upload into a rich document, that would be helpful. We could then use automations and/or n8n to link the recording, transcribe, and then maybe even delete the original file. It would be helpful for some of our phone recordings where it doesn’t auto-transcribe. It could be a credit-based usage so that it doesn’t get slammed by someone doing a ton of transcription? Just throwing ideas out there.

[bear]

Thanks for the update! Excited about Whiteboard templates. And the Custom apps. Very promising.

AI pricing is good, of course I can pay for that and especially if that means that I can pay my way beyond any limits so I do not worry about such limits!

@mdubakov

We’ve also decided to Sunset Video/Audio transcription feature, since the usage is extremely low (fewer than 5 workspaces use it).

This is unfortunate, I can use this now that I am doing lots of interviews, makes the workflow nice and smooth to be able to do this within Fibery. So I would become the 5th or 6th workspace to use it then, but that’s percentage wise a big difference! But seriously, I am surprised that it’s not used more as it (I assume) it must be useful for way more people.

[myg_ge]

Thank you so much Michael! Great news!