Weād love to see a native Supabase/Postgres integration as an alternative to Airtable! Airtableās API rate limits make real-time data refresh or sync really tough. Fiberyās Postgres reports feature works great for querying, but it doesnāt let you import or convert that data into native Fibery records.
We tried building a link between our Supabase DB and Fibery with n8n, but couldnāt get it to work reliably.
A first-party Supabase/Postgres connector or an official n8n node would fit Fibery beautifully!
We ended up building a custom app hosted on Vercel which pulls from our Supabase (Postgres) and updates Fibery. Has been a game changer for us. Additionally, Fibery has webhooks integration (which we are still in the process of implementing) for realtime updates.
That being said, the setup is more complex than a native integration and I believe Fibery is missing out on a big opportunity here to help Enterprise customers sync and import raw data with ease.
Either way, weāve made it work for us. If interested, I can make some time to open source the integration we made for our custom app.
Would just like to second this!
My understanding is that Fibery uses Postgres. Integration (incl live sync) with other Postgress databases seems a logical step (?)
I love the idea that we can replicate live data in a separate open source tool that we can port to any other tool should we need to, instead of relying on CSV exports / backups. I love Fibery but relying on any single private company for data is always risky.
Just to add, specifically thinking of Supabase integration.
I agree. Fibery already allows you to sync Postgres within their Reports feature. Seems like the logical next step (Postgres, Supabase, Neon) sync to Fibery Databases/Entities.
Iāve been advocating this for years but I donāt believe Fibery team sees the value
Data has always been key and even more so now with AI. Being able to natively sync external databases with Fibery would increase customer lock-in, since theyād easily import massive amounts of business critical data without any effort (like building a custom app). It would enable businesses to build Fibery processes around their core backend data, create new relationships and now with Fibery Smart Agent, analyze.
The topic title and original post is about the former, whereas @Hendrik seems interested in at least the latter, which should probably be a separate topic.
Agreed. Since we are starting from scratch, we need to make architectural decisions from the start that would make sense for redundancy - sync out / backup.
However, while we have data in Postgres, we would love to be able to, for instance, capture data in the field on a simple mobile app to the ārootā Postgres database, which should sync back into Fibery. So I see significant benefeit to bi-directional syncing. And itās simple to create such an app that can sync with Supabase for instance. To us, this would be better than to have a Fibery app which would have to be focused on Fiberyās core mission (and probably not let us distribute a simple app to clients or agents without the requirement for 20 additional Fibery subscriptions for a simple task).
A decoupled database is just so much better to my mind.
I donāt doubt that, but if weāre trying to gauge demand (and to determine a solution that satisfies the most people) it makes sense to split the use cases in two.
There might be more people who are very interested in a āliveā backup (to Postgres or even to some other non-proprietary format) than people who are interested in syncing their existing data from Postgres into Fibery.
For what itās worth, a bidirectional sync is unlikely to happen for many months (probably even years, if ever).
@Hendrik you mentioned that itās simple to create an app that can sync with supabase, and @Illusory has said that they made a supabase custom integration. Sounds like you could team up to get something working that satisfies your needs for Mobile ā Postgres ā Fibery syncing?
As for this:
we are always open to developing features for our Enterprise customers, so if thatās your situation, reach out to us directly.
I donāt think itās simple (in fact, I mentioned that it was more complex). Although weāre generally happy that we were able to create our own custom solution, it was not without aches and pains (e.g. we still have to manage separate infra and codebase for the purpose of syncing and still havenāt gotten webhooks to work properly).
My aim is here in the forum is almost always to promote or suggest features that I think could be of benefit to many Fibery users, not just for our specific use cases.
I donāt expect this to be implemented but I still think it could be very valuable.
