Go live

Publish your app

Choose a live address, publish a tested build, and update it safely.

On this page

Publishing makes the latest successful build available at a public website address. Building and publishing are separate, so changes you make in the editor do not replace the production version until you publish them.

Check the app first

Before opening Publish, use the preview to complete the main journey that visitors will use. Check the layouts you changed at desktop and mobile sizes. If the app uses accounts, saved data, uploads, or server functions, test those paths too.

Also remove sample content and check page titles, links, and contact details. Publishing uses the current built version, so finish or discard any unfinished change before continuing.

Publish to production

The steps below describe the standard Ahamo Cloud publishing flow. Enterprise tenants can also configure customer-cloud destinations and publishing controls; see Your cloud or Ahamo Cloud.

  1. Open the app and choose Publish at the top of its pane.
  2. Choose Publish to production.
  3. Review the website URL. Select the displayed suffix if you need to edit it, then choose Next.
  4. In Who can see this website?, choose who can open the app, then choose Next. Anyone with the link lets anyone who has the link open it without signing in. It isn't listed anywhere and search engines don't show it. The other choices ask visitors to sign in to Ahamo first.
  5. On Review and publish, check the URL and app name, then choose Publish. If the app has security risks to review, a Check security step lists them. Review them, choose Ask Ahamo to fix them, or Continue anyway. Your organisation can require a scan before publishing.
  6. Wait for You just published your app. Open the displayed link or use Copy to copy it.

Publishing can take a moment. While it is running, the control shows Publishing... and prevents another publish from starting. If the operation fails, read the displayed error and resolve it before trying again.

Show the app in search engines

An app that anyone with the link can open is kept out of search engines, because every page says so to search engines, while link previews in chat and social apps still work. To let people find it through search, open Publish, choose Change next to who can see the website, and turn on Show in search engines. You can also change it in the app's settings under Who can open your app, separately for production and staging. The change applies right away, without publishing again.

Choosing any other option turns the switch off again.

Embed the app on another site

Only the app's own pages can show it in a frame. To show it inside another website, add that site's address, such as https://shop.example.com, under Sites that may embed this app in the app's settings under Who can open your app, or ask the AI in the app's chat. Only exact https addresses are accepted, up to 10, and the change applies right away. A listed site could also trick visitors into clicking inside the app, so add only sites you trust. Embedding works only for an app anyone with the link can open, and choosing any other option clears the list.

Verify the production version

Open the website URL in a private browser window or a browser profile that is not signed in to Ahamo. Confirm that the expected app and page title appear, follow the most important link, and complete the main visitor journey once.

For an app with a backend, use safe test data and check the production behavior that changed. Preview data is not proof that production data or access works. If the release needs a production-like check first, see Use a staging preview.

Publish an update

After a later build succeeds, Publish shows Pending changes to publish. Test the change in Preview, then choose Publish. What goes live lists the saved changes since the live version, and anything to check before it goes live. The live version stays until the new one passes Ahamo's check.

Choose Update production. Wait for the completion screen and repeat the smallest live test that covers the change. A successful build alone does not update the live app.

If the live version has a serious problem and should no longer be reachable, follow Unpublish an app. For URL details, including changing the suffix, see Understand app addresses. To open the app at a domain you own (Pro and up), see Connect a custom domain. If publishing fails after the visible cause is resolved, use Troubleshoot an app build.

On this page