🌼 Fibery strategy 2026

[jurgenappelo]

Exactly. I wish I could manage all this structured data inside Google Workspace, but I can’t. Google has all my other information but they don’t offer me what Fibery can do. Now, Google is adding AI agents to Workspace and I hope it’s going to be easy for those agents to work with my data in Fibery. Then I would have the best of both worlds.

[Yuri_BC]

Make 2026 explicitly agentic-first by turning Fibery into the safest agent-operable company OS—shipping agent identities and permissions, auditable/rollbackable action execution, and an “architect + agent first-week” onboarding flow so your target nerd leaders orchestrate agents instead of manually building complexity.

[Mircea_Braescu]

As always, a fascinating read. I love seeing how the sausage is made, especially for products that I care about. I’m glad to hear that you finally found your footing in terms of identity which is a huge milestone.

For me at this point it feels like like Fibery is in a very good spot and there are no major missing features and the biggest challenge is finding how to best make use of the tool itself (but that’s an “us” problem not a Fibery one).

Only one minor nitpick regarding the article: I would suggest you make a little addition here, to calm people’s nerves a bit (which you did much later during the article).

The reason for it is that if I were to share the article with the team (cause it’s an interesting read), some of my team mates might not have the patience to read it from start to finish, and would just recoil / bounce and the “not yet profitable” part and start worrying or create noise.

[mdubakov]

But we have this below

Note that there is almost no risk that we will run out of money, our burn rate is low and we do have more financial sources if needed.

However, I agree it is OK to duplicate this message here as well

[tycecycle]

The comparison to Linear is interesting to me. I know it’s not a main focus in the 2026 strategy, but as a happy Linear and Fibery user, that one caught my eye the most. You can of course replicate the basics of Linear in Fibery. But there’s so many QoL aspects of Linear with its deep integrations with Github and coding projects that it would take a ton of improvement in Fibery to make me drop Linear. I’m happy enough to integrate Linear into the Company OS that is Fibery and not try and run our coding related work management through Fibery. Fibery is awesome, Linear is awesome, I just think looking at them as competition in any regard is a distraction (except for implementing something similar to how they do keyboard shortcuts!)

• Better Workflow. Track cycle time and states changes history, disable some states transitions.
• ​🥇 Time tracking extension. Let people setup and track time easily.
• ​🥇 More granular dates. High-level things are planned by month or quarter, not by individual dates or precise date ranges.

Will any of these changes on the roadmap around time in Fibery dovetail with More Flexible Date FIeld? I know I asked about it recently (and have surfaced it a couple of other times in the past), but it remains my biggest roadblock to Fibery feeling seamless.

[jandrabek]

Redarding time tracking does it mean that Fibery will move in a app oriented direction? Or will this be same as time tracking that exists now? Database and entities.

[mdubakov]

Database and entities, but with some pretty UI on top

[interr0bangr]

Always love getting a sense of what’s coming next for Fibery!

I think the focus on the Architects is brilliant and as one myself I’m really looking forward to some of the “no/low-code” improvements you are prioritizing like the expansion of auto-linking logic, automation rule improvements, revamping formulas and finally getting over the hump on polymorphic relationships.

My biggest automation/rule requests as an architect:

• Adding formulas in rule filters
• Adding a “delay” option in rules
• Adding branching “if” paths in rules
• Including existing values in button triggered “user sets value” popups
• Allowing “user sets value” popups to be triggered by regular rules, not just buttons
• Adding an easy way to see/edit/add rules from within a view or entity, instead of having to leave your current context and go all the way to the database settings.

My biggest formula requests as an architect:

• Allowing the formula editing box to be dynamically expanded and resized.
• Being able to add inline comments to complex formulas.
• Allowing the use of a filter within a filter.
• Adding a “Union” function to merge multiple collections into a single collection.
• Being able to see references to the deleted field name in broken formulas.

Other random improvements that as an architect, I wish I could solve for my teams:

• Making the entire entity layout like a dashboard where related fields, rich text boxes and buttons can be moved around and resized at will to create our ideal UI.
• Increasing the maximum number of rows visible in a list without needing to click the “Show all” button.
• Increasing the maximum characters allowed in a “unit” label
• Adding an option to “Rename” an entity in a context menu (in lists) instead of having to open the entity itself.
• Being able to select what databases get included in the calculation/summary row of a table view. Or at least the option to calculate to the top level entities only.
• Allowing filtering and sorting when trying to link to an entity with a “to-many” relation, just like you can with “to-one” relations.
• Displaying fields other than just the entity’s name when linking to an existing entity so users can tell entities with the same name apart.
• Having context filtering apply to all levels of a view instead of only the top level.
• Having flexibility in column names and field alignment in table views so it’s more like a spreadsheet.

Thank you!

[mdubakov]

@julien.erny

I don’t know what it would mean for Fibery to go for this market. One caveat I see is that I’m not sure of the average nerdiness in this community .

Maybe you don’t need new features but just make yourself known in this community. Having a readily available Holacracy template could also help for sure. This is something I’ve been meaning to publish for a long time now, never finding the time to do it

I’ve read many things about Holacracy and Teal Organizations quite many years ago and implemented many things in my previous company. Overall I guess fibery can be a good fit for Holacracy process, but indeed we lack templates. Not sure how large is the market and how tools like Glassfrog are doing (last time I checked it was around 2019 maybe

[JonathanJ]

I have also researched about holacracy and the tools that are being build like nestr.io. The problem with those tools is that they are build for companies that already work with holacracy principles and are happy with the limitations of the tools.

I see how fibery could have a much better advantage of providing holacracy tooling via templates and all the other capabilities. This could make it also much easier for companies to transition to teal organisations and holacracy, because they can stay within one tool as they transition.