Projects and templates

Start from an idea or a template

Create a project from a request on Home, or choose a prepared starting point on Templates. A template can contain one application or a complete multi-application project. Using it creates your own editable copy of the published template, including its applications, configuration, installed dependencies, and any database contents and Storage files included in that template. The database and Storage belong to your new project. The original project's chats, Git history, environment values, and integration connections are excluded when the template is prepared.

Some templates are available to everyone; others require template access in your plan. Templates that require a plan always show a badge in the lower-right corner of their preview, including when your plan grants access. Click Upgrade your plan → to open Plan and review the available functions. Updates to a template affect future copies; they do not replace projects you already created from it. Application addresses in copied source may still point to the original: ask Amazi to check the new project's references before using it.

When a template has a published website, click its image or the website button beside its name to open it in a new tab. The link uses the connected custom domain when available, otherwise its Amazi production address. Preview images and website links are generated automatically. Use template creates your own project separately.

Published template websites show a Template badge. Your own project created from a template follows the ordinary publishing and plan rules.

For web, server and mobile starting points, see Supported applications. You do not need to choose a technology: describe what the application should do. Mobile requests normally start with an app that opens your website (WebView). You can also request React Native/Expo; Amazi will explain the differences and confirm your choice. The guide explains what appears in Preview and how to request an Android installation file.

Find and organize projects

When Amazi needs your answer, the project card shows a question icon in its preview. Publishing and sharing indicators remain beside the project details.

The Projects page separates projects you own into Active and Archived collections. Projects shared with you appear in Shared. Search and sorting help you return to an existing workspace. Your plan can limit the number of projects you own and the applications inside each project. A downgrade keeps existing resources but can block creation of another one until capacity is available.

The modification date advances only when a new chat message is saved or a new commit appears in History. Renaming, settings changes, and background status updates do not change it. A project without messages or commits shows its creation date.

While a project is being prepared, copied, or changed by Amazi, its card shows Working on your project....

Copy a project

Making a copy creates a separate project and prepares its files in the background. All applications, their configuration, and installed dependencies are copied. Five options start off: Git history, chats, database contents, Storage files, and environment values and integration connections. Enable the data you want to carry over. The environment option includes saved secrets and integration connections; enable it only when the new project should receive them. Copying database contents creates an independent database. The Storage option copies application files into the new project's own storage and keeps their identifiers. Select both database contents and Storage files when your records reference uploaded files. Chat attachments are included with chats.

After copying, review and send the suggested request in the copy's chat input. Ask Amazi to check the project and update references to the original, including API URLs, domains, and connections. The draft is saved to your account and is not sent automatically. An independent database does not prevent copied application settings from pointing to the original API.

While copying, Preview shows the standard While you wait screen. The notice above the chat input explains that sending becomes available when copying finishes; your draft stays saved. You can leave and return to the page. If copying fails, the page shows an error instead of an endless creation screen. Make a new copy from the original project; the original is unchanged.

The suggested request includes the original project's link and asks for a review of both source code and environment variables across the whole project. When chats are included, their attachments are also copied.

The copy does not include:

• production releases or custom domains;
• GitHub repository links;
• application volumes.

Applications receive new identifiers; copied environment and integration bindings point to the new applications.

Archive and restore

1. Archive removes the project from Active and makes it owner-only. Only the project owner can archive it from the web workspace.
2. Restore returns an archived project to active work, including projects that have never been published. Archived cards retain their saved preview image when available.

Only the owner can perform these actions or transfer ownership. See Collaboration and access for project roles.