# Publishing strategy to eventually replace Softr

**URL:** <https://community.weweb.io/t/publishing-strategy-to-eventually-replace-softr/4031>\
**Category:** How do I?\
**Created:** [August 25, 2023, 7:51pm UTC](https://community.weweb.io/t/publishing-strategy-to-eventually-replace-softr/4031 "2023-08-25T19:51:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericp](https://avatars.discourse-cdn.com/v4/letter/e/ea666f/32.png) [@ericp](https://community.weweb.io/u/ericp)\
**Post date:** [August 25, 2023, 7:51pm UTC](https://community.weweb.io/t/publishing-strategy-to-eventually-replace-softr/4031/1 "2023-08-25T19:51:17Z")

</div>

I’m almost done re-building my app in WeWeb with Xano, which will replace the app I built with Softr using Airtable. Softr is setup to use my custom domain.

If I didn’t want to effect use of the current app, what are my options for publishing my WeWeb app on the same domain? Create a subdomain? Really just want to test the published version outside of the WeWeb editor before pulling the plug on Softr.

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [August 25, 2023, 10:54pm UTC](https://community.weweb.io/t/publishing-strategy-to-eventually-replace-softr/4031/2 "2023-08-25T22:54:01Z")

</div>

Hi @ericp 👋

Just to clarify, you want to:

- publish the WeWeb app to test internally that everything works fine when the app is live,
- but keep directing users to the Softr app for now?

If that’s correct, you can simply hit publish in WeWeb without adding a custom domain. No need to publish it on the same domain as your live app.

Your app will be live on a URL that looks something like this `https://bunch-of-random-numbers-and-letters.weweb-preview.io` on the `weweb-preview.io` domain so people are unlikely to find it unless you share it with them so you can test freely 🙂

If you want users to test the WeWeb app but keep the Softr app as backup in case testing goes awry, then I’d recommend:

- announcing a scheduled maintenance to your users giving plenty of time for DNS records to propagate worldwide
- setting up a new subdomain in your domain registrar and connecting the Softr app on it
- updating the DNS records of your app’s domain name to connect your WeWeb app

Does that help?

---

<div class="post-metadata">

**Author:** ![ericp](https://avatars.discourse-cdn.com/v4/letter/e/ea666f/32.png) [@ericp](https://community.weweb.io/u/ericp)\
**Post date:** [August 26, 2023, 12:04am UTC](https://community.weweb.io/t/publishing-strategy-to-eventually-replace-softr/4031/3 "2023-08-26T00:04:41Z")

</div>

Thank you, that is very helpful and gives me a good plan.