We're reorganizing the developer space

We’re making some changes to how the developer and builder areas of the Community are organized, and before we flip the switch, we want to share what’s coming and why.

What’s changing

The current Developer Support and Apps categories are getting consolidated into a single space: Develop, Build & Integrate.

Here’s how the sub-categories map from current to new:

Staying the same:

  • APIs & Integrations

  • CMS Development

  • Developer Announcements

Moving and getting renamed:

  • HubSpot Native Apps → HubSpot-built Apps

  • Third-Party Apps → Marketplace Apps

Getting added:

  • App Development: building apps on the HubSpot platform

  • Developer Platform & Tooling: CLI, local dev, APIs, and developer infrastructure

  • MCP & Agents: Model Context Protocol, AI agents, and agentic integrations

  • UI Extensions: CRM cards, custom UI components, and in-app experiences

Not sure which sub-category fits your question? No problem – you can always post directly in Develop, Build & Integrate and use tags!

Why we’re doing this

The current Developer Support and Apps split was set up for different audiences, but in practice a lot of you are doing work that spans bothand it’s not always clear where a question belongs. The sub-category structure also hasn’t kept up with newer surfaces like MCP, UI Extensions, and developer tooling, so those conversations haven’t had a clear home.

The goal is a single, inclusive destination for developers, builders, technical partners, and HubSpot users; organized around what you’re trying to build and how you’re expanding HubSpot.

What stays the same

Your existing posts and threads aren’t going anywhere. This is a structural reorganization, not a content migration — everything will remain accessible.

We’d love your feedback

Does this structure align with how you work? Are there surfaces or use cases we’ve missed? Drop a reply below, we’re still finalizing and your input matters.

The new structure makes sense, especially as developer work increasingly overlaps across APIs, app development, tooling, and AI integrations.

I particularly like the addition of Developer Platform & Tooling, MCP & Agents, and UI Extensions. Having these areas separated should make it easier to find discussions without forcing developers to decide between the old Developer Support and Apps categories.

One thing that could be useful is a clear set of tags for common technologies or use cases, such as webhooks, OAuth, CRM APIs, serverless functions, CLI, and AI integrations. That could make discovery even easier as the developer space grows.

Overall, consolidating the developer experience into one destination seems like a positive change.

Thanks for the feedback @Frankhayes2, I love the idea of adding more tech-related tags. I’ll get your suggestions over to the community team to see if that’s something we can put on the list to update.