I recently started using Teable.ai, and I genuinely love the concept. It’s incredibly powerful for building applications with a solid database foundation, automation, and end-to-end development—all within a very short time. What really stood out to me is how quickly I could go from idea to a production-ready app, sometimes in just a day or two. It gave me a lot of confidence to build and experiment without feeling overwhelmed.

That said, there are a couple of areas that could be improved. The credit system currently lacks transparency—there’s no clear log or breakdown showing where credits are being consumed, which makes it difficult to track usage. I also noticed there’s no option to purchase one-time credits, which would be very helpful for flexible usage.

I understand that improvements to credit consumption tracking are already in progress and expected in the coming weeks, which is great to hear. It would be helpful to know approximately how much optimization we can expect—what percentage reduction in credit consumption might users see before and after these updates?

Additionally, I’m looking forward to the custom domain integration feature. Having clarity on the expected timeline for this would be really valuable for planning production use cases.

Overall, Teable.ai is a highly promising platform with huge potential, especially for builders who want speed and simplicity without compromising on capability.