🍒 Fibery Product Report: August 2025

In August we did 4 releases with total 280 points (625 → 470 → 280 last 3 months). Our QA engineers and several developers went on vacation for 2 weeks and it affected releases, but we still did a pretty good job in August.

Main product areas and how they will change with time in near future.

We’ve got a new quite large enterprise customer and it affected priorities of quite many features in our backlog. So in the next 2 months significant part of Fibery team will work on these features. Note that all of them are requested by other customers as well and they benefit to the product as a whole. To give you perception of some features we will work on here:

  • Access previous values in Automation Rules
  • Duplication automation rule to another database
  • Disable sharing for the whole workspace
  • Batch drag and drop cards on Timeline and Gantt views
  • Some security features (session duration, service accounts for API)
  • likely some filters improvements
  • …

Permissions

Live

Track access changes (aka permissions) in history on all kind of levels is on production:

This should bring peace of mind to our architects and eliminate distractions for our dev team.

Introduce access audit for Users and User Groups is live for Spaces and Databases:

Add Entity access audit for Users and Groups has proved much more challenging due to the sheer volume of data coming from numerous sources. We haven’t found a feasible solution so decided to postpone and collect feedback.

We also implemented Add automation action to revoke access via Created By and immediately received dopamine from one large customer:

L: We’ve tested it - we’re delighted:) It works fast, no downsides found)

O: THANK YOU SO MUCH!!!

Next

While Deleting v1 permissions model is happening under the hood, we’ll finally start the long-awaited user-facing Features:

  • Consolidate default access template names across Space, Database, and Entity levels
  • Deprecate old Contributor Space access
  • Enable automatic Editor access via Created By by default for new Databases
  • Allow not to extend access from Space to its Entities
  • Allow to have Databases outside Spaces (in Default Space)

We are also likely to Introduce custom access templates for Databases access as a part of paid custom development for new enterprise customer — waiting for their official request.

Import

Live

We released a highly requested Feature: Update existing entities or skip duplicates via CSV import:

How popular is it? Stay tuned for the next monthly report :upside_down_face:.

We implemented it “the right way” and now have Fibery API: create-or-update (upsert) entity command.

Other smaller things included:

  • Import and sync data via AI smart agent
  • Add JQL Filter to Jira Sync
  • Add date of account creation for integrations accounts page
  • ​Webhook retry improvements and notifications about failures

Some customer dopamine:

I did a migration from notion to fibery for a client this weekend, and i build the full field mapping, and process changes in fibery using the notion integration and button automations. syncs up to the right stage, checks the old tasks, everything. And not just a simple import, we changed to much more complex processes. Goes to show how powerful this really is :exploding_head: really crazy.

Next

We are looking to Streamline how Users are imported and synced in integrations:

It’s in our best interest that people can easily migrate users from their current tool (ideally, with all the assignments preserved), since collaboration is key to adoption and since we charge per seat.

We’ll both unlock the existing functionality with a more approachable UX and add the missing bits.

Views & UI polishing

In August we decided to apply some effort on UI improvements and 3 people had been working on that. We’ve improved many areas visually, including Board View. We delivered many many small improvements here and there.

We will work on better Board View in September and then switch to List View and Calendar View improvements.

AI

In AI we were mostly focused on AI Agent Build mode. What was done:

  • We’ve added a possibility to create automations rules
  • [ai-agent] tag was added to rich text fields automations
  • UI was improved to include links to created views, databases, fields, etc.

We’ve also released Fibery Remote MCP Server, but we did not receive any significant feedback here so far.

AI Agent usage is growing, with 6500 calls in August.

Getting Started flow was not released still, but we will do it in September.

One of the problem is performance, AI Agent is relatively slow, so we will also dig into possible solutions and re-think its architecture.

Next things to do are

  • Create Whiteboards via AI Agent (works in beta, should be improved and fully released soon)
  • Make it possible to update Automations Rules and make them better
  • Improve UX
  • Then we will focus on better context management, so it will be possible to mention specific Fibery objects and change them

Whiteboard

In August, the Whiteboard activity feature was developed, it’s now in the testing phase and will soon be ready for release.

We updated the behavior of sections and improved support for color themes Update color palettes for elements for both themes. The behavior of bent lines was redesigned for better performance with diagrams Whiteboard: Bent connectors improvements

Next things:

  • Embed views on Whiteboard Embed views into the whiteboard (reports, tables, etc)
  • Relations support updates Whiteboard: Support all relations

Mobile

Good progress on the mobile app in August. We reworked the overall navigation, updated some common UI components (not all) for mobile behavior, the editing toolbar in the rich field, settings pages, mobile notifications, and quick actions. This month we’re moving toward the beta release.

Next things:

  • Finish the rich field editor on mobile device
  • Update all core UI elements (buttons, actions menu, calendar and icons pickers, lists etc.)
  • Update views and entity toolbar
  • Update views (Board, Table etc.)
  • Visual polishing
  • Internal testing
  • TestFlight/Google console release for beta testers

