At one stage, we looked to adopt Airtable and found a couple of roadblocks as we tried to build anything that was a little bit advanced. Was wondering if you had considered these issues.

1. We came across a bunch of examples where we wanted to hide data access to particular columns/fields. For example, we might create a staff table which had salary information on, that we only wanted to expose to managers. 

2. In this same use-case we tried to get around the problem by creating an entirely separate base for HR info, but we weren't able to pull that data into other bases.

So basically every time we were building something with data that we had to restrict (which amounts to a lot of data for business apps) we couldn't achieve what we wanted. Realise Tables is new and lots more to come, but thought I'd share this feedback of why we ended up abandoning a similar product.