Questions, honestly answered.
Is Nordva Launch live? Do I need an invite?
It is live and open to everyone. There is no waitlist and no invite. Run npx nordva@latest init in your project, or sign up at app.nordva.dev: the free plan has no time limit and needs no card. Paid plans can be bought today, Indie at $19 a month and Builder at $49 a month, with about 20% off when paid yearly.
What happens to my product if Nordva Launch is down?
Your product keeps working: nothing in Launch sits between your users and your own app unless you put it there. What stops is Launch's part. A waitlist form shows an error and the visitor can try again, the changelog widget says it is unavailable, feedback cannot be sent, and in-app notifications do not update until it is back. Webhook deliveries are retried for up to about nine hours. There is no uptime SLA on any plan. It runs on Cloudflare Workers and D1, and you can export your waitlist as CSV on Indie and up, so your list is never locked in.
How does it compare with dedicated tools like Beamer, Canny, Knock or Novu?
Each of those goes deeper in its one area: Canny and Featurebase have public voting boards and roadmaps, Knock and Novu have multi-channel notification workflows with email, SMS and push, Beamer has segmentation. Launch has none of those. It has the part a solo developer needs from each, behind one key, one MCP server and one bill, and it connects them: which signup source produced paying customers, and what those customers asked for. If one of those areas is the core of your product, use the specialist for it. The alternatives pages say for each tool who is better served by staying.
Do in-app notifications use WebSockets or Server-Sent Events?
No. Your app polls GET /v1/notifications/inbox with a publishable key and the signed user id (user_hash), every 30 to 60 seconds as the answer suggests. There is no streaming endpoint. If you need instant delivery or email, SMS and push from one workflow, a notification service such as Knock or Novu is the better fit.
Can my AI coding agent write and publish my changelog?
Yes. With the MCP server connected, the draft_changelog_from_commits prompt has the agent read your git log since the last published entry, keep what users would notice, draft an entry in the tone of your earlier ones, and publish or schedule it only when you say so. Every operation a secret API key can perform has an MCP tool, so an agent can also add signups, triage feedback, create webhooks and record what a channel cost.
Why not use Beamer, Canny, and Knock separately?
You can. One tool per job (waitlist, changelog, feedback, notifications, revenue, attribution) comes to about $487 a month at their entry paid plans, across 6 accounts, 6 API keys and 6 bills, and none of them can tell you which signup became which customer. 4 of those 6 have their own MCP server, so an AI agent needs one connection per tool and none of them sees the others' data. Nordva Launch trades best-of-breed depth for one key, one MCP server and one bill, which is the right trade-off for founders and small teams before and after launch.
What happens when I hit plan limits?
You get an in-dashboard warning at 80%. At 100%, the API returns a PLAN_LIMIT_REACHED error (HTTP 403) with a remediation message that says what to do. No silent overages, no surprise bills.
Where is my data stored?
Cloudflare D1 (SQLite at the edge) and Workers KV, hosted in EU and US regions. No data is sent to third parties except Resend (for transactional email), Anthropic (for feedback triage classification on the Indie and Builder plans), and the destinations you configure yourself: feedback routing and webhooks.
Which AI coding tools does the MCP server support?
Anything that speaks the Model Context Protocol. Verified on Claude Code, Claude Desktop, and Cursor. Other compatible clients should work out of the box.
Can I self-host this?
Not in v1. The Workers-based stack is tightly coupled to Cloudflare D1 and KV. Self-hosting is on the roadmap but not committed.
What is the uptime SLA?
No formal SLA in v1. We will not pretend otherwise. Incidents are announced by email and in-product notice, and we commit to an SLA once we have the operational history to back one.
Who is Nordva Launch not for?
If you want heatmaps, session recordings or click paths, use PostHog or Hotjar next to Launch. If you want a public voting board and roadmap, Canny or Frill do that; Launch keeps feedback private. If you send email, SMS and push campaigns, use Knock, Novu or your email platform. If you bill through something other than Stripe, note that revenue and paying customers come from Stripe only. If you are well past early ARR and need cohorts and forecasts, ChartMogul or Baremetrics fit better.