Early access is open. Here's what happens next

We started this blog on New Year's Day with an idea and not much else. Ten months later, Testomatica has run against a real staging site, lives on its own server, and is ready for a few more teams to try it.

Early access opens today. Here's what that actually means.

What onboarding looks like

There isn't much to install, because Testomatica runs on its own machine as a black box. You don't add an SDK to your app or change your build.

1. Connect your staging site. We need a URL and whatever access it takes to reach it. Staging stays read-only: requests that could write data are blocked in the browser.
2. Connect your tracker. Today that's Jira. Findings land there with steps to reproduce, a trace and screenshots, so they show up where your team already works.
3. Wait for your next deploy. Testomatica detects it and runs. The first run is where the gate checks, the universal rules and the business rules all get their first look at your site, and agents explore what changed.

Setup is guided. We'll walk through it with every early team. Partly because the rough edges are still real, and partly because we learn more from watching someone connect their site than from any amount of guessing.

Who it's for

We built this for teams that ship with AI. If coding agents write a good part of your code, you've probably felt the gap between how fast changes arrive and how fast anyone can check them.

It's also for startups that don't have a QA team and aren't going to hire one this quarter, and for solo builders who are the developer, the reviewer and the tester all at once. If your current test plan is "click around before lunch," we'd like to help.

What's still rough

We'd rather say this now than have you discover it.

Personas only see public pages for now. Signed-in flows like a buyer's account or a seller's panel need data masking in place before anything goes to a model, and that isn't done yet. Browser coverage is narrower than we want. And as our first dry run showed, agents still waste some steps fighting the browser instead of testing.

What we're building through winter

• Signed-in personas, once data masking is in place.
• More browsers, so device and rendering differences get the same attention as function.
• Pull request comments that show what a change will affect and which tests matter, before it merges.
• A release gate on production deploys, where your pipeline asks for go, stop or a human decision, and never gets a silent pass when the system can't answer.

Early teams will shape the order we do these in. That's most of the reason early access exists.

If this sounds like your team, the early access form is at the bottom of our homepage. We read every one.