Starter
$39 /mo
Standard-equivalent capability with managed operations.
- 10K subscribers
- 25K emails / month
- 100K API budget
- 1 connected WordPress site
- Analytics, webhooks, doctor, editor, audit
Agent-first, human-friendly email ops as a fully managed operator app at app.sendykit.dev. SendyKit wraps around Sendy without modifying core, giving humans and agents a modern API, CLI, analytics, AI, health diagnostics, and managed email operations — without you running the stack yourself.
No free-forever drag. Every tier is a serious operating model with explicit limits, connected-site controls, and real room to grow.
Standard-equivalent capability with managed operations.
Pro-level capability for serious teams.
Meaningful volume with stronger economics.
Dedicated infrastructure and negotiated limits.
Operators live in SendyKit at app.sendykit.dev. Navigation, billing, analytics, editor, doctor, and settings feel like one product.
Managed SMTP pool, warm-up strategy, updates, and ongoing infrastructure care. You don’t need to babysit the engine room.
Remote WordPress installs pair in as controlled connected sites instead of random API clients. Site caps and budgets keep the model sustainable.
Starter maps to Self-Hosted Standard. Growth, Scale, and Enterprise map to Pro-level capability — not a stripped-down hosted toy.
Subscribers, emails, API budget, AI usage, and connected-site usage all surface in one operator dashboard.
Metered SMTP, machine-payment pricing, and connected-site controls protect margins while giving customers clear upgrade paths.
Each remote WP install is a paired, site-scoped edge of your SaaS tenant — never a loose API-key copy. That is why site count is a real SaaS resource.
| Plan | Connected WP Sites | API Budget / Month |
|---|---|---|
| Starter | 1 | 100,000 |
| Growth | 5 | 500,000 |
| Scale | 20 | 1,500,000 |
| Enterprise | Custom / unlimited | Custom / unlimited |
No. SaaS keeps product parity by tier. The big difference is who operates the stack, not whether you get the real SendyKit.
Because each remote WordPress site consumes pairing, support, heartbeat, auth, and API budget. Site limits keep pricing honest and margins healthy.
No. Customers buy SendyKit SaaS. Backend Sendy-compatible mechanics stay behind the SendyKit shell and are not your burden.
Yes. The product language and operator model stay familiar. The difference is whether you want us to run it or you want to own the stack directly.
If you want SendyKit-first operator UX, managed updates, and clear economics for teams, plugins, and agents, SaaS is the fastest path.