Overview
Snapp is designed as a multi-tenant, self-hosted URL management platform with strong boundaries between domains, organizations, and users.
Features are not presented as isolated checkboxes. Each one is part of a coherent system built around:
- explicit ownership
- strict permission models
- predictable behavior under load
- server-side enforcement
This section documents Snapp capabilities by area.
Each feature has its own dedicated page with implementation details and constraints.
Feature areas
Custom URLs
Create, manage, and resolve short links with full control over domains, slugs, and lifecycle.
Includes domain binding, per-organization ownership, collision handling, and fallback behavior.
See Custom URL
Authentication
Authentication is built on top of Better-Auth and extended to support multi-host setups, email workflows, API keys, and optional social providers.
Includes email verification, password recovery, OTP, and TOTP.
See Authentication
Multi-Domain Architecture
How Snapp leverages Better-Auth organizations to provide multi-domain access while preserving isolation and ownership.
Teams
Teams provide scoped access to resources inside an organization through explicit permission policies.
See Teams
Metrics
Metrics are collected server-side and aggregated per organization, URL, and time range.
Includes internal vs external traffic, UTM tracking, referrers, devices, browsers, and geographic breakdowns.
See Metrics
Third-Party Integrations
Optional integrations extend Snapp with external services for analytics, security, and automation.
Currently includes Umami analytics and VirusTotal reputation checks.
Notes
- All features are self-hosted
- No external service is required by default
- Each feature page documents:
- scope
- guarantees
- limitations
- operational impact