Glossary

Project and application

A project groups related work: chats, application source, configuration, history, and access. An application is a registered runnable part inside a project, such as a website or backend. A project can contain several applications. See Applications.

A template provides a starting structure for a new application. It is not a promise that a particular business workflow, integration, or sign-in method is already complete.

Chat and task

A chat is a conversation in a project. A task is the work started by a submitted request. A project queue holds requests waiting for the active task to finish.

Context is information available to the assistant while it works. Amazi manages that working context automatically; it is not the same as deleting the saved chat history.

Project instructions are saved project-wide preferences applied to new tasks. They do not override platform permissions. See Project instructions.

Preview and runtime

Runtime means the processes and environment used to run application code. Preview is the development application shown in the workspace, often inside an embedded browser frame.

A project thumbnail is a captured image used on a project card. It is not a continuously live preview.

A health check is a request used to assess whether a process responds. It does not test every user workflow.

History and release

A commit records a version of project files in Git. History lets you inspect and restore supported file versions.

A release is the production version built for publication. Updating development files does not automatically change the active release. Production is the published runtime intended for application users.

Restoring source does not restore database data. See History and restore and Publishing and domains.

Data and connections

A database stores structured records. Object storage stores file bytes. A volume is declared application-local persistent storage with its own lifecycle.

An environment variable is a named configuration value supplied to an application. A secret is a sensitive value that must not appear in browser code or ordinary chat.

An integration connects an external service. AI Gateway provides managed access to configured AI services for project applications; this differs from the assistant that builds your project.

Accounts, roles, and credits

A project role controls a collaborator's access in Amazi. An application user belongs to the authentication system implemented in your app.

Credits measure billed product usage. A completed task's total may combine several operations. Plan availability determines which functions and allowances an account can use; current values belong in the live plan catalog, not a fixed glossary.