I have built several internal and external websites and apps using Teable. It is an absolutely beautiful, incredible, and highly powerful tool. From app building to automations and scripting, it handles almost everything effortlessly.

The automation and database capabilities are next level. You can:
• Create complex, multi-step automations.
• Set up automated fields that fetch and auto-populate data from one column or table to another.
• Seamlessly link different databases together.
• Connect an app to a script, and that script directly to a database.
• Integrate external APIs to push your automations even further.

The pipeline feels endless. The only limit is your imagination. If you know what you want, Teable can help you build it.

However, I ran into a major frustration. While building 2 internal tools and a public-facing static site, I wanted to use AstroJS, which is currently the best and most popular framework for static sites.

I used Claude AI to write highly detailed prompts for Teable's App Builder, explicitly requesting an AstroJS app. Instead, Teable kept generating a Next.js app. When I pushed back, the AI finally agreed to generate AstroJS code, but it simply would not execute. The sandbox preview kept throwing errors because the Teable dev environment is strictly locked to Next.js and kept overriding the AstroJS code.

I reached out to support, and their response was disappointing. They told me the app builder is built for "vibe coding" for everyday users and that they do not and will not support AstroJS.

I strongly disagree with this mindset. Most AppSumo users are tech-savvy power users. Even if we don't know how to code; we know coding terms, industry practices, and have coder friends in our circle. That also means we know about tech stacks and which tech stacks are best for specific use cases. Refusing to support AstroJS for static site generation is a big missed opportunity.

Because of this issue, I had endless conversations with the AI builder, trying to fix the AstroJS errors in a Next.js sandbox. As a result, I unknowingly burned thousands of AI credits for a project that would not even run. To be fair, the Teable team previously refunded me about 7,000 credits when the system used to consume too many credits, which I deeply appreciate. However, losing so many credits again over an unsupported framework was very frustrating.

Despite my frustrations, I do not have any major regrets. It is an amazing product. I am giving it 4 Tacos for now, but I will happily change this to 5 Tacos if they start supporting AstroJS and other essential modern stacks. And let their AI model choose the best "stacks/frameworks" for who are "vibe coders (don't know how to code at all)".

Thank you to the team for making such an innovative product. Please keep improving it!