Overview

This section covers the minimum steps required to bring a Snapp instance online and understand its operational model.

Snapp is designed to be self-hosted, stateful, and explicit. There are no hidden defaults, no external dependencies forced at runtime, and no configuration split across multiple layers.

Getting started means:

• deploying the application
• configuring it intentionally
• understanding what state is created and where

Each page in this section builds on the previous one.

What you need

Before deploying Snapp, ensure you have:

• A Docker-capable environment
• Persistent storage for PostgreSQL
• A domain (or domains) you control
• Basic familiarity with containerized services

Nothing else is required.