Product blog

Product blog

Product updates, field guides, and field notes—each with links to docs and the hub where relevant. High-level milestones also appear on the changelog.

  1. The Novus software ecosystem: NSS Background Remover and Novus Visualizers under one operating model

    Product highlight · Jun 9, 2026

    One software ecosystem, two tools: how Background Remover and Visualizers fit together

    A map of the Novus software ecosystem: NSS Background Remover and Novus Visualizers, the shared free-first and on-device principles, and the deliberate differences between them.

    • Two tools, one model
    • Two creator apps
    • Free-first, on-device, honest

    Novus Stream Solutions

    Read
  2. Scattered feedback inputs from support, reviews, analytics, and messages flowing into a cluster of themes, then sorted into a roadmap with now, next, and later lanes

    Field guide · Jun 9, 2026

    From scattered feedback to a roadmap, without a PM

    A practical method for turning scattered feedback into a roadmap when you have no PM: getting all the inputs into one place, clustering raw requests into underlying themes, weighing each theme by frequency and pain against effort and fit, and sorting the result into build now, watch, or decline — across multiple products without drowning.

    • Themes, not raw requests
    • Weigh pain × frequency × fit
    • Build, watch, or decline

    Novus Stream Solutions (hub)

    Read
  3. A pre-launch runbook with grouped checks — build and assets, metadata and previews, performance, monitoring, and rollback — leading to a ship gate

    Field guide · Jun 8, 2026

    A go-live runbook for a serverless browser app

    A practical, ordered go-live runbook for an app with no backend: verifying the build and assets, confirming metadata and share previews, checking performance and the offline path, making sure analytics and error reporting are live before traffic arrives, and knowing exactly how to roll back. Less a philosophy than a checklist that has earned its place.

    • No servers, subtler risks
    • Check before traffic, not after
    • Know your rollback cold

    Novus Stream Solutions (hub)

    Read
  4. Paid-tier-grade features delivered free and ad-supported, made sustainable by client-side architecture

    Field guide · Jun 7, 2026

    Free-first, ad-supported: delivering paid-tier features without a paywall

    Why the tools give away what competitors charge for, and how the free-first, ad-supported model is made sustainable by architecture rather than wishful thinking.

    • Paid-tier features, no paywall
    • Ads fit the model; subscriptions don't
    • Made sustainable by architecture

    Operating model

    Read
  5. A hub domain with product subdomains, predictable path naming, and dense internal linking between them

    Field guide · Jun 7, 2026

    The URL map: naming, routing, and interlinking a multi-product ecosystem

    The deliberate URL and linking architecture that makes a multi-product ecosystem navigable for users and legible to search engines.

    • Hub-and-spoke domain layout
    • Predictable naming logic
    • Deliberate internal linking

    Operating model

    Read
  6. A single product name covering several distinct apps that each needed dedicated time and focus

    Field guide · Jun 7, 2026

    Why we shelved Novus Stream Studio: a second-screen idea that was really several apps

    A kill-decision retrospective: how an appealing single product turned out to be a bundle of apps, and why that made it the wrong thing to keep building solo.

    • One name, several apps
    • Solo bandwidth is the real constraint
    • Killing it was the system working

    Operating model

    Read
  7. Generic utilities that function correctly but are interchangeable with many existing tools

    Field guide · Jun 7, 2026

    Why we retired Novus Stream Tools: generic utilities that didn't earn their place

    A kill-decision retrospective on building utilities that work fine but have no real reason to exist, and the test that should have caught it sooner.

    • Worked fine, solved nothing new
    • A tool needs a real reason to exist
    • Generic ≠ valuable

    Operating model

    Read
  8. A product whose constant real-time data refresh created an always-on cost incompatible with a near-free operating model

    Field guide · Jun 7, 2026

    Why we killed our sports-odds project: the real-time data bill we couldn't make cheap

    A kill-decision retrospective on a product that was structurally incompatible with our cost model — the data had to be fresh every minute, and fresh-every-minute is expensive.

    • Up-to-the-minute data is expensive
    • Constant reads/writes broke the cost model
    • Structural mismatch, not a bug

    Operating model

    Read
  9. A lean software overhead stack where client-side architecture keeps the marginal cost of each app near zero

    Field guide · Jun 6, 2026

    Keeping monthly overhead low while running a portfolio of apps

    The infrastructure cost discipline behind running a multi-app portfolio solo, and why the architecture is what keeps it cheap.

    • Lean software stack
    • Client-side architecture = near-zero marginal cost
    • New apps add little recurring spend

    Operating model

    Read
  10. Product ideas passing through a runs-almost-free filter, with heavy-cost ideas screened out

    Field guide · Jun 4, 2026

    Keep, kill, or shelve: a structural "no" as a product filter

    An operating note on using a structural constraint — must run almost for free — as an honest product filter, not a failure of execution.

    • Runs-almost-free as a hard filter
    • Shelved AI-agent + sports projects
    • A structural no is a complete reason

    Operating model

    Read