This is where we keep an honest log of what's gone out the door. We don't track every little thing, just the stuff customers should know about. Newest first.
We added comparison pages for every major QA and observability tool, 300+ pairs in total, plus alternatives hubs for the tools people search for most. If you've been trying to figure out where ObserveOne fits next to Datadog, Sentry, or Playwright, those are now the right pages to land on.
A real /search page that points at the parts of the site people actually look for: compare pages, alternatives, the blog, the docs. We added SearchAction JSON-LD too, so Google can surface the search box directly.
Three plain pages that probably should have been there from day one. /about explains who we are. /security tells researchers how to report issues. /contact gives sales, support, security, and press their own routes.
When a test fails, we now try to tell you why before you click anything. The agent looks at the trace, the diff, and recent runs, then writes a short note at the top of the failure. It's not always right, but it's usually a head start.
We rebuilt the runner. Test suites that used to take ten minutes finish in three or four. Your mileage will vary by suite, but most people see at least a 2x drop.
No. We ship small fixes daily and most of them don't belong on a public changelog. This page is for the things that actually change how you use ObserveOne.
Not for the changelog itself yet. The blog has one at /blog/rss.xml and most release notes also get a post there.
Email [email protected] or open an issue at github.com/Observeone1. We read everything.
Subscribe to the blog feed at /blog/rss.xml or follow @observeone on X. We post there when something noteworthy goes out.
Want the steady drip? Read the blog or grab the RSS feed.