# Prelay Documentation

> Prelay is a self-hostable, encrypted notification relay. One HTTP request from any sender, delivered by an Android app. Also available as Prelay Cloud.

## Overview

- [Send encrypted notifications with Prelay](https://docs.prelay.sh/): Self-hostable, encrypted notifications. One HTTP request to send, delivered on your Android device.

## Get Started

- [Decide your path](https://docs.prelay.sh/get-started/decide-your-path): Run Prelay yourself, or use Prelay Cloud. Same protocol, same app, one HTTP request either way.
- [Quickstart](https://docs.prelay.sh/quickstart): From nothing to a received notification in under five minutes.
- [App setup](https://docs.prelay.sh/app/set-up): Install the Android app and pair it with a server.
- [Screens](https://docs.prelay.sh/app/screens): What the app looks like in use.

## Self-hosted

- [Start with self-hosted](https://docs.prelay.sh/start-with-self-hosted): Install the server, pair the app, send your first notification.
- [Deployment](https://docs.prelay.sh/self-hosting/deployment): Covers self-hosting the Prelay server. The Android app is covered in the README quickstart
- [Send your first notification](https://docs.prelay.sh/self-hosting/send-your-first-notification): One request from any sender.

## Cloud

- [Start with Cloud](https://docs.prelay.sh/start-with-cloud): Sign up, pair the app, send an encrypted notification. The relay learns nothing it can read.
- [Create the account](https://docs.prelay.sh/cloud/register): Sign up for Prelay Cloud: 14-day Pro trial, no card required.
- [Subscription](https://docs.prelay.sh/cloud/subscription): Plans (Solo, Pro, Team) differ in scale only: devices, notifications, and seats. Features are identical on every plan.
- [Send your first notification](https://docs.prelay.sh/cloud/first-notification): One encrypted request from your machine, delivered on your phone.

## Reference

- [Encryption modes](https://docs.prelay.sh/reference/modes): Mode A (server-assisted) and Mode B (sender-encrypted): who encrypts, what the relay sees, and what stays on the device.
- [Architecture](https://docs.prelay.sh/reference/architecture): Components and data flows: server, app, FCM transport, stores, and the zero-knowledge boundary.
- [API](https://docs.prelay.sh/reference/api): Every endpoint of the v1 HTTP API: auth, tokens, devices, notify, billing, errors.
- [Protocol](https://docs.prelay.sh/reference/protocol): The v2 wire protocol: envelope format, X25519 + ChaCha20-Poly1305, replay protection, key rotation.
- [CLI](https://docs.prelay.sh/reference/cli): prelay: send notifications (encrypted or not), manage devices, tokens, and server config.
- [Database schema](https://docs.prelay.sh/reference/database): The schema and its migration history are defined in a single source of truth: `server/internal/store/migrate.go`. The same schema runs on SQLite (self-hosted) and PostgreSQL (SaaS) via the dual-dialect store — all queries