Open source email campaign platform. Compose HTML emails, manage contacts, send via Amazon SES, and track delivery — from the dashboard or programmatically via the REST API.

Cloud version — send-again.com — 1,000 free credits, no setup required.

• REST API — send emails, manage contacts, and query delivery status programmatically
• AI Compose — describe what you want, get HTML email generated for you
• HTML Preview — live preview as you write
• Campaigns — organize sends into campaigns with per-campaign analytics
• Event Tracking — opens, clicks, bounces, complaints via SNS webhooks
• Contact Management — CSV and API import, automatic unsubscribe/bounce handling
• Automatic DNS Setup — Namecheap, Cloudflare, and Route53 integration for SPF/DKIM
• High Deliverability — powered by Amazon SES with domain verification built in
• Billing — optional credit-based billing via Polar (pay-as-you-go packs)
• API Keys — scoped API keys (contacts.read, contacts.write, send.read, send.write)

• Node.js 20+
• A Supabase project
• An AWS account with SES configured (verified domain + configuration set with SNS)

git clone https://github.com/guillaumegay13/send-again.git
cd send-again
npm install

Create a .env.local file:

# Required
AWS_ACCESS_KEY_ID=your-access-key
AWS_SECRET_ACCESS_KEY=your-secret-key
AWS_REGION=eu-west-3
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_PUBLISHABLE_KEY=your-publishable-key
SUPABASE_SECRET_KEY=your-secret-key

# Recommended
APP_BASE_URL=https://your-domain.com
UNSUBSCRIBE_SECRET=replace-with-random-secret
INITIAL_OWNER_EMAIL=you@example.com

# Optional — AI compose
OPENAI_API_KEY=your-openai-api-key
OPENAI_MODEL=gpt-4.1-mini

# Optional — DNS automation
NAMECHEAP_API_USER=your-api-user
NAMECHEAP_USERNAME=your-username
NAMECHEAP_API_KEY=your-api-key
NAMECHEAP_CLIENT_IP=your-whitelisted-ipv4
CLOUDFLARE_API_TOKEN=your-cloudflare-token
CLOUDFLARE_ZONE_ID=optional-zone-id
ROUTE53_HOSTED_ZONE_ID=optional-hosted-zone-id

# Optional — Send job worker
SEND_JOB_PROCESSOR_TOKEN=optional-worker-token
SEND_JOB_BATCH_SIZE=50
SEND_JOB_CONCURRENCY=4
SEND_JOB_MAX_RECIPIENTS_PER_JOB=250

# Optional — Billing (Polar)
BILLING_ENFORCED=false
FREE_TIER_INITIAL_CREDITS=1000
POLAR_ACCESS_TOKEN=your-polar-token
POLAR_SERVER=sandbox
POLAR_CREDIT_PACKS_JSON=[{"id":"topup_10","name":"$10 Top-up","productId":"your-product-id","credits":10000,"amountCents":1000,"currency":"usd"}]
POLAR_WEBHOOK_SECRET=your-webhook-secret

See the full environment variable reference below.

The app uses Supabase Postgres. Run the schema in Supabase SQL Editor:

-- paste and run supabase/schema.sql

Then create your user in Supabase Authentication (Email provider):

1. Go to Authentication > Users
2. Create a user with your email and password
3. Sign in at your app URL

# Development
npm run dev

# Production
npm run build && npm start

• Developer docs UI: /docs
• OpenAPI spec: /api/openapi.json

• Supabase JWT — works on all endpoints
• API key (sk_...) — works on /api/contacts, /api/send, /api/send/status, /api/send/jobs

To receive delivery/open/click/bounce/complaint events:

1. Create an SNS topic in AWS
2. Configure your SES Configuration Set to publish events to that topic
3. Add an HTTPS subscription pointing to https://your-domain/api/webhooks/sns

• On Vercel, use Vercel Cron to call GET /api/tasks/process every minute
• For non-Vercel workers, call POST /api/tasks/process
• POST /api/send/process remains available when you explicitly want send-job-only processing
• GET/POST /api/campaigns/process remains available as a compatibility alias
• Set CRON_SECRET for Vercel Cron auth
• Set SEND_JOB_PROCESSOR_TOKEN and pass it via x-send-job-token or Authorization: Bearer ... for external workers
• Keep the inline fallback enabled unless you have a reliable external worker
• POST /api/send also accepts an optional sendAt ISO timestamp for first-class scheduled sends

MIT