> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spitzli.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up an application

> Create an application from an immutable image and check its deployment.

Select the intended project in [Console](https://console.spitzli.cloud). Application creation requires enabled Hosting, an assigned execution target and sufficient configured resources. A project record alone does not provide those resources.

## Create from an image

Where **New application** is available:

1. Enter an **Application name** and immutable **Image digest**, such as `registry.example/app@sha256:…`.
2. Review **Startup arguments**, **Application port** and **Health path**. The process must listen on the configured port and answer the healthcheck.
3. Set CPU, memory, temporary storage and replicas within the available allowance.
4. Set **Persistent storage** if the application needs durable files. The fixed-volume model supports one replica.
5. Add private environment values and select **Request application**.
6. Open the application and its operation. Wait for the rollout result and check the expected endpoint.

Where public address allocation is enabled, **Public website or app** requests an HTTPS address under the configured domain. Default Spitzli Cloud project addresses use `spitzli.site`. Use the exact address shown by Console; creating a project does not reserve a hostname. Your own domain is configured separately.

## Use a Git repository

Git self-service is not generally available. Repository authorization, project registry bindings and build execution must be explicitly activated before this route can work. The presence of a Builds screen does not open public build access.

For an activated project, follow [Git builds and deployments](https://docs.spitzli.cloud/guides/git-deployments.md). A repository URL alone does not authorize fetching or running its code.

## Connect services

For a new PostgreSQL database, create it in your own Neon account and use [Connections](https://docs.spitzli.cloud/guides/byok-neon.md) to inspect its project. Neon inventory is not an automatic SQL or runtime binding. Set the appropriate database connection details only through your application's private configuration.

Existing service bindings and guided setup are available only where explicitly enabled. Use ready services and resolve conflicting manual environment values before deploying. Disconnecting a service does not delete its data.

Mail requires a ready sending connection and verified domain. Incoming mailboxes and forwarding are activated separately; see [Mail](https://docs.spitzli.cloud/guides/mail.md).

## Recover an interrupted setup

Open the existing application or setup record before submitting another request. Use the displayed retry for the same uncertain request, or ask the operator to reconcile its result. Existing resources remain allocated after a partial failure.

Continue with [application management](https://docs.spitzli.cloud/guides/applications.md) and [persistent storage](https://docs.spitzli.cloud/guides/storage.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.