Thank you for taking the time to write such a detailed and honest review. We truly appreciate it — feedback like this helps us see our blind spots and improve. I'd like to address each of your points directly.

On row limits:
We'd like to offer some context here. Teable and NocodeBackend are quite different products — NocodeBackend is an API backend generator aimed at developers, while Teable has a collaborative no-code database with rich field types, real-time collaboration, and a spreadsheet-style interface, much more in the same category as Airtable.
Compared to Airtable — which we believe is the more appropriate comparison — Teable offers significantly higher row limits at every tier: Teable Pro supports 250,000 rows vs. Airtable Team's 50,000 (5x more), and Teable Business supports 1,000,000 rows vs. Airtable Business's 125,000 (8x more). These are also not hard caps — you can subscribe to additional capacity as your needs grow.

On VLOOKUP / Joins between tables:
We owe you an apology on this one. Teable does support this — we have a built-in feature called Conditional Lookup that lets you automatically match and pull data from another table based on conditions (e.g., matching IDs), very similar to VLOOKUP in Excel. Unfortunately, the AI assistant misunderstood your request and pointed you toward a manual scripting approach instead. That shouldn't have happened, and we're sorry for the wasted effort. If you'd like, we'd be happy to walk you through how Conditional Lookup works.

On duplicate detection and cleanup:
You raise a fair point. We don't yet have a dedicated one-click deduplication tool, and we'll seriously consider adding one. In the meantime, the AI Chat can identify duplicate records via SQL queries and help you bulk delete them — but we fully acknowledge that's not as intuitive or discoverable as a built-in feature should be.

On semantic search / embeddings:
We appreciate you sharing this perspective. When we asked about use cases, it was genuinely to understand how our users would benefit most, so we could prioritize effectively — not out of doubt about the value of the technology itself. It's a direction we're actively evaluating.

On the AI assistant and App Builder credits:
We understand this was frustrating, and we're sorry. To be transparent: BYOK (Bring Your Own Key) currently applies to AI Chat (table-related AI features), but App Builder does not support BYOK yet — so usage there still consumes Teable credits regardless of whether you've connected your own LLM. We recognize this is a real limitation and should have communicated it more clearly upfront.

On AI memory / context persistence:
You're right — the lack of persistent memory across conversations is a real pain point. It's something we're actively working on improving, and we understand how frustrating it is to repeat context every time.

On large-scale data imports:
The current AI-driven import works in small batches, which makes it painfully slow for larger datasets. That's not the experience we want to provide. We're actively working on making large-scale imports significantly faster and more reliable, and an update is coming very soon.

On server location and GDPR:
We understand the importance of data protection for businesses serving EU clients, and we do want to support GDPR compliance. Honestly though, in the near term we don't yet have enough resources to complete all the related compliance work (such as EU region server selection), and we can't provide a confirmed timeline yet — we're taking things step by step. If your use case does not involve storing or processing third-party personal data (PII), EU customers can use our Cloud service normally. We appreciate your understanding on this.

On credits:
We've identified that in certain real-world building scenarios — especially long conversations, large data files, and extensive data operations — credit consumption can be significantly faster than users expect. That gap between expectation and reality is on us.
We want you to know: improving credit efficiency is now our team's #1 priority. We will be rolling out improvements within days to significantly reduce credit consumption.

In closing:
We hear you, and we take this seriously. Some of the issues you ran into were caused by the AI assistant not guiding you to the right built-in features — that's clearly something we need to fix. Others are genuine product gaps we're working hard to close. And some come down to documentation and onboarding that didn't set you up for success. None of that is okay, and we're committed to doing better.

Thank you for giving Teable a serious look, and for holding us to a high standard.