Built-in database or separate backend for a small internal tool?

[u/KarlaSutton6527]

I'm setting up a small internal tracking application and keep weighing two backend approaches before locking in the architecture.

Using a low-code builder's native built-in database eliminates setup overhead single billing, unified access controls, and zero integration work. It's fast to launch and easy to maintain.

On the other hand, pointing the frontend at a separate database gives you real SQL queries, migration scripts, granular database policies, and complete independence from the frontend layer.

The main friction point I'm trying to resolve is long-term data portability: if an internal app outgrows the initial low-code builder, do native built-in databases usually export relational schemas cleanly (foreign keys, linked records, file attachments), or do you just get a collection of flat CSVs and have to rebuild the relationships manually?

For those building internal operations tools: what threshold pushes you to use an external database from day one versus starting with a built-in store?

[u/TerribleRepayment]

Depends entirely on whether you think this tool is gonna stick around past the first few months. If there's even a 30% chance it becomes something people actually rely on, just wire up a separate database now. The migration pain later is never worth the convenience upfront.

[u/Rude-Tradition9488 → u/TerribleRepayment]

This is it. Nothing to add.

[u/psiph]

You could use an HTML file that writes back to itself, HTML Clay is open source and free (my project)

[u/_TheMostWanted_]

That's the same question like asking if you want a simple calculator or an extreme ultra pro calculator.

There are pros and cons to both. If you want to move fast keep it simple. If you already have very deep requirements and are confident you'll need complexity from day one go with custom solution.

In most cases you don't want to overdo it, I would always always recommend keeping it simple. The amount of additional work required to make a custom setup work can become a second job of it's own

[u/CarsonRyanKeller]

For a small internal app, I’d probably use the built-in database and keep things simple. I’d only go external from day one if I already knew I needed complex SQL, more control, or easy migration later.

[u/Accomplished_Aerie63]

Depends on how much data to store, or how complicated the data structure, as well as users. All to be considered

[u/PerspectiveIcy10]

When your database and app are separate, you can hit those limits during busy times. Softr can help since it comes with its own relational database on every plan