---
title: "Deploy Sessy"
description: "Open-source email observability for AWS SES"
category: "Observability"
url: https://railway.com/deploy/sessy
---

# Deploy Sessy

Open-source email observability for AWS SES

**[Deploy Sessy on Railway](https://railway.com/template/sessy)**

- **Creator:** Techulus
- **Category:** Observability
- **Total deploys:** 5

## Template content

### sessy https://raw.githubusercontent.com/marckohlbrugge/sessy/28b18d9303675422adff350b94142359a43b0192/docs/icon.svg

- **Image:** ghcr.io/marckohlbrugge/sessy:main
- **Public domain:** Yes

## Documentation

# Deploy and Host Sessy on Railway

Sessy is an open-source email observability tool for Amazon SES. It gives you a beautiful interface to track what happens after you hit send — deliveries, bounces, complaints, opens, clicks, and more — without paying for overpriced email services that are just glorified SES wrappers.

## About Hosting Sessy

Deploying Sessy on Railway uses the official Docker image (`ghcr.io/marckohlbrugge/sessy:main`). It's a Rails application that stores data in SQLite and uses Solid Queue for background job processing. Sessy needs a persistent volume to retain its SQLite database, job queues, and storage across redeploys. You'll need to set `SECRET_KEY_BASE` for secure session handling and `DISABLE_SSL=true` since Railway handles TLS termination. Once running, configure AWS SES to send event notifications to your Sessy instance's webhook endpoint to start tracking email activity.

## Common Use Cases

- Monitoring Amazon SES email deliveries, bounces, complaints, opens, and clicks through a clean web dashboard instead of digging through CloudWatch
- Replacing expensive email analytics services with a self-hosted, open-source alternative that sits on top of your existing SES setup
- Debugging email deliverability issues by tracking the full lifecycle of every message sent through AWS SES

## Dependencies for Sessy Hosting

- Docker image: `ghcr.io/marckohlbrugge/sessy:main`
- Persistent volume for SQLite database and storage
- An Amazon SES account with event notifications configured

### Deployment Dependencies

- [Sessy GitHub Repository](https://github.com/marckohlbrugge/sessy)
- [Sessy Docker Deployment Docs](https://github.com/marckohlbrugge/sessy/blob/main/docs/docker-deployment.md)
- [Amazon SES Documentation](https://docs.aws.amazon.com/ses/)

### Implementation Details

Environment variables for the Railway service:

| Variable | Description |
|----------|-------------|
| `SECRET_KEY_BASE` | Rails secret key (generate with `openssl rand -hex 64`) |
| `DISABLE_SSL` | Set to `true` — Railway handles TLS termination |

Mount a persistent volume at `/rails/storage` to preserve the SQLite database, Solid Queue data, and uploaded assets across redeploys.

The background jobs dashboard is available at `/jobs` to monitor queues, retry failed jobs, and view recurring tasks.

## Why Deploy Sessy on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Sessy on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

## Similar templates

- [Pyroscope profiling](https://railway.com/deploy/pyroscope-profiling) — Protected continuous profiling with durable Pyroscope storage.
- [SigOnly](https://railway.com/deploy/sigonly) — Deploy SigNoz with a working demo app & config in one click
- [Unwrapped Spotify Music Stats](https://railway.com/deploy/wide-bold) — Unwrapped Spotify Music Stats, Estatísticas de músicas disponíveis

Open this page in a browser: https://railway.com/deploy/sessy