I am the co-founder of a SaaS startup,
Our application is a Node.js web app served on Heroku and eventually AWS in the future. The problem I have is that I can’t really use the blogging platform of HubSpot because it doesn’t support simple integration.
What would be really nice would be to have some sort of npm package I can install, configure it, and setup the routing to say blog.mydomain.com and have the HubSpot platform serve my blog there.
The problem for people like me is that we have 2 sides of our businesses. We have the “public facing website” and we have the “web app” portion. Most of the marketing tools out there are build to integrate into public websites but for someone with a tech stack like mine where I have a server where really 90% of the code is the web app and then I have few routes setup for the public site, there are no tools that smoothly integrate.
I also can’t say hookup a subdomain to a separate hosting and serve my blog through there because my web app uses dynamic subdomains.
Hi,
Did you go any solution?
My suggestion would be if you have a separate APP which can communicate between your app and hubspot.
You can directly integrate the Hubspot API with your app.
Coming to this in 2026 and a lot has changed since you originally posted. HubSpot now has a proper CMS API that lets you fetch blog posts, authors, and tags programmatically from any backend (Accounts Dashboard | HubSpot ).
So for your Node.js app on Heroku or AWS, you can just call those endpoints from your server, render the content in your own templates, and serve it on whatever route you want. No need for a separate subdomain or hosting setup at all, which solves the dynamic subdomains conflict you were running into. You basically use HubSpot as a headless CMS where you manage content in HubSpot’s editor but serve it through your own app.
The pattern most SaaS teams use now is to cache the API responses in their own database so they’re not hitting HubSpot on every page load, and then use a webhook or polling to refresh when content changes. That keeps your blog fast and avoids any rate limit issues. Also since you mentioned eventually moving to AWS, if you’re currently using Heroku Connect for any Salesforce to Postgres sync stuff, that’s going to break the moment you leave Heroku. We’ve helped a lot of teams migrate off Heroku Connect with Stacksync as a proper alternative that gives you real time two way sync without being locked into Heroku’s ecosystem. Note This response was written based on my own experience and lightly reformatted with AI for clarity.
Hope this helps.