Publishing and domains

Publish the complete project

Click Publish in the workspace toolbar to open the publishing popover. The panel shows the publication status and last publication date. Switch application tabs to view each address. Publish is disabled when all enabled applications are already on the current version; an available update is marked in yellow. Click Publish to publish changes and confirm an update when prompted. The release includes all applications enabled for publication; if an update fails, the previous complete release remains available.

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 when you publish. 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.

The project's publishing status and update indicator include only applications enabled for publication. An unpublished mobile app or an old deployment of a disabled app does not make an otherwise current release appear outdated.

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 start with a generated Amazi address. Private server applications build and run inside the release but do not receive a public browser address.

Updating Amazi's API does not stop your published applications. Features that call Amazi's API, such as managed file uploads, may be temporarily unavailable during maintenance. Retry them after the update finishes.

Click inside the project preview to close the publishing popover and continue using the preview. A domain editor or confirmation dialog stays open until you close or complete it.

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 beside the publishing button. 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.

Deleting an application that has never been published removes it immediately, including its generated Amazi address. An application with an existing release remains pending removal until you update publishing.

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.

If committed files contain an unsafe link, publication stops with a diagnostic identifying that link. Ask Amazi to fix the tracked files and create a new version before publishing again; repeating the same version will not fix it. Temporary contention with another project operation is retried automatically and does not by itself mean that the application build failed.

Connect a custom domain

Each public application has one production domain: its generated Amazi address, a named Amazi address, or an external domain, depending on the owner's plan. Only the selected domain works. Choosing another domain stops serving the old address; it does not redirect visitors.

Existing connected domains remain selected, including those awaiting DNS verification or showing a verification error. Applications without a connected domain keep their generated address. A selected external domain becomes available after successful DNS verification; its previous Amazi address is not available while verification is pending or failed.

To change an Amazi address, click the pencil beside it, enter a name in the dialog, and click Apply. If the name is taken, choose one of the available alternatives or enter another name, then apply it. Your address will be name.app.amazi.pro. Amazi connects it automatically; no DNS configuration is needed.

For an external domain, open the connection dialog from the Custom domain card. If your plan does not include this feature, the card shows a crown and upgrade guidance.

When Cancel is the only action at the bottom of the domain details, it spans the full width. Click it to close the dialog.

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, then click Verify DNS. Each record has separate name and value copy buttons.

Amazi custom-domain routing currently uses IPv4, so a conflicting AAAA record blocks verification. Removing a named or external domain selects the generated Amazi address again. Domain routing reuses the current application image; it does not create a new project release or start a stopped application. 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.