Roadmap to Kommento · Year One

A safer web, one trusted search at a time.

We’re turning the Kommento Safety Index into something investors can touch: a running API, a hardened browser, portable builds, Wi-Fi boxes, and family- friendly profiles. Scroll down and watch each phase of the next 12 months unfold in full screen.

Color Coded Search Results Blocks Millions of Known Bad Websites The Safest API Search on the Planet
Safety API · Visualized
One call returns the state of a domain.
For any URL we return the core fields our products use: trustScore, tint, riskTier, isBlocked(profile) and structured signals for developers.
trustScore: 0-100 tint: green / lightgreen / yellow / orange / red categories: porn, scam, malware, trackers signals: MANY_TRACKERS, MIXED_CONTENT, etc.
View How Our Safety Index API Works
Phase 1 · Month 1
Lock the scoring engine.
Every domain and URL is scored the same way, every time. Porn, scams, malware, and “never safe for kids” content move into hard red. Trusted core infrastructure lands in consistent greens.
Keyword heuristics (porn + scam) Known-bad host dictionaries Trusted core list (Google, banks, etc.)
Engine · v1 frozen
Phase 1 · Right now

Lock the engine so Kommento’s Safety Index behaves like a product.

The first job is to take our scoring logic from “it works in tests” to “we could license this tomorrow.” This phase is all about clarity: what we collect, how we score, and what we store.

  • Scoring bands locked: 80–100 = green/light green; 70–79 = yellow; 60–69 = orange; <60 = red.
  • Hard red categories: porn, clear scam patterns, known malware domains, and other “never OK for teen mode.”
  • Trusted list curated: core infrastructure (Google, Stripe, major universities, gov, large SaaS) pinned into green bands.
  • What we collect / store: URL, domain, trustScore, tint, category flags, security signals, and lastCheckedAt timestamp.
Phase 2 · Months 2–3

Turn the crawler into a live, hosted Safety API.

Here we move from “dev machine” to a real API on a real server: multiple workers crawling, backoff logic for 403s, and a simple JSON contract that our own products consume first.

  • Continuous crawl loop: master list of domains, batching, retries, backoff, and error logging for timeouts / SSL issues.
  • API surface: GET /safety?url=… returns trustScore, tint, categories, signals, and isBlocked(profile).
  • Host profiles: roll URL-level scores into a host-level profile to power “entire domain” decisions.
  • Metrics & health: crawl rate, error rate, score distribution, and coverage dashboards.
API Call · Example
GET /safety?url=https://example.com
The output is the same record our browser and Wi-Fi boxes use. That keeps the story simple for investors, partners, and developers.
{ "trustScore": 93, "tint": "green", "riskTier": "low", "categories": ["business","saas"], "signals": ["MANY_THIRD_PARTY_SCRIPTS"], "isBlocked": { "adult": false, "teen": false, "kid": true } }
Same contract across products Ready for external licensing later
Phase 3 · Browser
Kommento as a daily driver.
The same Safety Index powers Kommento Browser on Windows and as a portable USB build. This is the “show, don’t tell” demo for investors.
Kommento Browser v2 (Windows) Portable mode (no install) Rating bars, tiles, legend + colors
UX + safety glued together
Phase 3 · Months 3–4

Ship the browser + portable build powered by the Safety Index.

Once the API is live, we wire it into the products we control: the Kommento Browser and a portable USB build. This gives us something concrete for demos, pilots, and real-world feedback.

  • Kommento Browser v2: rating bars, AI detection, and trust tints all calling the same Safety API.
  • Portable Kommento: full browser + safety layer from a single folder or USB key; no install, no admin rights.
  • Mac groundwork: begin planning a Mac build so we have a credible path to multi-platform.
  • Theme & extension store beta: prepare for third-party UI integrations later in the year.
Phase 4 · Months 4–5

Kommento Wi-Fi boxes bring those scores into the living room.

The next step is hardware: small Wi-Fi boxes that sit next to a modem and apply Kommento’s decisions across every device in the home—phones, tablets, TVs, and consoles.

  • Wi-Fi box prototypes: basic hardware design with on-device filtering that calls our Safety API for new domains.
  • Simple admin panel: one local web app to see what’s being blocked, add exceptions, and toggle modes.
  • Home lab tests: try it in real multi-device households to validate performance and UX.
