> ## 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.

# Console and workspaces

> Find your workspace, projects, connections and resource usage.

Open [Spitzli Cloud Console](https://console.spitzli.cloud) and select your workspace. The main website is [spitzli.cloud](https://spitzli.cloud).

## Find the right resource

| Resource | What it represents |
| - | - |
| Workspace | Your customer account, members, enabled services and limits |
| Project | A group of related resources within a workspace |
| Application | A running workload with configuration, deployments and logs |
| Website | An independent website with its own content and CMS |
| Database service | An existing database with its own access and lifecycle |
| Connection | Permission to access a provider account, such as Neon |

Creating a project does not provision a database or application. Connecting Neon lists authorized projects; it does not deploy a database.

Use **Connections** to connect your own Neon account, **Plan and usage** to review workspace limits, **Domains** for domain management and **Members** for permitted membership changes. Product entries depend on your workspace's enabled services.

## Customer and operator access

Customers see their assigned workspaces and resources. Platform operators also manage infrastructure, customers and service permissions. An operator's read-only customer preview blocks changes. If an operator is explicitly acting as a customer owner, the displayed customer permissions apply; this is a separate mode.

## Follow an action to completion

An accepted action may create an operation. Open its details and wait for the final result, then check the resource itself. A queued restart or successful build does not establish that an application is serving traffic.

> [!TIP]
>
> When reporting a problem, include the resource and operation IDs. Remove API keys, cookies and private connection strings.


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