Feature request: separate cache between staging and production (Xano + WeWeb)

Ask us anything
1

Hi :waving_hand:

I’m using WeWeb + Xano with two branches (live and test).
The issue: when enabling Cached / Static collections in WeWeb, the staging environment shows cached production data, even though the Xano branch is set to “test.”

This makes it impossible to properly test staging data and can cause inconsistencies or even data leaks between environments.

Suggestion:

  • Allow isolated caching per environment (Editor / Staging / Production),
    or

  • Let us define the collection type (Dynamic / Cached / Static) depending on the environment.

This would be a huge improvement for teams working with multiple Xano branches. :folded_hands:

If anyone knows a simple and reliable workaround for this, I’d love to hear it!

2

Hi Romain, :waving_hand:

thank you for your recommendation,

I’m going to submit your feedback to our team.

1 Like
3

Hi Romain

Could you tell us what’s your use case for caching Xano? Caching is mainly useful for integrations like Airtable, where you’d want to not expose you data directly on the frontend. But with Xano, you anyway get a dedicated backend. So I’m curious to know why you want to cache?