Kommento · At the edge
From URLs in a browser to packets on a router.
For investors, this is where the business model expands: boxes, subscriptions, and family-level plans that don’t depend on a single browser.
“Set it once” safety for all devices Household & small office plans Foundation for ISP / OEM deals
Phase 5 · Profiles
Adult, Teen, Kid: three modes that make sense.
Profiles turn raw scores into human-readable defaults. The same domain can be allowed for adults, warned for teens, and blocked for kids.
Adult: maximum control Teen: moderated but open Kid: strict blocking by default
Family profiles · v1
Phase 5 · Month 6

Layer profiles on top of scores so families can just pick a mode.

Instead of asking parents to tweak dozens of checkboxes, we ship three opinionated profiles built on top of our Safety Index and hard-red categories.

  • Profile logic in code: isBlocked("teen") and isBlocked("kid") use both category flags and hard rules.
  • UI for parents: one place to pick a profile, add exceptions, and see recent blocks.
  • Feeds into future teen/kid products: our own teen-focused browser themes, extensions, and Wi-Fi bundles.
Phase 6 · Months 7–9

Turn the Safety Index into a developer-ready platform.

Once our own products are stable, we let other builders plug in. This is where the API becomes more than a backend for Kommento—it becomes something other browsers, extensions, and apps can license.

  • Developer program: small, curated beta for extension authors, security apps, and parental control tools.
  • Docs & examples: copy-paste snippets for “Get trust score and tint for a URL” in a few languages.
  • Usage metrics: calls per day, score distribution by partner, and abuse monitoring.
Developer · Beta
“Can I just ask you if this URL is safe?”
That’s the core idea: every product on the planet that needs “safe / risky / blocked” decisions can ask Kommento instead of reinventing this wheel.
API keys & quotas Reference apps & CLI tools Early design partners
Phase 7 · Pilots
Small schools and teams, not giant contracts.
We start with realistic pilots: a school, a tutoring center, a small company. Enough to prove value without building a huge enterprise stack.
Org-level policy Simple reports Wi-Fi boxes in pilot sites
Phase 7 · Months 8–10

Prove it in the real world with schools and small organizations.

For investors, this phase is about evidence. Can Kommento box and browser actually make life easier for teachers, admins, and IT leads?

  • Org controls: organization-wide settings, multiple admins, and basic user management.
  • Reporting: high-level “what’s getting blocked and why” views, not a firehose of logs.
  • Structured feedback: capture what pilots loved, hated, or needed next to shape Year Two.
Phase 8 · Months 9–11

Plug into the wider security world: threat feeds and intelligence.

Kommento doesn’t live in a vacuum. We hook into trusted malware, phishing, and scam feeds so our Safety Index is always learning from the larger security ecosystem.

  • Automated threat ingestion: scheduled imports of known-bad domains, IPs, and URLs, mapped into our categories.
  • Audit trails: see when and why a host was moved into or out of a red category.
  • Incident-friendly signals: richer fields for security teams and future enterprise customers.
Threat Inputs
Our scores + external evidence.
For an investor, this is where Kommento evolves from a “nice UX layer” into real security infrastructure with multiple signal sources.
Known malware domains Phishing lists Internal heuristics
End of Year One
A clear story for partners.
By this point, we have code, products, pilots, and a narrative that can support serious conversations with ISPs, OEMs, and strategic investors.
Browser + Wi-Fi + API all running Proof from pilot sites Roadmap for Year Two
Phase 9 · Month 12 & beyond

Scale, partnerships, and the next chapter for Kommento.

The first year is about building a believable, working system. After that, the conversation shifts to scale: more crawlers, more markets, and more ways to ship “safer defaults” to normal people.

  • Investor-ready: clean metrics, live demo environments, and crisp materials explaining what we collect and how we decide.
  • Partnership-ready: a Safety API and Wi-Fi box story that make sense for ISPs, OEMs, and device makers.
  • Year Two planning: expansion beyond English-only, deeper enterprise features, and more advanced analytics.