Skip to content

Introduction

Nordva Launch is one REST API and one MCP server for the things a small product needs around its users, from before launch to after people pay.

PrimitiveWhat it does
ChangelogMarkdown release notes, scheduling, a hosted public page, email subscribers and an embeddable widget.
WaitlistSignups with referral codes, a hosted page and widgets, invites, CSV import and export, and where each signup came from.
FeedbackFree-text feedback, classified automatically and routed to email, Slack, Linear or GitHub.
NotificationsIn-app notifications: send to a user id, poll unread from the browser, mark read. Builder plan.
RevenueYour own Stripe account, connected read-only: MRR, new and churned subscriptions, revenue over time. Indie and Builder.
ContactsOne record per person across waitlist, subscribers, feedback and Stripe. Not a CRM.
AttributionWhich signup sources produce paying customers, with no tracking script. Indie and Builder.

Everything is behind the same API key, and every primitive is also available as tools in the MCP server, so Claude Code, Cursor or VS Code can publish a changelog entry, look up a customer or report your MRR from inside a session.

  • Two kinds of key. A secret key (nv_live_…) for your server, and a publishable key (nv_pub_live_…) that is safe in a browser and can only write to the public endpoints: waitlist signup, feedback, changelog subscribe, and reading notifications. See Authentication.
  • One response shape. Every response is { data, error, meta }. Errors carry a stable code and a remediation telling you what to do. See Error codes.
  • Safe retries. POST and PATCH accept an Idempotency-Key. See Idempotency.
  • No tracking script. Attribution and insights only count what passes through Launch’s own forms and API. There are no pageviews or sessions here.