Create your first Product

A Product in Herald is what you’d call “one thing I want to understand” — Helpkit, SaasLab, your side project. It’s the billing unit, the isolation unit, and the Durable Object unit. One Product → one tenant → one agent → one briefing.

Sign up

Head to app.withherald.co/sign-up. Email + magic link. No credit card.

Name your Product

Pick the name you’d use in conversation. “How’s Helpkit this week?” is the test. You can rename later — the name is a label, not an identity.

Then pick a profile. This sets sensible defaults for retention, briefing cadence, and how the briefing weights your feedback sources:

• B2B SaaS — 90-day event retention, hourly + daily rollups, feedback weighted toward Intercom and sales calls.
• PLG consumer — 30-day retention with sampling over 1M events/day, daily rollups, feedback weighted toward reviews.
• Sales-led — 180-day retention, daily + weekly rollups, feedback weighted toward sales calls.

Every knob is editable in Settings later.

What gets provisioned

The moment you submit, Herald creates:

• A Durable Object dedicated to your Product — its own SQLite database, its own agent memory, its own alarm schedule.
• A Vectorize namespace for semantic search over your feedback.
• An R2 prefix for large blobs (transcripts, email attachments, briefing PDFs).
• Your ingest email: fwd+{product_id}@inbox.withherald.co. Forward anything useful here and Herald will route it.
• A public SDK key and a server key.

All of this runs in under a second. Your dashboard loads with the onboarding checklist already in place.

What to do next

Connect at least one source — Herald needs signal to write its first briefing.

• Install the JavaScript SDK to start sending product events.
• Connect Stripe — even alone, Stripe is enough to generate the revenue section.
• Forward an email — zero setup, no integration required.

Aim for three sources by Friday. Monday’s briefing lands the same week.