Projects
A project is one product: one waitlist, one changelog, one feedback inbox, one set of contacts. An account can hold several, so a side project and your main product do not share keys or data.
What belongs to a project, and what to the account
Section titled “What belongs to a project, and what to the account”| Per project | Per account |
|---|---|
| API keys, secret and publishable | Your sign-in |
| Waitlist, changelog, feedback, notifications, contacts | Plan and billing |
| Usage limits: signups, changelog entries, feedback per month | The weekly digest setting |
Name, public address (launch.nordva.dev/waitlist/<slug>), custom domains, allowed origins | |
| A connected Stripe account (Builder: one per project. Indie: one on the account) |
An API key belongs to exactly one project. Nothing in the REST API or the MCP server takes a project id: the key decides.
How many
Section titled “How many”| Plan | Projects |
|---|---|
| Free | 2 |
| Indie | 4 |
| Builder | 10 |
Limits apply to each project separately. On Free, each of your two projects gets its own 100 waitlist signups and 10 changelog entries.
After a downgrade you keep every project you have. You cannot add another until you are under the new plan’s number.
Create, switch, delete
Section titled “Create, switch, delete”All three happen in the dashboard. The project menu is at the top of the sidebar.
- Create. “New project” in that menu. The project’s first secret and publishable key are shown once, right after.
- Switch. Pick another project in the menu. Every page then shows that project.
- Delete. Settings → Danger zone, for the project you have open. It removes the project’s keys and all its data. An account keeps at least one project, so the only project cannot be deleted. Other projects, your plan and your billing are untouched.
There is no API-key endpoint and no MCP tool that creates or deletes a project. A key, or an AI agent holding one, can only ever reach its own project.
With the CLI
Section titled “With the CLI”npx nordva@latest init asks in the browser, not the terminal. When your account has more than one project, or room for another, the approval page has a “Which project is this folder for?” menu:
- If the folder’s name (from
package.json) matches one of your projects, that project is preselected. - Otherwise it offers a new project named after the folder.
- The keys written to your env file belong to the project you choose there.
Run it once in each product’s folder and each gets its own keys.
With MCP
Section titled “With MCP”The MCP server authenticates with a secret key, so each connection works on one project. To use two projects from one editor, add the server twice under different names, each with its own key. init does this per folder: the project-level MCP config it writes carries that folder’s key.