Sendy alone
- API surface7 legacy endpoints
- CLINo
- WebhooksNo
- AnalyticsBasic campaign stats
- SMTP flexibilitySES-first baseline
- Health diagnosticsNo
- Audit trailNo
- Operator feelingIt works
SendyKit wraps around Sendy without modifying core, giving humans and agents a modern API, CLI, analytics, AI, health diagnostics, and managed email operations.
You bought Sendy because SES email is cheap and dependable. But Sendy’s surface is still 7 legacy endpoints, no CLI, no analytics API, no audit trail, and no serious operator layer.
SendyKit reads your Sendy database and adds its own layer around it. It never patches Sendy core. If SendyKit stops, Sendy keeps running.
Licensed install, current database, current campaigns, current domains.
API, CLI, analytics, doctor, audit, UI shell, SMTP overlay, AI, billing intelligence.
Admin UI, shell workflows, connected sites, agent calls, and managed operations.
Only `sendykit_*` tables. No Sendy core-file fork trap. Uninstall cleanly if you ever need to back out.
Stop SendyKit and Sendy continues as before. The wrapper adds capability without turning your base install into a hostage.
Uses the Sendy database you already have. Existing brands, lists, and campaigns stay where they are.
This is the same product story in two forms: polished operator UI for humans, composable APIs and shell tools for agents.
7 polished admin pages. Mobile-first. Dark mode. Real operational context, not just campaign CRUD.
240+ composable commands. JSON output. Shell completion. Read/write can be machine-driven; send stays behind verified-domain trust controls.
The operating model changes. The product power doesn’t. Self-hosted is for ownership. SaaS is for managed execution.
The super-exoskeleton for Sendy. Your server. Your data. Your rules. Launch ladder by future-major entitlement.
Managed operator app at app.sendykit.dev. Paid from day one. No subsidies. Connected-site economics built in.
Install beside your current Sendy, validate the license, run non-destructive migrations, and start operating immediately.
API, CLI, analytics, health diagnostics, SMTP control, AI, audit, editor, and a serious operator shell — all layered around Sendy without modifying core.
125 endpoints across brands, lists, subscribers, campaigns, analytics, doctor, audit, billing, and more.
240+ commands with shell completion, machine-readable output, and workflows built for operators and agents.
68 automated checks across setup, DNS, PHP, cron, database, SES quota, and service-health categories.
Open rates, click rates, best send times, geography, trends, and operator-ready interpretation instead of raw numbers only.
Any provider, per-brand control, encrypted credentials, and managed overflow paths when you want them.
AI authoring, visual editing, and redacted audit history live inside the same product surface, not bolted-on fragments.
Until customer testimonials exist, the site should prove seriousness with concrete engineering and operational facts.
Never. SendyKit wraps around Sendy, reads the existing database, and creates its own `sendykit_*` tables. Sendy core files remain untouched.
Sendy continues working exactly as before. Remove the binary and the SendyKit tables if you want a clean uninstall. The base Sendy install is still yours.
No. SaaS presents as SendyKit Cloud at app.sendykit.dev. Self-hosted requires an existing Sendy install. SaaS does not.
Yes. Self-hosted is a one-time paid product with launch tiers based on included future major upgrades. It is not a free side path.
Yes. Agents can work through the API, CLI, and machine-payment-backed premium actions. Sending still stays behind verified-domain trust controls.
Because SendyKit sits in a different slot: it gives Sendy operators a realistic upgrade path, offers a managed SaaS path too, and is explicitly designed for humans and agents instead of treating automation as an afterthought.
If you want ownership, buy the exoskeleton. If you want managed operations, rent the cockpit. Either way, the product power stays real.