The library · The stack

Loops and Hogsend

Use Loops for account email and signups, or write bespoke lifecycle journeys in TypeScript with Hogsend.

5 files · 11 KB

Why I keep it

I use Loops for WithSeismic’s signups, so a new subscriber becomes a contact and sends the event that starts the workflow. The starter uses Loops for account email too. When I want more bespoke behaviour, Hogsend is my lifecycle engine for journeys and segments written in TypeScript.

I’ve included the Loops transactional sender, the signup pattern and a Hogsend welcome journey, so you can choose the route your product needs. The signup code keeps a local JSONL record as a safety net; account emails use their own templates without adding recipients to an audience.

Take the files

5 files · 11 KB

  • README.md4 KB
  • hogsend/activation-welcome.ts1 KB
  • loops/env.example248 B
  • loops/subscribe.ts3 KB
  • loops/transactional.ts2 KB

Keep building your setup: The stack

Back to the shelves →
  • 015 files · 151 KB

    The SaaS starter

    Start with accounts, organisations, email and analytics wired into a React app and Hono API.

  • 025 files · 6 KB

    Turborepo

    Run builds, tests and type checks across your apps in dependency order, with cached results.

  • 0316 files · 18 KB

    Hono

    Give your API typed routes, generated docs and a consistent error response before adding features.

  • 048 files · 8 KB

    Drizzle

    Keep your database schema typed and your SQL migrations checked in beside the code that needs them.

  • 052 files · 5 KB

    Better Auth with passkeys

    Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.

  • 069 files · 10 KB

    TanStack

    Keep React routes, session checks and cached server data working from the same types.