Publishing and domains

Publish the complete project

Open Manage publishing from the project menu or workspace. The first Publish all and every later Update all create one immutable project release containing every application enabled for publication at the same Git commit and environment snapshot. Individual application lifecycle actions are intentionally unavailable: either the complete candidate becomes active or the previous complete release remains the user-facing version.

Amazi includes web and server applications in publication. Mobile, desktop and other application types stay in the catalog with any available preview, but their publishing status is gray and they are skipped by Publish all and Update all. Mobile and desktop applications are distributed separately, for example as installation files or through app stores. You can also ask Amazi to disable publication for a specific web or server application.

Publishing stays available while Amazi is working. A manual publish uses the latest already committed Git revision at the moment the release starts; later or uncommitted agent changes are not added to that release. When Amazi itself uses the production tool after changing the project, it first commits the current task changes and publishes that checkpoint.

Development and production remain separate runtime surfaces: publishing builds managed production images instead of reusing editable development containers or mutable development volumes. The managed PostgreSQL database is the exception: development and production connect to the same project database and therefore read and write the same data. Public browser applications receive permanent Amazi system addresses. Private server applications build and run inside the release but do not receive a public browser address.

Update, stop, and resume

When files or environment values change:

1. Confirm the available update.
2. Allow every application to build and pass its health check.
3. Verify the complete candidate after activation.

If candidate activation fails, Amazi keeps or restores the previous complete release. Activation can still cause a brief interruption.

To cancel a publication that is still running, click Stop the update on the left. The previous publication state returns: an existing site keeps its previous version, and a first publication returns to unpublished. Cancellation does not show a failure or add a chat message or notification.

When you ask Amazi to publish, it waits for the build and startup result. If publishing is still running, Amazi can check that same release without starting another one. A continuing release is not a build failure. After activation, check the public address as well as the publication status.

A failed application card keeps the complete production diagnostic available for download. Ask Amazi attaches those exact bytes to a new request and starts the required Debug and Production workflows. Amazi first distinguishes an application-code failure from an Amazi platform or service failure, changes project files only when the evidence supports it, and publishes a correction only when it is ready.

Stopping production removes every application route and container while preserving the immutable release and declared production data. Resume starts that same release without rebuilding. A stopped release must be resumed before it can be updated.

Connect a custom domain

Each publicly routed application can own one additional domain alongside its permanent Amazi address. Depending on the owner's plan, choose a named Amazi address or an external domain. Only one of these options can be connected at a time.

For a named Amazi address, enter a name, select Check availability, and then Connect address. Your address will be name.app.amazi.pro. Amazi connects it automatically; no DNS configuration is needed.

For an external domain:

1. Enter a hostname without protocol or path. Amazi automatically converts internationalized letters to the technical ASCII form used by DNS.
2. Add the exact TXT verification record at your DNS provider.
3. Add A for an apex domain or CNAME for a subdomain.
4. Keep proxying disabled during verification and allow time for propagation.

Amazi custom-domain routing currently uses IPv4, so a conflicting AAAA record blocks verification. Removing a domain leaves the system address available. Domain routing reuses the current application image; it does not create a new project release. Publishing requires Editor, Full access, or ownership. Custom domains depend on the owner's plan. Badge-free publishing is checked against the account that starts publication; without that feature, publication remains available with the Amazi badge.

Published template websites display a Template badge regardless of the publishing account's plan. Projects you create from a template follow the ordinary publishing rules.

The Development preview, Made with Amazi, and Template badges each have a close button. Closing a badge hides it until the page is reloaded.