I recently ran into an unforeseen problem working with Xano that is concerning to say the least.
A few weeks ago I started noticing instability in my Front End making REST API cals into Xano. I actually thought the problem was originally related to my Front End (WeWeb), so spent time troubleshooting there since I was nowhere near any of the published limits of the Xano plan that I was on Launch (Legacy).
Last week I finally opened a support ticket with Xano, thinking that maybe there was a problem with my instance. After support looked at my instance, and Xano support is amazing btw, they said that I had too many API endpoints, functions and addons, and that my instance was effectively running out of memory becuase of it. They also sent me a reference to this post: https://community.xano.com/ask-the-community/post/anyone-else-getting-cors-errors-recently-requests-erroring-and-not-AAihT0jgXuFhIBP?highlight=xfIg0MQDqVgBLHS
For reference, here are my API endpoints:
32 TABLES
237 APIS
50 FUNCTIONS
0 TASKS
The first thing they said to do was to delete as many endpoints, functions, and addons that were not being used as possible. I was able to clean up a number of addons and a couple of functions, but I can't delete my API endpionts, they are used in my application. Even after cleanup there was no change in performance. There is one mention of this in their docs which they say is a very rare scenario: https://docs.xano.com/api/api-performance/troubleshooting-a-slow-response
The second thing they said I could try doing would be to upgrade from the legacy plan, which I was paying $67/month for to the new Launch plan at $99/month since it has more resources.
I was hesitant to make this change, since it was such a large increase in cost, but I didn't realy have any option left since I can't delete my API endpoints, which my application relies upon. In desperation, yesterday I upgraded my plan from Legacy to new Launch, and I'm still seeing issues with running out of memory, of which there is no reporting for, you just know because of the CORS errors and pages failing to load in your Front End.
This is a real conundrum.
There is nothing clearly stated in the Xano pricing page about memory, or it's limits. Had I known about this massive limitation I potentially would have never started building on Xano in the first place. Although I absolutely love the product, I'm now stuck trying to figure out how to fix this without moving into Scale tiers which I realy should't need to do at this point. Even if I did move to Scaler tiers there is nothing published about available memory, I don't know that it would solve the problem.
Xano is built around creating REST API endpoints, it's frustrating that the key feature of the product is consuming an important, unpublished resource limitation and completely unmeasurable resource for any of us working in the product. It's frustrating that even though I have not yet launched, I'm already out of a resource I wasn't even aware I had to take into account when designing in Xano.
Xano team, I implore you, please remove this limitation. I think we are all happy to fit into the constraints you have set around the different plans, but this very limited, unmeasurable, and hidden memory limitation is absolutely devastating. Please help!