Best practise for backups and maintenance for client on essential plan

Ask us anything
1

Hi,

I’m on the partner plan building the app for the client with backend as supabase.
I will be transferring my project to my client who wishes to be on essential plan. I have a few doubts in regards to taking backups and providing maintenance to client post transfer from my Partner plan :-

  1. Essential plan doesn’t give manual backup options. Can i create copies of the project and label them with a date and store them in a folder in the client’s workspace since i will be added to their workspace for maintenance?

  2. Is there a limit on how many copies i can make of the live app ?

  3. In a scenario where i want to revert back to an older date copy, do i need to re-setup hosting on weweb and the backened(supabase) or would each copy that i’ve made, be ready to publish as soon as i unpublish the current live app? i.e. Creating a copy sets up everything else also ready to deploy whenever needed ?

  4. As i’ll be on the partner plan and added to the client’s essential plan’s workspace, can I transfer back the app to my partner plan to properly debug (using staging) and when i’ve finished the upgrade, i can again transfer it back ? OR is this process too tedious/not possible and i should just debug on a copy of live app in the client’s workspace itself and then manually copy the changes to the live app ?

  5. Given the system proposed by me to manage backups on the essential plan, what am i still missing out by not just taking the Pro Seat plan ? Client doesn’t need the unlimited seats nor the 25M Tokens. The unlimited manual backups is the only attractive feature that comes with it and as per my understanding backups would be tied directly to the live app so its going to be more convenient/error proof to take aback ups and restore them without having to change the published URL for users i guess ? Any other major advantages on this front vs my workaround ?

Cheers
@Slavo @Agustin_Carozo please guide :folded_hands:

2

As far as I remember

  1. No
  2. No
  3. Yes
  4. No
3

  1. yes can create duplicates of the project and then transfer those duplicates to your customer’s workspace. Not in a folder, however, WeWeb’s workspaces do not support folders (yet).

  2. no limit

  3. each app duplicate is a normal app with al the bells and whistles. You can publish any of the duplicates at any time to the internal WeWeb domain. If you want to publish it to your custom domain, u=you need to remove that domain from the live project first and then add it to the next one.

  4. No, transfers are only from Workspace with the Partner plan. If your client has the Essential plan, you will not have the option to transfer.

  5. The difference between Pro and Essential are the ability to add more seats, more AI tokens and the backups.

    In my opinion, the workaround you propose is not worth it, it will create a substantial admin overhead and work for you, as welll as end user friction. With the native backup feature, if you see something is not right, you just load a previous version of your editor and then publish it and your are done - there will be no disruption.

    With your workaround, you have to remove the domain from the active app which will take the app offline, then you have to attach the domain again to the new version, you have to make a new DNS entry, wait for DNS propagation, etc.