Self-Hosted Email Course vs ConvertKit

A self-hosted email course vs ConvertKit comparison is a category comparison, not a feature-score grudge match. ConvertKit (now Kit) is a creator marketing platform: lists, sequences, tagging, landing pages, broadcasts. A self-hosted curriculum engine such as Cadensend plans a learning series from your sources, writes cited issues, and delivers exactly once — currently only to your verified address. There is no hosted Cadensend signup. If you need a list tool this week, ConvertKit can be that tool. If you need grounded curriculum, Cadensend is the other job.

Key Takeaways:

• ConvertKit optimizes audience operations; Cadensend optimizes Plan, Ground, Write, Deliver for learning.
• Cadensend is MIT, clone-and-run, not a SaaS course host, not a CRM, not a bulk sender.
• The MVP will not mail your ConvertKit list; do not architect as if it will.
• You can author in Cadensend and, if you already have consent, paste locked HTML into Kit — that handoff is your ops, not a built-in integration.
• Exactly-once, timezone-correct, citation-true issues are not sequence pixels.
• Security of retrieved PDFs is an LLM problem ConvertKit does not attempt to solve.

Table of Contents:

• Two Products, Two Jobs
• Feature Matrix
• What ConvertKit Does Well
• What a Self-Hosted Curriculum Engine Does Well
• Honest Non-Goals
• Worked Example: Creator Teaching Postgres
• Worked Example: Internal Platform Course
• Cost, Ops, and Security
• Migration and Hybrid
• A 30-Minute Decision Procedure
• Frequently Asked Questions

Two Products, Two Jobs

ConvertKit is where consented subscribers live; a self-hosted email course engine is where a syllabus becomes issues. Collapsing them produces either uncited marketing drips labeled "course" or a curriculum tool people yell at because it will not tag buyers.

Cadensend's own positioning: narrow on purpose. Not a marketing suite, not a CRM, not an autonomous agent, not a bulk-email provider. Open source: GitHub. Product: Cadensend.

Kit's own docs describe sequences, visual automations, and subscriber management — see Kit sequences documentation. That is the right manual for broadcasts and funnels. It is the wrong manual for coverage validation against a PDF.

A newsletter vs email course split is the pedagogical version of this article. Kit is strong at newsletters. Cadensend is aimed at courses.

Feature Matrix

Score the job you have, not a generic "email platform" wishlist.

Kit is not "worse." It is not trying to be a grounded generation pipeline. Cadensend is not trying to replace Kit's creator platform.

What ConvertKit Does Well

Kit does audience state: who opted in, what they clicked, which sequence they are on, when they unsubscribed. If you sell a paid cohort and already run forms, stay there for mail that is legally a commercial send. Read CAN-SPAM and RFC 8058 for unsubscribe headers on list mail — Cadensend's MVP sending to yourself is not an excuse to skip those when you use Kit.

Sequences can drip seven emails. Those emails are whatever you typed or had a generic LLM draft in a doc. Kit will not:

• Validate that day 4 requires day 2
• Retrieve handbook §3
• Refuse to write when chunks are missing
• Render citations from chunk IDs

You can still teach in Kit if you do that work by hand. Many good courses do.

What a Self-Hosted Curriculum Engine Does Well

Cadensend turns one learning goal into a structured series: Plan, Ground, Write, Deliver. Create Series wizard: includes, excludes, outcome, audience, cadence, timezone, tone. Planning graph: coverage and ordering, revision pass. Plan Studio: reorder, edit objectives, lock issues.

Ground: structure-aware ingest, hashes, series-scoped retrieval, diversified sources. Write: retrieve, write, visual spec, critique, gate, capped revise; AST then deterministic HTML/text (structured output). Deliver: Postgres FOR UPDATE SKIP LOCKED (guide), delivery record before provider, keys on workspace + issue + recipient + version (idempotency). Metrics targets from the product: 0 duplicate deliveries tolerated; scheduler and approved-send lag budgets.

