Hey Airtable community! We use Stacker internally to build some customer-facing software as well as internal tools. I’m sure there are many of you who have built Stacker apps on top of Airtable.
If your company or product wants to connect your Stacker app to a database like Postgres, MongoDB, Firebase, etc. then you may run into some roadblocks.
Stacker does have a Postgres connector, but it has it’s limitations.
You can only use it on the enterprise plan, so needless to say it’ll get pricey
You can only import data into Airtable from Postgres. If you want to sync data from Airtable to Postgres, that currently isn’t possible
The only database Stacker supports is Postgres. If you use Firebase, MongoDB, Snowflake, MySQL or literally anything else then you’re out of luck.
Bracket released it's Stacker connection. It syncs Airtable with your database or data warehouse in either direction. With automatic 2-way syncs between these tools, Bracket enables business teams to read & write to their database without ever leaving their spreadsheet tool.
Here’s how current Stacker & Airtable customers are using us today:
Sync data from MongoDB, Firebase, etc. to Airtable so that business teams can have a read-only view of data that they usually cannot access
Spin up new instances in your Postgres based on the data already living in the Airtable that your Stacker app is built on
Turn Airtable into a UI for your database. Individuals who aren’t given access to the backend database now have a way to get primary contact with data that is relevant to them while still keeping controls on protection and permissions over data.
For small businesses, this allows you to continue to use Stacker while keeping your data in an actual database built for scale, efficiency, and cost minimization.
For tech companies, this prevents data in Stacker from staying siloed. A company that operates on a standard tech stack should have a source-of-truth for data. It also allows business teams to build internal tools with Stacker that interact with your backend data stores, without needing engineers to build & maintain internal tooling. It’s giving full power to the non-technical end users to own their tooling while still giving engineers control over permissions.