Deploy Hogsend - Lifecycle Email Automation
Code-first lifecycle email for scrappy product engineers, self-hosted.
Hatchet Lite
hatchet-lite
Just deployed
/app/config
Postgres-J_tJ
Just deployed
/var/lib/postgresql/data
hogsend-api
Just deployed
Redis
Just deployed
/data
Just deployed
/var/lib/postgresql/data
hogsend-worker
Just deployed
Deploy and Host Hogsend - Posthog Audience Stack on Railway
Hogsend is code-first lifecycle email automation for teams on PostHog + Resend. You define journeys as TypeScript — welcome series, trial nudges, churn recovery — triggered by your PostHog events and sent via Resend, with link/open tracking and one-click unsubscribe built in. This template self-hosts the whole stack on your own Railway project.
About Hosting Hogsend - Posthog Audience Stack
The template provisions six pre-wired services: an HTTP api (ingestion, auth, the data plane), a worker that runs your durable journeys and sends email, Postgres (TimescaleDB) for the event store and contacts, Redis for the PostHog property cache, and a self-hosted hatchet-lite workflow engine with its own Postgres. Database, Redis, the auth secret, and public URLs are wired automatically. You provide a RESEND_API_KEY, and — once hatchet-lite boots — a HATCHET_CLIENT_TOKEN minted from its dashboard. The worker inherits both from the api, so you set them once, then redeploy.
Common Use Cases
- Lifecycle email for a PostHog-instrumented product: welcome, activation, and onboarding sequences defined in code
- Trial-to-paid nudges and failed-payment / churn-recovery journeys
- Behavioral + transactional email via Resend, with open/click engagement fanned back out to PostHog, Segment, or Slack
Dependencies for Hogsend - Posthog Audience Stack Hosting
- A Resend account and API key for email delivery
- A PostHog project as the event source (the primary use case; optional)
Deployment Dependencies
- Hogsend docs: https://docs.hogsend.com
- Resend: https://resend.com
- PostHog: https://posthog.com
- Hatchet: https://hatchet.run
Implementation Details
After deploy, point a PostHog webhook at https://your-api/v1/webhooks/posthog and edit your journeys in TypeScript under src/journeys/. Mint the Hatchet token from the hatchet-lite dashboard (Settings, API Tokens), set it as HATCHET_CLIENT_TOKEN on the api, and redeploy.
Why Deploy Hogsend - Posthog Audience Stack 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 Hogsend - Posthog Audience Stack 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.
Template Content
hogsend-api
dougwithseismic/hogsendRESEND_API_KEY
HATCHET_CLIENT_TOKEN
hatchet-lite
ghcr.io/hatchet-dev/hatchet/hatchet-lite:latestRedis
redis:8.2.1hogsend-worker
dougwithseismic/hogsendPostgres-J_tJ
ghcr.io/railwayapp-templates/postgres-ssl:16