Moving my database to Xano


I have finished my beta app but it is very slow so i want to externalize my database for app speed purpose.

What do you advice me to do ? I have a lot of collections link to the users’ collection , is it smart to move those collections too? Or do i only migrate collections without any links to users?


Hi @batouuu,

Here’s a great post by James (@James_App_Maker) that will useful here! : External database - #2 by James_App_Maker

Love to know other makers thoughts too! :smiley:

Thank you

Here is my view on it, we cannot say different DBs measure equally and fit same purposes. It all depends on your needs:

Lacks a lot on filter functionalities, all needs to be filtered from the frontend. It has basic API endpoints with no filter engine (Similar to Airtable and XANO, but these have backend filter).
Apps that rely a lot on images, you will consume DB fast, you should then use AMZ S3 that has a small cost on top but use Integromat or tools like Adalify for this (Another cost on top)
Possibility of creating relationships with other collections. but only simple relationships (Airtable and XANO you can do multiple and complex relationships)

Free up to some 1200 records.
10$ 5000 records
You can create more complex relationships than Adalo
only 2GB of attachments (Not good for media apps), (5GB for the 10$ plan) or use AMZ S3 as similar to Adalo (previous point)
More filtering on the server side (Airtable)
Also filtering from Adalo side

Free up to 10.000 records (No record limit but with a 3GB database storage in the 59$ plan, this is a lot just for records not counting media)
You can create more complex relationships than Adalo and Airtable
No disclosure of GB for media in the free plan (59$ plan you get 10GB) or use AMZ S3 as similar to Adalo (previous point)
Region selector (not possible in Airtable or Adalo) - Paid Plan only
No rate limit (Airtable and Adalo have a rate limit) - Paid Plan only, but free plan has generous rate limit better than Adalo and Airtable.
You can add much more complexity on the XANO side to transform data before getting it in Adalo

To sum it up

Good for apps that rely in Basic/Medium complexity
Good for apps that you don’t rely on massive amount of Media
Good for apps that don’t have complex relationships
Best price

Good for apps that rely in Basic/Medium complexity (But one level up than Adalo)
Good for apps that rely more in Media than using Adalo (Here you can always hack by using more Bases)
Good for apps that need more relationships or filters than Adalo
Paid plans also gives you some automations behind
Worse priced than Adalo but better priced than XANO

Good for apps that rely in high complexity
Good for apps that rely more in media than airtable and Adalo
Good for apps that need more relationships and filters than Adalo and Airtable
Has a higher price compared to the others (if you consider paid plans)

There are other ways to go also behind these 3, but requires more technical knowledge and time to setup as Adalo is not compatible out of the box.

I am biased as I prefer to use all with XANO (I am not affiliated at all, just my go to DB, Backendless and Supabase are also great), whether simple or heavy apps, but some customer ask for Airtable and Adalo, I then use it, it is all a matter of bugdet, complexity and data volume vs media volume.

Have fun Adaloing :slight_smile:


my two cents, keep the user collection and the user management in Adalo.
The rest in Xano, which works very well and will allow you to do many more things.

Hi ,
You have to use both or XANO. By not using the Auth via XANO, you are exposing the XANO API endpoints publicly.

You can always set a type of password on the XANO side, but it will still not be as secure as using the AUTH side of XANO.

Yes, I know that, but I have another way to make api secure.
If you use Auth via Xano you can not use push notifications nor login with google and apple.
The problem is not Xano, is the Beta User External collection in Adalo.

have you tested through abracadalo push notifications?

That’s not the problem, you could also send it from Zapier or Integromat, the problem is that if you don’t have a user in Adalo you don’t have a recipient for the notification.

Maybe getting the user record from the External User ID from a custom action and then get the email from it and save it on a input and use that input in the Notification custom action recipient or after the getting user record custom action add that notification custom action and for the recipient add the email from the get user record custom action? I could be wrong here :zipper_mouth_face: Just thinking

We could actually combine both, by maybe adding an custom action to create and login the user without password.

What I did in another low code platform was exactly that, User logins via AUTH XANO, then receives an email with magic link to login user. the email contains a password. So then the Password is actually the Adalo password (I made it even random to change all the time), then in the last step, it logins the Adalo user. So in the end it becomes a sort of 2FA.

Didn’t try with Adalo yet.

1 Like

Good comparison. I think xano is great and powerful.

I think so too