Q: Qs
A few portability/storage questions:
1. Since files/images aren't stored in NoCodeBackend, can it securely integrate with private Cloudflare R2/S3 storage using signed URLs?
2. What exactly does a full DB export include—data, schema, indexes, relationships/foreign keys?
3. Can users/auth credentials, roles, RLS policies, Pre-Hooks, webhooks and configuration also be exported/migrated?
4. If I leave NoCodeBackend, can existing users be migrated without forcing everyone to create new accounts/passwords?
5. Are automatic infrastructure backups maintained in addition to LTD snapshots? What is their retention?
6. Can exports/backups be automated?
7. Are the custom domain, extra DB and Pre-Hook add-ons truly one-time/lifetime, and do I keep them if I later change tiers?
Riya_NoCodeBackend
Aug 23, 2026A: 1. Since files/images aren't stored in NoCodeBackend, can it securely integrate with private Cloudflare R2/S3 storage using signed URLs?
Yes, securely and natively.
NoCodeBackend integrates directly with Cloudflare R2 (available on Tier 2+). You provide your Cloudflare Account ID and S3-compatible credentials in the dashboard to connect your private bucket.
NoCodeBackend generates secure, time-limited Presigned Upload & Download URLs so your client apps (iOS, Android, Web) upload and access files directly to/from your private bucket with zero egress bandwidth fees. You can also connect a custom domain (e.g., cdn.yourdomain.com inside cloudflare) for public assets like avatars or product photos.
2. What exactly does a full DB export include—data, schema, indexes, relationships/foreign keys?
It is a complete, standard SQL dump (.sql.gz) of your database containing:
Full Schema: All CREATE TABLE statements with exact data types, default values, nullability, and auto-increment sequences.
Indexes & Constraints: All Primary Keys, Unique Constraints, and Custom Indexes.
Relationships: All Foreign Key constraints (FOREIGN KEY ... REFERENCES ...) and table relationships.
All Table Data: Complete row data (INSERT INTO statements) across all your tables.
3. Can users/auth credentials, roles, RLS policies, Pre-Hooks, webhooks and configuration also be exported/migrated?
Included in the Database Export:
User Accounts & Credentials: The authentication tables (ncba_user, ncba_account, ncba_session, etc.) live directly inside your database instance. All registered end-users, password hashes, OAuth account links, and sessions are fully included in the SQL dump.
Roles & RLS Policies: Table-level RLS policies and role-based permissions are stored in your database tables and are included in the SQL dump.
Pre-Hooks & Webhooks: Custom Pre-Hook JavaScript functions and Webhook triggers run as platform-level serverless middleware on NoCodeBackend. They are not bundled inside the raw SQL database dump. (A direct JSON export for Pre-Hook and Webhook configurations is planned for a future update).
4. If I leave NoCodeBackend, can existing users be migrated without forcing everyone to create new accounts/passwords?
Yes, seamlessly.
Because your end-user authentication tables are part of your database export and store standard cryptographic password hashes, you can export your user records and import the hashes directly into another backend or auth provider without requiring users to reset their passwords.
5. Are automatic infrastructure backups maintained in addition to LTD snapshots? What is their retention?
Yes.
In addition to user-initiated snapshots in the dashboard, automated system-level database backups are maintained at the infrastructure layer. These are stored only for the GDPR purposes and disaster-recovery.
6. Can exports and backups be automated?
No. These are user-initiated exports and need to be done from the UI.
7. Are the custom domain, extra DB and Pre-Hook add-ons truly one-time/lifetime, and do I keep them if I later change tiers?
Yes, 100% Lifetime and Retained.
All add-on packs (Additional Databases, Extra Record Capacity, Pre-Hooks, AI Calls, Custom Domains) are permanent one-time purchases.
If you upgrade or stack higher AppSumo tiers later on (e.g., moving from Tier 1 to Tier 3 or Tier 5), all previously purchased add-on quotas stay with your account and stack on top of your new tier's limits. You never lose purchased add-ons when changing tiers.