We're Folding Tidra Back Into OpsLevel

We’re folding Tidra back into OpsLevel.

Tidra started as OpsLevel’s Maintenance Agent. Earlier this year we spun it out under its own brand, and now we’re bringing it back in. Same agent, same tech, just under the OpsLevel name from here on.

What this means if you use Tidra today

• Your Tidra account will move to a full OpsLevel account over the coming months, at no additional cost
• We’ll reach out to you directly when your move starts
• We’re no longer taking new signups on Tidra itself. The Maintenance Agent lives in OpsLevel now.

There’s nothing you need to do right now. Your initiatives keep running, your PRs keep tracking, and we’ll contact you directly before anything changes on your side.

Why

Building Tidra showed us that maintenance is one part of a much bigger problem.

As coding agents get better, the bottleneck moves to review, testing, CI, security and deploys. So we’re building for the whole agentic SDLC now. And agents working across your whole org need Context (your catalog: what services you have and who owns them) and Guardrails (your standards). That’s exactly what OpsLevel already provides, so the Maintenance Agent makes much more sense inside OpsLevel than as a separate brand.

Thank you

Thank you to every team that used Tidra and told us what was working and what wasn’t. A lot of what we’re building next came from you.

I wrote up the full story — where this came from and where we’re taking it — over on the OpsLevel site: Retiring Tidra and building for the agentic SDLC.