Use it to draft a daily email course, 7-day onboarding, or educator curriculum. PDF notes are a typical corpus.

This is a bounded agentic workflow, not AutoGPT-for-email. HinterBuild AI agent development and RAG systems are the surrounding practices. Data pipelines for the queue.

Honest Non-Goals

Do not evaluate Cadensend as a Kit clone, and do not evaluate Kit as a RAG product.

Cadensend will not, today:

• Host your subscribers
• Provide a marketing site or paid signup
• Send to a mailing list
• Offer creator billing
• Browse the web as a research agent

Kit will not, today (and should not be blamed for this):

• Enforce citation coverage
• Isolate tenants in a vector store
• Treat PDF text as untrusted tool-incapable data

Roadmap honesty: Cadensend Update 2 is literally labeled for newsletter creators (opt-in audiences, consent, suppression, unsubscribe, analytics). That is future. Writing this post as if Update 2 shipped would be a vibe. We will not.

Worked Example: Creator Teaching Postgres

Example 1. You have 4,000 Kit subscribers and a desire to "do a course."

Wrong: dump ChatGPT's 10-day Postgres into a Kit sequence. Hallucinations ship to paying humans. RAG garbage if you half-RAG without gates.

Better:

1. Self-host Cadensend. Attach PostgreSQL indexes docs plus your own notes.
2. Plan 10 issues. Lock. Review chunks. Receive them yourself.
3. If — and only if — your list consent covers educational sequences, copy locked HTML into Kit by hand or via your script. Cadensend has no hosted integration.
4. Keep Kit tags for "completed sequence." Cadensend is not the source of truth for who is a subscriber.

Retention vs video: drip vs video. Spacing: spaced repetition email.

Worked Example: Internal Platform Course

Example 2. No public list. A staff engineer wants a grounded on-call series. Kit is the wrong default (personal creator tool, extra SaaS, possible data residency issues).

Cadensend on internal infra, verified address = the author, then export to the company wiki. Ocherfort if you need a hardened self-hosted security layer around models and tools. Prompt injection on handbook PDFs. When to self-host LLMs if legal forbids vendor models.

Cite sources so SRE and legal can audit. Human approval before even your own inbox if the handbook is sensitive. Guardrails.

Cost, Ops, and Security

Kit: subscription plus their deliverability stack. Cadensend: free software, you pay GPU/API, SMTP, Postgres, and paging yourself. Cadensend FAQ: the engine is free; plug in your LLM and email provider.

Ops: you run backups, upgrades, SMTP auth, DKIM on your domain. Kit operates the ESP. If you cannot run Postgres, Cadensend is not "easier ConvertKit."

Security: Cadensend treats retrieval as data, allowlists tools, SSRF-limits ingest, encrypts secrets, TLS for the vector store, verifies webhooks, redacts logs. Kit's threat model is account takeover and list abuse, not OWASP LLM. Different attackers.

PII before you embed customer tickets into a series. Chunking and embeddings are your problem on self-host.

About HinterBuild. Contact if you want the curriculum engine operated as an internal service — still not a promise of hosted Cadensend SaaS.

Migration and Hybrid

Author in Cadensend; send commercially in Kit only when consent exists and you accept that citations may need to remain in the HTML you copied. There is no official sync. A future public API is Update 5 on Cadensend's roadmap, not a secret endpoint.

Hybrid anti-patterns:

• Generating in Kit with "please cite" in the prompt
• Pointing Cadensend at Kit's API as if it were a bulk sender
• Double-sending because both tools retried

Exactly-once is Cadensend's obsession. Kit retries are an ESP conversation. If you paste into Kit, Kit becomes the sender of record. Do not also schedule the same issue in Cadensend to a future list that does not exist.

A 30-Minute Decision Procedure

Walk the jobs in order: list operations, then syllabus quality, then send target. Most "which tool?" threads start with UI screenshots. Start with the job that is blocking you this week.

