Built from fifteen years of client work
Hogsend is the lifecycle stack Doug Silkstone rebuilt on every client engagement, shipped once as a versioned framework.
One engineer, the same wall, every engagement
I'm Doug Silkstone — a software engineer with a previous life in growth engineering, analytics, and martech. Over 15+ years of freelance startup and product work, every engagement hit the same wall: the team had PostHog, had Resend, and had a folder of webhook handlers pretending to be a lifecycle email system. Dashboards everywhere — and then someone asks "can we send an email when someone drops off onboarding?" and everyone stares at each other.
I rebuilt that system enough times to know exactly what it should be: durable journeys, real segments, suppression that actually suppresses, all as code the team can review. So I built it once, properly, and versioned it. Hogsend is that codebase — shipped as a framework you install (@hogsend/engine), not a service you rent or a repo you fork.
Why it's shaped like this
Code-first
Journeys are TypeScript because lifecycle logic is product logic, and product logic gets reviewed, tested, and versioned.
PhilosophyStudio watches the run
If a dashboard could edit journeys, the repo would stop being the source of truth. So Studio shows you every send, run, and contact — and changes to the journeys themselves happen in your editor, through review.
StudioPostHog-first, not PostHog-only
Events come in from anywhere and engagement fans out to anywhere. PostHog is the default center of gravity, and every wire in and out is swappable.
How it worksOne engineer, building in the open. No growth team — which is funny, given the product.
Roadmap lives in GitHub issues and the changelog. Pre-1.0 and versioned properly: the public surface is semver-committed, and breaking changes come with migration notes.
Start by finding the leaks
I built Hogsend to go faster for my clients; the service is the same engagement, productised. One week, $2,000 — your events, your emails, and your funnel gone through end to end, and a 90-day roadmap you can act on with or without me. It comes off the build if you go ahead.
Bugs go to GitHub issues. I read everything.
No forms or calendars. Email what you're working on and you'll get a straight answer — including "you don't need me for this."
Your events are already flowing. Add the journeys that act on them.
One scaffold command gives you the engine, 10 journeys, and 13 templates — in your repo, under your review.
Free to self-host · One scaffold command · No per-contact billing
$ pnpm dlx create-hogsend@latest my-app