First clicks: a URL map for the entire Novus ecosystem

If you only remember one domain, remember novusstreamsolutions.com. It links to every active product, explains the venture structure, and hosts this blog plus Documentation. From there, branch to the spoke you need instead of guessing subdomains.

tools.novusstreamsolutions.com is for calculators, planning, and diagnostics in the browser. studio.novusstreamsolutions.com is for OAuth-connected dashboards, alerts, chat, and in-browser media helpers. newsletter.novusstreamsolutions.com is for composing and sending issues, managing subscribers, and configuring hosted pages. discordbots.novusstreamsolutions.com is for installing automation that keeps Discord organized. novussupply.ca is for purchasing physical goods.

Use novusstreamsolutions.com/docs for implementation detail: OAuth scopes, widget embeds, and operational guidance. Use /product-blog for hub-authored product narratives like this page. Use /changelog for dated ecosystem milestones. Use /community/{your-publication-slug} for the public API-fed index of emails, blog posts, and community items from the newsletter stack.

Use /newsletter for the hub’s subscribe experience that should align with your publication settings. Use /contact when you need human routing; describe which product you mean so support can forward quickly.

Subdomains can add features; paths can move when information architecture improves. Prefer linking to novusstreamsolutions.com hub pages when you write docs internally—they tend to gain redirects and update more gracefully than deep links to transient marketing slugs.

When in doubt, start at the portfolio, pick the product, and click through to the live app. That two-step habit prevents sharing deprecated URLs when a spoke rebrands a path but keeps the same hostname—exactly the stability Novus aims for as the ecosystem grows.