1. Do you need forms, tags, and broadcasts to people who opted in? If yes, you need Kit or another ESP. Cadensend does not do this in the MVP.
2. Do you need coverage checks, scoped retrieval, and citations the model cannot type? If yes, self-host Cadensend and attach sources. Kit will not grow a vector index for your PDFs.
3. Who receives mail this week? If the answer is "me, while I author," Cadensend's verified-address send is the right rehearsal. If the answer is "4,000 subscribers," Kit is the sender of record — after you paste locked HTML you already reviewed.
4. Are you allowed to run Postgres and an LLM bill? If not, do not pick self-host to "save on Kit." You will pay in ops.
5. Is the content a newsletter? Use Kit. See newsletter vs email course. Cadensend is the wrong abstraction for a perpetual weekly.

Example: a consultant selling a "5-day email course" lead magnet. Steps 1 and 3 force Kit. Step 2 still justifies Cadensend on a laptop to draft days 1–5 from a client-safe PDF, then a manual copy into a Kit sequence. There is no webhook. That is the honest hybrid.

Internal platform training with no public list skips step 1. Cadensend plus a wiki export is enough. 7-day onboarding and PDF notes describe that path. Ocherfort if the models stay on-prem.

Write the decision down. Teams reverse it two sprints later when someone asks "why are we paying Kit and running Postgres?" The answer is two jobs. Forgetting that is how you either dump uncited sequences into Kit or try to turn Cadensend into a CRM it refuses to be. If a stakeholder still wants "one platform," show them the feature matrix above and the MVP send limitation in writing. Ambiguous architecture reviews are how list-blast features get promised from a repo that does not have them.

If legal blocks self-hosting an LLM, you can still write issues by hand with honest citations and use Kit only as the ESP. Cadensend is an accelerator for grounded drafts, not a requirement for teaching. The comparison is lost when people score "has a pretty sequence UI" as equivalent to "will not invent a Postgres command." Those are different products, and the MVP send target (you) makes that difference operational, not rhetorical.

Frequently Asked Questions

Is Cadensend a self-hosted ConvertKit?

No. It is a self-hosted curriculum engine. ConvertKit is a hosted creator marketing platform. Overlap is "email goes out." Everything else diverges.

Can Cadensend send my course to my ConvertKit list?

Not in the MVP. No hosted signup, no list, no Kit integration. Send target: your verified address.

Should I cancel Kit if I install Cadensend?

Only if you did not need lists, forms, or broadcasts. Most creators should keep Kit for audience mail and use Cadensend to write courses.

Which is better for a "free 5-day course" lead magnet?

Kit, for the lead magnet mechanics. Cadensend, for making those five days actually teach from your sources. Using both by hand is the honest answer today.

Does self-hosted mean better deliverability?

No. Deliverability is domain reputation, authentication, and complaint rates. Kit has an ESP. You have whatever SMTP you configure. Self-hosting can be worse if you improvise.

What license is Cadensend?

MIT. You can read and run the source.

Will Cadensend grow list features?

The public roadmap includes opt-in audiences after consent and suppression are real. Until you see that ship, assume it has not.

How do I choose this week?

If your blocker is "no list tool," use Kit (or another ESP). If your blocker is "uncited AI lessons," use Cadensend locally. If both, do both without pretending they are one product.

Conclusion

• Self-hosted email course vs ConvertKit is curriculum vs audience operations.
• Cadensend: Plan, Ground, Write, Deliver; MIT; no hosted signup; verified-address MVP.
• Kit: lists, sequences, creator stack.
• Hybrid is copy-paste after lock, not a hidden integration.
• Do not market Cadensend as bulk email.

See Cadensend, the repo, and contact HinterBuild for internal curriculum infrastructure.

Resources:

• Kit: using sequences
• FTC CAN-SPAM guide
• RFC 8058 List-Unsubscribe
• PostgreSQL indexes documentation
• Cadensend GitHub