Use hs project create for a New HubSpot Marketplace App

This page is for teams creating a new public or Marketplace app, especially after the legacy public app creation path is no longer available for their developer account. HubSpot's create-app documentation points new developer platform apps toward the CLI-based Projects workflow, with `hs project create` as the setup command to review.

This is not the page to use when you only need to maintain an existing legacy public app. It is also not enough for a private app migration decision. In those cases, classify the app first and follow the relevant migration or private app docs.

The output you want before a developer starts is a short creation brief: target developer account, app name, authentication type, OAuth redirect URLs, scopes, feature list, Marketplace intent, and who owns listing/support/privacy materials.

`hs project create` starts the project creation flow to review in the official docs. After setup, teams commonly review project commands for local development, upload, and opening the project in HubSpot.

Treat this flow as a source-controlled project setup, not a one-time UI action. Files such as `hsproject.json` and app configuration files become part of the review surface for CI, code review, and handoff.

Before upload, confirm the target account and install/test flow. For public or Marketplace apps, also check listing requirements early so technical build work does not outpace support, privacy, and review-readiness work.

A Projects CLI app can still fail a launch workflow if Marketplace materials are unfinished. Assign owners for support contact, privacy policy, testing instructions, screenshots or assets, and install-flow evidence.

Keep the product language precise with clients: this checklist helps prepare a reviewable workflow, but it does not guarantee Marketplace approval or certify compliance. Marketplace requirements must be checked against HubSpot's current listing documentation before submission.

If the app includes classic CRM cards, create a separate app-card modernization task. The CRM card deadline is not the same as the May/June legacy public app creation sunset.