Hi everyone,
We build client apps on WeWeb + Xano, and we’re reviewing our backup and disaster recovery strategy. On the Xano side, we’re covered: the Metadata API lets us export complete workspaces (data + logic) and store the archives outside the platform.
On the WeWeb side, we’ve hit a wall, and I’d like to know how others deal with it.
What we can back up today:
- The generated code, via code export or GitHub sync — great for keeping the app running anywhere.
What we can’t back up:
- The editable project itself (pages, workflows, variables, bindings). It only exists in the Editor’s internal backups/commits, which are stored on WeWeb’s side and can’t be downloaded (confirmed by support). And exported code can’t be re-imported into the Editor.
So in scenarios like an account compromise with malicious deletion, an accidental permanent deletion, or a major incident on WeWeb’s infrastructure, we would keep a running app but permanently lose the ability to maintain it in no-code. When clients ask about our disaster recovery plan (some of them have strict compliance requirements), we don’t have a great answer for this part.
My questions for the community:
- How do you address this with your own clients, especially enterprise ones with DRP/reversibility requirements?
- Does anyone use project duplication into a separate workspace/account as a “cold copy” strategy? Any gotchas?
- Has anyone obtained something specific from WeWeb on this (Enterprise plan commitments, on-demand exports via support, contractual guarantees)?
- Am I missing an option?
Thanks!