Hey there! At our company, Bit Complete [1], we use Airtable a bunch for managing operations. We really like how easy it is to throw up a form to collect information, or to build automations for offline processing like aggregations.<p>One challenge we kept running into was how to build more complicated interactive apps using the API, while maintaining fine-grained access control to Airtable data. Airtable ties identity to API access control via API keys, which makes it very hard to build apps with realistic access control needs.
So we built AirQL! [2]<p>It’s a utility layer between Airtable’s API and custom/internal web applications that supports Google authentication and flexible access control.<p>We’ve found that it makes it practical to build simple, useful internal apps, that still benefit from everything else Airtable has to offer.<p>If this sounds interesting, check out the docs [3], try out the product, and let us know what you think! We’re looking for feedback and to learn if this would be useful to others. If you have questions or suggestions, please get in touch at airql-support@bitcomplete.io.<p>[1]: <a href="https://www.bitcomplete.io/" rel="nofollow">https://www.bitcomplete.io/</a>
[2]: <a href="https://www.airql.dev/" rel="nofollow">https://www.airql.dev/</a>
[3]: <a href="https://docs.plz.dev/airql" rel="nofollow">https://docs.plz.dev/airql</a>