Sessy is a self-hosted email analytics dashboard for Amazon SES, built by indie developer Marc Kohlbrugge. It connects to your AWS account, ingests delivery events through SNS topics, and shows per-message status, bounces, complaints, and campaign performance. Teams run it on their own VPS with Kamal or use hosted Sessy Cloud.[1][2]
Quick verdict
Sessy fits teams that send through Amazon SES and want per-message delivery visibility on their own server. Its concrete advantages are SNS event ingestion, message and campaign search, historical replay, and an MCP server for agents. It is not a sender, its license bars competing SaaS resale, and hosted pricing needs a direct check.[1][2][3]
Key features
SNS event ingestion for deliveries, bounces, and complaints Sessy connects to an AWS account through SNS topics and ingests delivery, bounce, and complaint events, turning the raw SES event stream into queryable records.[1]
Per-message search across delivery history Operators can search individual emails and inspect what happened to each message, which is the core debugging workflow for failed or missing transactional mail.[1][2]
Campaign search and performance views Beyond single messages, Sessy groups sending into campaigns with search and performance views, so bulk sends can be reviewed as a whole.[1][2]
Dashboard charts for deliveries, bounces, and complaints A real-time dashboard with charts tracks deliveries, bounces, complaints, and unsubscribes, giving a standing overview without digging through CloudWatch.[1][2]
Historical imports via EventBridge replay over S3 Teams with archived SES events can replay them over S3 through EventBridge, backfilling history instead of starting analytics from zero.[1]
CSV exports of delivery data Delivery records export to CSV, keeping exit options open for external analysis or auditing outside Sessy.[1]
Rails MCP server for agent-driven operations The October 2026 MCP server lets coding agents inspect SES delivery, diagnose bounces, and analyze campaigns from the terminal against live data.[1][2]
Team invitations, custom domains, and unsubscribes Recent releases added team invitations, custom domain names, unsubscribe tracking, and cross-account SES setup, rounding out multi-user operational use.[1]
Who will love it
SES senders who are blind in CloudWatch If transactional mail already flows through SES and delivery questions mean digging through raw events, Sessy adds the per-message visibility that setup is missing.[1][2]
Operators who debug bounces daily Per-message and campaign search plus replayable history fit the person who gets paged about missing mail and needs the answer in minutes.[1][2]
Self-hosters and agent-driven teams One-command Kamal deploys keep analytics on your own server, and the MCP server fits teams that already operate infrastructure through coding agents.[1][2]
Who should avoid it
SES is required; Sessy sends nothing itself Sessy is an analytics layer that pairs with Amazon SES and does not replace it. Teams without SES, or teams wanting one vendor for sending and tracking, need something else.[1][2]
Source-available license with a SaaS non-compete The O'Saasy license permits use, modification, and distribution but forbids offering the software as a competing hosted service, which rules out reselling Sessy as a service.[1]
Hosted pricing detail stays thin Sessy Cloud offers a trial with monthly and annual plans, but exact plan prices were not captured in the inspected pages, so cost planning needs a direct check of the pricing page.[1][2]
What the reports suggest
One maker build log on the WIP community platform (the author own year-in-review) recording the December 2025 launch, the SES-event MVP, and an early 50-star milestone. No Reddit threads or G2 reviews were inspected.
1 cited community source. The single community source is the maker own launch record, not an independent review; nothing about reliability at scale, support quality, or user consensus can be inferred.
Launch record and early traction The maker launched Sessy in a single December 2025 burst with a working MVP receiving SES events, announced it on X, and passed 50 GitHub stars early, reading the open-source angle as resonating. The motivation was concrete: after switching transactional email from Postmark to SES, he needed a Postmark-like UI to see what was going on.[1]
Sample limits This is the maker own build log, not an independent user report, and no Reddit or G2 sample was accessible. It says nothing about reliability at scale, support responsiveness, or how other operators experience Sessy.[1]
Alternatives and portability
Incumbent alternatives Sessy is positioned for teams that stay on SES and want visibility. Teams that would rather consolidate sending and analytics pick a hosted provider such as SendGrid; teams that outgrow SES analytics entirely move toward full deliverability platforms rather than sideways into another dashboard.[1][2]
Integration and portability surface The MCP server connects Sessy to agent workflows, Kamal self-hosting keeps data on your own server, and CSV exports keep delivery history portable if you leave.[1][2]
Questions worth asking
Does Sessy replace Amazon SES or SendGrid?
How much does Sessy cost per month?
Can I self-host Sessy on my own server?
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
One maker build log on the WIP community platform (the author own year-in-review) recording the December 2025 launch, the SES-event MVP, and an early 50-star milestone. No Reddit threads or G2 reviews were inspected. The single community source is the maker own launch record, not an independent review; nothing about reliability at scale, support quality, or user consensus can be inferred.
- Sessy - Email analytics for Amazon SES
official · Observed October 10, 2026
Official product site inspected October 2026. Establishes SES analytics positioning, self-hosted and Cloud editions, feature set, Rails implementation, and indie authorship.
- Sessy pricing
official · Observed October 10, 2026
Official pricing page inspected October 2026. Establishes hosted monthly and annual plan structure with a 14-day trial; exact prices not captured.
- marckohlbrugge/sessy repository
official · Observed October 10, 2026
Public repository inspected October 2026, including README feature list, SNS and replay setup, self-hosting docs, and active 2026 development.
- Sessy O'Saasy license
official · Observed October 10, 2026
Repository license file inspected October 2026. Establishes the source-available O'Saasy terms with a competing-SaaS restriction.
- Sessy contributor guide
official · Observed October 10, 2026
Repository contributor guide inspected October 2026. Establishes Rails stack, Kamal deployment, SQLite and PostgreSQL databases, and the production checklist.
- Sessy documentation
official · Observed October 10, 2026
Official docs hub inspected October 2026. Establishes release history through October 2026 and active maintenance.
- Your Amazon SES data, now in Claude
official · Observed October 10, 2026
Official October 2026 blog post inspected. Establishes the MCP server for agent-driven SES operations over live data.
- Marc Kohlbrugge WIP Wrapped 2025
community · Observed October 10, 2026
Maker year-in-review on the WIP community platform inspected October 2026. Documents Sessy December 2025 launch burst, MVP receiving SES events, X announcement, early 50-star milestone, and the motivation: switching transactional email from Postmark to SES and building a Postmark-like SES UI. Written by the maker; a launch record, not an independent review.