Projects and resources

Project

A project is the user boundary for a set of resources, environments, and deployment history. It is not a server or source repository.

Project lifecycle

Projects can be read, renamed, and archived. Archiving a project keeps the project, resources, and deployment history visible, but blocks new environments, resources, and deployments under that project.

Rename and archive in project settings only change the project-level lifecycle. They do not create a deployment, rewrite historical deployment snapshots, or immediately stop, restart, or delete running runtime state.

Rename a project

When you rename a project through Web, CLI, or API, Appaloft derives a new project slug from the new name. Pick a different name if another project already owns that slug.

Archive a project

Archive projects that should no longer receive new deployments. Archive does not delete resources, environments, domains, certificates, logs, or deployment history. Use the resource lifecycle actions when you need to clean up individual resources.

Resource

A resource is an application or service that can be deployed. It owns source, runtime, health, and network profiles.

Why resource profiles exist

Resource configuration describes future deployment behavior. It is not a one-off deployment parameter bag.