OpsProbe

Latest progress

OpsProbe v0.3.57 is live in production.

This update records the public-preview state as of October 12, 2026: verified-site discovery, bounded assertions, clearer alert delivery, and public reliability summaries.

Updated October 12, 2026 Latest deployed release v0.3.57 Production verification

Quick answer

OpsProbe is in the public-preview MVP stabilization phase. Release v0.3.57 fixes report sharing reliability while keeping single-region and non-browser capability boundaries explicit.

Production status

Release0.3.57 deployed
API release0.3.57 deployed
Product modelWebsite reliability checks and monitoring
MonitoringHTTP, DNS, SSL, TCP, Ping, Keyword, Heartbeat
Release statePublic preview MVP

v0.3.57 release

v0.3.57 fixes public report sharing. Social links now point to the OpsProbe-hosted report URL, shared reports persist as redacted local JSON snapshots after creation, and PNG preview generation uses the completed probe payload instead of opening an empty editor.

v0.3.56 release

Verified websites now expose discoverable HTTP, DNS, TLS, TCP, domain, and security signals, with idempotent enablement for selected recommended monitors. HTTP assertions cover status, keyword presence or absence, JSON path/value, and response-header latency with bounded body reads. The Alerts view shows delivery attempts and retry timing without message contents or raw provider errors. Public status pages add 90-day uptime and average response time.

Migration 024 adds nullable/defaulted monitor assertion and check-evidence fields. Evidence excludes response bodies and sensitive headers. Multi-node probes, browser journeys, AI diagnosis, and MCP actions remain unavailable.

Earlier release history

The public shell and documentation layout improvements were recorded in the v0.3.49 static-site update.

v0.3.49 release

The public site now shares one navigation and footer shell, with consistent documentation breadcrumbs, article widths, legal-page spacing, and responsive mobile columns. Pricing comparison content is aligned with the plan cards.

v0.3.45 release

Pricing now keeps the preview-credit note with the Ops Credits introduction instead of leaving a detached full-width block. Privacy and account-deletion lists use consistent inherited typography and spacing. Public contact links use service@opsprobe.com; the deployed public pages no longer expose a personal contact address.

The API remains on v0.3.44; this is a static-site-only patch with no API or database changes.

v0.3.43 release

The homepage now states the product purpose, no-login diagnostic path, Google API scope, and AI NCII boundary directly in static HTML. It links to the Privacy Policy, Terms of Service, account deletion instructions, and public Docs. Clean `/privacy`, `/terms`, and `/delete-account` routes work without login or JavaScript.

v0.3.42 release

The API now supports both conventional /health and /ready paths alongside /healthz and /readyz. Releases now have a public smoke gate, documented local-build SSH deployment, timestamped backup and rollback steps, and a disposable PostgreSQL/Redis test dependency helper.

v0.3.41 release

Administrator traffic trends, visitors, probes, pages, events, leads, and geo enrichment now exclude empty user agents, private or invalid IPs, OpsProbe monitors, HTTP clients, crawlers, SEO tools, AI crawlers, and scanners. Migration 021 cleans historical analytics without deleting raw waitlist contact records. Isolated PostgreSQL/Redis coverage passed 115 tests with 80.85% workspace line coverage.

v0.3.40 release

Shared diagnostic reports now expose one-click publishing controls for X, LinkedIn, Reddit, Facebook, and Hacker News, plus copy-link and supported native device sharing. The desktop side rail becomes an in-flow panel on smaller screens. The public administrator entry is now /admin, while /admin.html and /admin/ remain compatibility redirects.

v0.3.39 release

The release raises Free capacity to ten websites and ninety days of plan-aware history, reports SMTP readiness, preserves bounded confirmation behavior, and adds the Basic P0 subscription foundation: billing summary, cancellation intent, resume, signed webhook validation, and duplicate-event suppression. Checkout and real payment collection remain disabled.

Verification now covers 114 deterministic and isolated integration tests with 80.89% workspace line coverage. A database-backed test-schema marker prevents cross-process migration replay during coverage.

Recent work

  • Restricted visitor analytics to known OpsProbe pages.
  • Excluded self-monitoring and common scanner noise from page-view analytics.
  • Aligned historical backfill with the same visitor boundary rules.
  • Removed noisy historical page-view records from production analytics.

These analytics changes shipped in v0.3.22 and remain part of the current production build.

v0.3.38 released

v0.3.38 publishes the Free V1 P0/P1 hardening work: five websites, fifty monitor slots, five-minute scheduling, seven standard monitor types, one TCP port per Free website, one public status page, controlled alert verification, plan-aware retention, cached RDAP profiles, and bounded scheduler and outbound request budgets.

The release gate passed 72 deterministic tests and 103 coverage tests with 80.06% workspace line coverage. A representative long-running 50-monitor soak remains operational evidence for future capacity increases; the current Free limits are bounded and server-enforced.

v0.3.37 released

v0.3.37 connects the standard pricing preview to the signed-in workspace. The plan usage response now reports history, TCP-port, team-member, and included-credit entitlements, while workspace initialization creates one auditable and idempotent welcome grant. Payments, monthly replenishment, expiry, and top-ups remain disabled.

The v0.3.38 release adds five websites and fifty monitor slots for Free, five-minute scheduling, seven standard monitor types, one TCP port per Free website, one public status page, controlled SMTP test delivery, plan-aware retention, cached RDAP domain profiles, and bounded scheduler and outbound request budgets. Isolated PostgreSQL/Redis integration coverage passed the release gate; a representative 50-monitor soak/load run remains operational evidence for future capacity increases.

v0.3.36 released

v0.3.36 fixes the Usage/Credits summary error caused by PostgreSQL returning numeric values for sum(bigint). The API now casts granted and consumed aggregates to bigint before decoding them as Rust i64, and integration coverage protects the balance and ledger summary path. No schema or payment behavior changed.

v0.3.35 released

v0.3.35 makes report sharing more useful: the HTTP path is shown as ordered DNS, TCP, TLS, HTTP response, and body-download phases with cumulative timing. Shared reports open with complete captured evidence, visitors can reset and run another check, and a sanitized PNG is available for X, LinkedIn, and native image sharing. The Rust API contract and 24-hour privacy boundary are unchanged.

v0.3.34 released

v0.3.34 makes HTTP evidence readable: the HTTP tab now identifies response type, body size, document metadata, TTFB, body download time, and five diagnostic phases from DNS through body download. Raw HTML is available only behind an explicit disclosure control. Real payments and credit purchases remain disabled.

Page trafficKnown OpsProbe pages only
Noise removalSelf-monitoring and scanners excluded
Internal viewDedicated administrator entry
SessionRedis-backed eight-hour cookie
BoundaryCustomer Console has no Analytics menu

Billing, multi-region diagnostics, browser checks, and AI analysis remain follow-up work. Plan enforcement and retention controls are live in the current preview.

Not live yet

  • Real credit purchases, top-ups, payment activation, and recurring renewals
  • Administrator MFA and role-based internal access
  • Multi-region probe selection
  • Multi-node false-positive reduction and regional diagnostics
  • Business-flow monitoring, deep security scanning, and AI analysis

What comes next

  1. Select and configure a payment provider, then add real checkout and webhook reconciliation.
  2. Continue Free alert outbox verification and long-running production soak evidence.
  3. Harden analytics retention and role-based access before expanding business-flow and security monitoring.