⚠️ ACTION REQUIRED: Update Your WeWeb URLs to Avoid Disruptions

We are implementing important changes to our URL structure to improve infrastructure isolation and reliability across projects.‍

Please review and update your setup as soon as possible to avoid disruptions.

What’s changing

‍The following links have been updated:

• ‍editor.weweb.io/{uid} is now {uid}-editor.weweb.io‍
• {uid}.weweb-preview.io is now {uid}-production.weweb.io‍
• {uid}-staging.weweb-preview.io is now {uid}-staging.weweb.io

We have set up redirections to minimize disruption. However, issues may still occur if you rely on query parameters, hardcoded URLs, or external integrations.

Who is impacted

‍These changes affect:

• ‍WeWeb apps published on a free WeWeb subdomain (e.g. 2724f29e-53bc-4718-9ba4-48b0c8bbe9d9.weweb-preview.io is now 2724f29e-53bc-4718-9ba4-48b0c8bbe9d9-production.weweb.io)
• ‍WeWeb apps using the staging environment (e.g. 2724f29e-53bc-4718-9ba4-48b0c8bbe9d9-staging.weweb-preview.io is now 2724f29e-53bc-4718-9ba4-48b0c8bbe9d9-staging.weweb.io)
• ‍Organizations that have whitelisted WeWeb editor domainsIf applicable, you should update your allowlists to ensure continued access.

Example updates:

• from editor.weweb.io/* to *-editor.weweb.io
• from *.weweb-preview.io to *-production.weweb.io
• from *-staging.weweb-preview.io to *-staging.weweb.io

Required action

‍To avoid disruption, please:

1. Update any references to old URLs in your systems, documentation, or integrations
2. Review and update firewall rules or domain allowlists if applicable
3. Share this update with your team if relevant

Failure to take action may result in broken links or loss of access to the WeWeb Editor for your collaborators.

If you have any questions or need assistance, please contact our support team.