Front-only plan: safe to downgrade?

Hi everyone :waving_hand:

First of all, congrats to the team for the recent evolution of WeWeb and the introduction of these new plans — it’s great to see the product expanding in this direction :rocket:

I’m currently reviewing my setup in light of the new pricing (especially the “front-only” plan vs the more integrated full-stack options), and I’d really appreciate some guidance before making any changes.

My current setup

  • Frontend: WeWeb

  • Backend: Xano (database + business logic + APIs)

  • Auth: Xano auth via the WeWeb plugin

  • Custom domain

  • Current plans: “Essential” (seat) + “Scale (legacy)” for the project

So in theory, I’m using WeWeb as a pure frontend and Xano as my full backend.

My goal

I’m considering switching to the front-only plan, mainly to avoid paying for overlapping services.

Where I’m not fully confident is this:

:backhand_index_pointing_right: I believe I’m not using any backend features from WeWeb
…but I’m not entirely sure how to properly verify that.

My questions

  1. What should I check before downgrading?
    Is there anything specific I should review in my project to make sure I can switch to the front-only plan without breaking anything?

  2. Workflows:
    If all my workflows are only:

    • frontend logic (variables, conditions, UI interactions)

    • API calls to Xano
      is it safe to assume they will behave exactly the same in front-only?

  3. Auth (Xano plugin):
    Since I’m using Xano auth via the plugin (and not WeWeb auth), I assume this should be unaffected — but I’d love confirmation.

  4. Custom domain and staging:
    I’m currently using a custom domain and also a staging environment.

    My staging environment is currently accessible via a WeWeb domain (e.g. https://[uuid]-staging-production.weweb.io).

    I’d like to double-check that there’s no impact on:

    • access to staging environments
    • staging/preview URLs provided by WeWeb
  5. File storage / assets:
    I noticed that some plans include file storage (e.g. 5 GB), while the front-only plan doesn’t mention it.

    In my current project, I have some images hosted directly in WeWeb (via the asset manager).

    Should I expect any limitation or impact on:

    • existing assets (will they remain accessible?)

    • uploading new files?

    Would you recommend migrating those assets to an external storage (e.g. Xano / S3) before switching plans?

My understanding is that WeWeb is now offering optional backend capabilities. A priori, I don’t think I need these new features, and I’m trying to confirm that assumption — because if that’s the case, the front-only plan seems like a perfect fit for my setup.

Thanks a lot in advance for your help :folded_hands:

2 Likes

Hey Romain :waving_hand:

I think you’re safe to keep the frontend only plan :slight_smile:

If you didn’t touch anything in the new Data & API or Settings tabs, you’re not using any backend feature.

If you were invited to select a server location at some point, then you’re using a backend feature:

CleanShot 2026-04-09 at 10.24.46

If you want to be double safe, don’t hesitate to reach out to the support team via the chat so they can take a look at your project and confirm :slight_smile:

Don’t worry, we automatically detect when you are using the backend and prevent you to pick the front-end only plan in the UI.

Front-end only plan has access to all features which existed before the release (including your asset manager/storage) and every new features not involving a back end setup like showed by Joyce.

1 Like

Hey Romain, adding to what Joyce & Alexis already said:

  • you can keep your current plan if it suits your need, we will continue to support it in the future
  • if ever you want to use the new plans, then your natural path would be to buy the front-end only plan + the staging add-on. The total cost for both would be $120/mo + usage based pricing for bandwidth usage over 10go/month. So the cost would be +/- equivalent to what you pay today with your plan, depending your bandwidth consumption.

hope that helps!