Can data be moved between databases without breaking relationships, IDs, and history?
Is it possible to upgrade from one LTD plan to another later while retaining existing data and features?
What happens if a database reaches the record limit? Does it become read-only, or are only new records blocked?
Is there a rate limit on how many records can be read or written per request?
Thanks,
Founder Team
Riya_NoCodeBackend
Sep 17, 2026
A: Hello,
1. Moving Data Between Databases: Yes. You can use our built-in Snapshots (1-click backup & restore) or export full SQL dumps from the dashboard. Because these use native database dumps, all auto-increment IDs, primary keys, foreign key relationships, timestamps, and history remain 100% intact.
2. Upgrading LTD Plans: Yes, as long as our deal is live on AppSumo. You can upgrade...
1. Do you provide a DPA (Data Processing Agreement) that we can sign with NoCodeBackend? This is essential for compliance with GDPR Art. 28 when processing sensitive health data. If yes, is it specifically suitable for mental health / therapy applications? 2. **Sub-processors**: Can you provide a transparent list of sub-processors (e.g., payment processors, CDN, analytics, ...
Founder Team
Riya_NoCodeBackend
Sep 17, 2026
A: Hi there,
Thank you for reaching out! Here are the answers to your questions:
1. Do you provide a DPA -Yes. We provide a legally binding Data Processing Addendum (DPA) compliant with GDPR Article 28 incorporating standard EU Standard Contractual Clauses (SCCs, Module 2: Controller-to-Processor). You can review it at https://nocodebackend.com/legal/dpa, and we can issue a counter-signed copy...
Q: Please Reconsider Tier 5 Record Capacity or Add-on Pricing for Production Use?
I understand the 50k–250k limits were introduced to keep the LTD sustainable. However, you’ve confirmed there is no hard architectural ceiling and that existing production customers are successfully running 4–5M+ records. Considering Tier 5’s price and positioning, could you increase its included capacity to at least 1M records per database? This would make it more suitable for serious production...
Founder Team
Riya_NoCodeBackend
Edited Sep 16, 2026
A: Thanks for the feedback. The fact that our infrastructure can technically support larger databases doesn’t mean unlimited or multi-million-record capacity can be included in the LTD tier.
The features we offer consume significant resources on our end — storage, RAM, CPU, database I/O, backups, and overall infrastructure capacity. These also create an ongoing recurring cost for us, as we...
I currently use Supabase which is affordable, mature and stable.
I'm interested in your product for a future build. 1) Why would I use you compared to Supabase? 2) What are the core differences? 3) How much are the extra row addons? I might have missed this. e.g. what do another 250k records cost?
Founder Team
Riya_NoCodeBackend
Sep 15, 2026
A: Hi! Thanks for the question.
Supabase is a mature and excellent platform, so I wouldn't say everyone should switch. The main difference is value, simplicity, and control.
NoCodeBackend provides the core backend capabilities you need — database, APIs, authentication, RLS/security, storage integrations, webhooks, AI/MCP tooling, etc. — while keeping the experience much simpler and the limits...
Q: Moving data between Databases
Can data be moved between databases without breaking relationships, IDs, and history?
Is it possible to upgrade from one LTD plan to another later while retaining existing data and features?
What happens if a database reaches the record limit? Does it become read-only, or are only new records blocked?
Is there a rate limit on how many records can be read or written per request?
Thanks,
Riya_NoCodeBackend
Sep 17, 2026A: Hello,
1. Moving Data Between Databases:
Yes. You can use our built-in Snapshots (1-click backup & restore) or export full SQL dumps from the dashboard. Because these use native database dumps, all auto-increment IDs, primary keys, foreign key relationships, timestamps, and history remain 100% intact.
2. Upgrading LTD Plans:
Yes, as long as our deal is live on AppSumo. You can upgrade...
Share NoCodeBackend
Q: Total Storage per Database
What is the actual total storage space per database, beyond the record count limit?
Does the record limit apply only to main tables, or does it also count:
related records
comments
metadata
media references
logs
system tables?
Can a single database contain:
threads
comments
media
tags
engagement history
frameworks
YouTube videos?
Can a single record contain large amounts of text, such as...
Riya_NoCodeBackend
Edited Sep 17, 2026A: Hi there,
Here is the exact breakdown of how records, storage, permitted data types, and queries work in NoCodeBackend:
0. Total Storage Space per Database (Beyond Record Count)
Record Limits (Primary Metric): Platform limits are primarily measured by record counts (rows) per database based on your tier.
Relational Data Storage: Structured data (text, numbers, JSON, dates, indexes) is hosted...
Share NoCodeBackend
Q: GDPR
1. Do you provide a DPA
(Data Processing Agreement) that we can sign with NoCodeBackend?
This is essential for compliance with GDPR Art. 28 when processing
sensitive health data. If yes, is it specifically suitable for
mental health / therapy applications?
2. **Sub-processors**: Can you provide a transparent list of
sub-processors (e.g., payment processors, CDN, analytics,
...
Riya_NoCodeBackend
Sep 17, 2026A: Hi there,
Thank you for reaching out! Here are the answers to your questions:
1. Do you provide a DPA
-Yes. We provide a legally binding Data Processing Addendum (DPA) compliant with GDPR Article 28 incorporating standard EU Standard Contractual Clauses (SCCs, Module 2: Controller-to-Processor). You can review it at https://nocodebackend.com/legal/dpa, and we can issue a counter-signed copy...
Share NoCodeBackend
Q: Please Reconsider Tier 5 Record Capacity or Add-on Pricing for Production Use?
I understand the 50k–250k limits were introduced to keep the LTD sustainable. However, you’ve confirmed there is no hard architectural ceiling and that existing production customers are successfully running 4–5M+ records. Considering Tier 5’s price and positioning, could you increase its included capacity to at least 1M records per database? This would make it more suitable for serious production...
Riya_NoCodeBackend
Edited Sep 16, 2026A: Thanks for the feedback. The fact that our infrastructure can technically support larger databases doesn’t mean unlimited or multi-million-record capacity can be included in the LTD tier.
The features we offer consume significant resources on our end — storage, RAM, CPU, database I/O, backups, and overall infrastructure capacity. These also create an ongoing recurring cost for us, as we...
Share NoCodeBackend
Q: Why Not Just Use Supabase?
Hi
I currently use Supabase which is affordable, mature and stable.
I'm interested in your product for a future build.
1) Why would I use you compared to Supabase?
2) What are the core differences?
3) How much are the extra row addons? I might have missed this. e.g. what do another 250k records cost?
Riya_NoCodeBackend
Sep 15, 2026A: Hi! Thanks for the question.
Supabase is a mature and excellent platform, so I wouldn't say everyone should switch. The main difference is value, simplicity, and control.
NoCodeBackend provides the core backend capabilities you need — database, APIs, authentication, RLS/security, storage integrations, webhooks, AI/MCP tooling, etc. — while keeping the experience much simpler and the limits...
Share NoCodeBackend