P.S. Your ideas, questions and reactions are welcome :cherries:

11 Likes

Always a joy to read these! Thanks for sharing them publicly.

This would be huge! Especially if in included extended access like access templates.

I really think Space Access control should just be separated into Data Access, View Access, and Space Config Access. With the ability to grant access templates for the space to users and groups.

I love how its not some dumbed down version of fibery, but the full fibery expeirence for mobile. You could technically build your full workspace, fix bugs, etc in mobile. Amazing! That said, I think it also calls for the non-admin / non-creator mode ("Non-admin" mode for admin :0)). Because of the lack of hover ability in mobile, seeing all the “…” buttons everywhere (for creators and admin) makes for a more cluttered ui.

Looking forward to all that’s to come!!

3 Likes

When will files actually be improved? They keep getting pushed back and now have a question mark on them. Do we have to wait for an enterprise customer to request it?

1 Like

Congrats on the new enterprise customer, that’s awesome!

4 Likes

Yeah congratz with this new customer!!

And looking forward to all the coming releases! Thursday is our Fibery day! :face_holding_back_tears: :yarn: :innocent:

4 Likes

I’m happy that you are growing and getting more business, but prioritising one big customer over lots of small ones doesn’t feel right. From the list of enterprise improvements you gave, I struggle to believe that any of those would be more beneficial to the community as a whole than fixing something like files.

I think here we probably need some patience – if they have to
prioritize some things in the short term that cement the relationship
with this customer, then it gives them extra resources to continue to
improve fibery as a whole, from which we all benefit.

12 Likes

Agreed – I too am desperately hoping that files gets an update soon, but I also appreciate @mdubakov being transparent about these things – and we know revenue-generation is crucial at all stages. My little two-seat account has gotten direct support and quality-of-life changes from posting in this forum, so I know they do the same (and should!) for their enterprise accounts.

The Fibery team has not stopped delivering valuable, user-focused updates on an extremely consistent basis. I’ll continue to trust their direction as the product grows.

10 Likes

We believe that extended templates for the Database access introduce too much complexity: imagine you’ve shared Projects DB with someone using Viewer extended to Tasks. What does this really mean? Do they get access to Tasks but only those that have been linked to some Project? How is this visualized on the access page of Tasks DB?

It gets quite messy pretty quickly, and, unlike on the Entity level, the alternatives are feasible: you can share each DB independently (there cannot be thousands of them) or share an entire Space.

It will essentially be like that, although maybe not explicitly.

We’ll aim to strike the right balance for the user :slight_smile:

3 Likes

Exactly!

No idea! Hahah yeah I agree it gets complex, and there aren’t many use cases (that can’t be solved with entity level access templates). Thought it was in the scope of what Michael said might be coming. Excited to hear more about the custom access templates for databases.

For the sake of clarity, having it explicit might be helpful. The “extend access to databases”, which is how it’s been explained on here for a while, I think adds unnecessary complexity. Just my two cents though.

One way to go :slight_smile:

1 Like

We never agree to implement things that are not beneficial for many customers and not aligned with our vision. But in terms of prioritization we did that before and will do that again, since Fibery is for-profit organization and we have to become profitable as soon as possible. We are close, but still not there yet.

I understand your concerns and we do not always execute what was planned, but we always try to communicate our intentions and progress.

7 Likes

This is MASSIVE! :heart_eyes:

I’ve counted 6 things that I’ve found awesome, specifically:

  1. Duplication automation rule to another database
  2. Update existing entities or skip duplicates via CSV import
  3. Fibery API: create-or-update (upsert) entity command
  4. AI Agent Build
  5. Fibery MCP Server is cool - but I use all AI models via n8n & OpenRouter
  6. Mobile - sexy - feels native

Any plans to build an OpenRouter integration?

1 Like

2 posts were split to a new topic: Share your Fibery MCP Use Cases

Your development velocity continues to be an inspiration.

My Fibery MCP server feedback - I really want to use it via Docker MCP toolkit catalog as described here: August 7, 2025 / ⛱️ Remote MCP Server, tons of small UI improvements - #9 by tycecycle, but the version on the catalog is still the old server.

1 Like

Hahaha guys let’s all look for Enterprises and convince them to go for Fibery AND to also make all of our favorite features a demand! :pirate_flag: :wink:

I will find that big rich organization that will demand more MAPS! :world_map:

Kidding of course (but you never know it could work :eyes:)

7 Likes

What would give you that confidence? And how is it working for you now, confidence wise?

We have to make sure that the LLM we use does not share data / use data to train, that we own all the output from it, and that the data is processed in the US or is kept under encryption (for legal reasons). We know that some of the enterprise subscriptions offer this but it has not been top priority.

2 Likes