Understand app addresses
Check an app’s built-in address, rename it safely, and verify that shared links point to the intended published app.
A published app has an Ahamo website address that people can open without entering the editor. Use the address Ahamo displays rather than constructing one from an app name.
Find the address
Open the app and choose Publish. For an unpublished app, Publish to production shows the website URL before the review step. After publication, the published summary labels the current link Website URL and provides a copy control.
The app’s settings also show a Built-in URL. Its workspace form contains both the app and Workspace suffixes, for example https://appointments.northstar.ahamo.app. The production publish flow can instead show a shorter claimed suffix such as https://appointments.ahamo.app. These are published addresses; the editor preview and staging link are different destinations.
Always copy the displayed Website URL when sharing the production app. Ahamo can reject a suffix that is invalid or already in use.
Change the website URL suffix
The supported edit path is in the production publish flow:
- Open Publish and choose Publish to production. For an existing release, open its published summary and choose Edit settings or Update production.
- On Your website URL, select the displayed address.
- Edit only the suffix before
.ahamo.app, then choose Next. - Complete Review and publish, and publish or update production.
- Copy the URL from the completion screen.
Treat a suffix change as a link change. Ahamo does not promise that the previous URL redirects, so update links you control only after the new address works.
Verify a link
Open the copied URL in a private window. Confirm that it opens the expected production app rather than Ahamo, a preview, or staging. Check the page title, one internal link, and the main visitor journey. If the app has its own sign-in, test with a safe app-user account.
After a suffix change, test the new URL before replacing bookmarks or published links. If it does not open the expected app, return to Publish and compare the exact displayed address. See Publish your app for the full release path or Troubleshoot an app build if a confirmed production URL still fails.