Highlights
Proxy Finder learned per-host. It doesn't just pick a generally-fast proxy anymore; it picks one that's already worked for the site you're hitting. Browser got a stability fix that catches a class of cold-start failures. And Dashboard's Metrics and Activity views can now scope by product.
What's New
Proxy Finder picks proxies that actually work for your target
This is the biggest change of the week, and it took several iterations to land.
Before: Proxy Finder selected from the global pool by general fitness. Two requests to the same target site picked from the same broad pool, even though most proxies in that pool wouldn't work on that specific site.
Now: for every target host you query, Proxy Finder tracks which proxies have actually delivered. New requests sample a couple from the proven set, fall back to a small probe of unknowns to keep learning, and avoid the ones that have already failed there. The proven set is per-host and persists across restarts.
If you scrape protected sites where only a small fraction of proxies work, you should feel this. Fewer dud picks, fewer retries, less wasted budget.
We rolled this out behind a flag, ran six iterations to fix sharp edges (one of them, gating the learning logic so it stays stable under low traffic, took two more passes), and flipped the production default this week.
Browser is reliable after idle periods
Two fixes, one outcome.
First, Browser had a stale-state bug at cold start. After enough idle time, the underlying display layer held a lock that prevented the next launch from succeeding. Your first request after a quiet period could fail or hang. We clear the lock before launch now.
Second, the public API path that routes to Browser was pointing at the wrong destination in some environments. Traffic was being silently misrouted. The routing config is correct now.
If you've seen flaky first-request behavior on Browser at low volume, that's it.
Filter Metrics and Activity by product
Dashboard's Metrics and Activity pages have a product chip filter now. Click Single, Browser, or Proxy Finder and the charts scope to just that product's traffic. Useful when you only want to see latency or errors from one part of your usage instead of the aggregated view.
A small site update
The /jobs page is live. We're hiring a Founding Engineer and an Engineer. Both pages spell out scope, what the first month looks like, and how to apply.
We also tightened mobile rendering on the homepage Dashboard preview, refreshed the per-page social-share images across nine public routes, updated robots.txt for the 2026 AI era (retrieval and social-share previewers allowed, training crawlers blocked), and refreshed the Terms of Service with a clearer acceptable-use clause and a Sofia jurisdiction note with EU consumer carve-out.
Under the Hood
A non-customer-facing rename earlier in the window: "anti-bot bypass" became "anti-bot resilience" across the site. Same product, same behavior; the old phrasing was tripping ad-platform policy filters.
We're not publishing numbers from the new selection logic yet. We want two clean weeks of production traffic before we make claims about success rates. Real numbers, when we have them.
We've spent the past month rebuilding the layer that decides which proxy to use for which target. And the hard part isn't the algorithm; it's measuring whether it actually helps under real workloads. That's what May looks like.