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 ecosystem: Supply retail, NSS Background Remover, and Novus Visualizers under one operating model

    Product highlight · Jun 9, 2026

    One ecosystem, three tools: how Novus Supply, Background Remover, and Visualizers fit together

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

    • Three tools, one model
    • Retail + two creator apps
    • Free-first, on-device, honest

    Novus Stream Solutions

    Read
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. The build, ship, measure, and keep-or-kill loop of an app testing lab

    Field guide · Jun 6, 2026

    What an "app testing lab" actually does: our build → ship → measure → keep-or-kill loop

    The operating model that decides what gets built, what survives, and what gets cut — and why cutting is the system working, not failing.

    • Build narrow, ship into real usage
    • Measure activation, not vanity
    • Keep, kill, or double down

    Operating model

    Read
  8. 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
  9. 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
  10. A steady publishing cadence feeding an auto-building sitemap from typed content files

    Field guide · May 29, 2026

    The cadence behind a site you can trust

    An operating note on why a steady publishing cadence matters, and the code-as-content architecture that makes it sustainable solo.

    • Publishing as a rhythm, not an event
    • Code-as-content, no CMS
    • Sitemap auto-builds from the data

    Operating model

    Read