Skip to content
Product roadmap · Updated August 2026

Prove the workflow before expanding the autonomy.

Bloggent is moving from shipped public research loops and a private-beta Website foundation toward specialized agents. Each step must first prove usefulness, evidence quality, safety, and reliable operation.

Now · Available

Shipped capability and the private-beta foundation running today.

SearchLens

Public topic analysis with live organic evidence when available, commodity-risk analysis, content-gap framing, and one structured recommended direction.

NonCC

Public deep non-commodity research with ranking-page analysis, proof requirements, and a proprietary defensibility evaluation.

AI Visibility Checker

Public webpage snapshots across relevant prompts in ChatGPT Search and Google AI Mode, with citations, mentions, competitors, and evidence-linked recommendations.

Private-beta foundation

Invitation-only accounts, Workspace ownership, and multi-website organization for testing real Website-level workflows.

Evidence, safety, and reliability

Explicit evidence states, quotas and budget stops, security/data-handling controls, protected releases, and monitored production health.

Next · Validate

A bounded proof cycle, not a promise that the full agent system already exists.

Beta evidence loop

Measure activation, Website launch, return use, requested jobs, failed steps, and useful outcomes with a small real-user cohort.

One research & opportunity workflow

Validate a single Website-scoped flow that turns traceable evidence into a structured, reviewable recommendation.

Operational cleanup

Keep product messaging, repository governance, release checks, Railway topology, and staging inventory aligned with live reality.

Execution decision

Use cost, reliability, failure-recovery, and user evidence to decide whether the next workflow needs durable background execution.

After the next gate

Implementation begins only after the workflow proof and an explicit authorization.

Durable workflow foundation

Website-scoped jobs, explicit state, idempotency, retries, budgets, action history, pause/cancel, and recovery—only if the proof shows they are needed.

Research artifacts

Persistent, traceable inputs and outputs that can be reused by later strategy and content workflows.

Strategy, content, and review

Move from approved opportunity to structured direction, brief or draft, and evidence-aware human review in controlled steps.

Railway capacity

Add a worker or queue only when the approved design demonstrates that the modular web process is no longer sufficient.

Later · Expand carefully

Broader autonomy follows proven workflows, permissions, and operational controls.

CMS draft operations

Prepare and push drafts to WordPress first, with least-privilege credentials and human publishing; Ghost follows after proof.

Internal linking & refresh

Find bounded linking, overlap, freshness, and maintenance opportunities without blind site changes.

Outcome-driven optimization

Use trustworthy site state and outcomes to choose the next approved research, content, linking, or refresh action.

Fleet operations

Coordinate queues, limits, failures, and next actions across multiple websites while preserving site context.

Teams, billing, and advanced controls

Expand roles, plans, and portfolio controls when real usage demonstrates the need.

Release gates

“Next” becomes available only when the proof is real.

Passing a gate supports the next decision. It does not silently authorize another product phase or automatic publishing.

Useful

A named user problem, a measurable outcome, and beta evidence.

Traceable

Structured artifacts and visible evidence behind recommendations.

Safe

Tenant isolation, bounded provider spend, retention rules, and human control.

Operable

Green release checks, Railway health, observability, and a recovery plan.

Roadmap

Direction, dependencies, and proof gates.

Timing is directional. A roadmap item is not a production-availability claim or a guaranteed delivery date.

Changelog

The record of what actually shipped.

Released capabilities and material improvements belong in the changelog. Directional agent workflows stay here until proven and released.

Read the changelog

Bring one real Website and one job that matters.

The private beta is where we validate which research and opportunity workflow deserves to become the next reliable part of Bloggent.