Tidra is now self-serve

Ship code changes across every repo. Free trial, no sales call required.

Tidra is now available for self-serve signup.

Connect your GitHub or GitLab repos, describe a change you want to make across them, and Tidra plans, generates, and tracks the PRs as a single coordinated initiative.

Since launch, the only way to try Tidra was to talk to us first. The product was early, and every user was a chance to learn what platform teams actually needed. We’ve spent the past few months working hands-on with teams at Keller Williams, TrueLayer, ecobee, and others — intentional about who we partnered with so we were building the right thing.

We’ve learned a lot about what makes these initiatives succeed. Today we’re opening the doors.

Our two-week free trial lets you run a few real initiatives. No sales demo, no credit card.

Who this is for

Platform engineering, DevOps, DevEx, SRE, and security teams. You’re making sure 200 services run on the same Go version, that every repo passes the new CI check, and that the latest CVE is patched everywhere by Friday.

Even when the change is small (like a one-line config update), coordinating it across hundreds of services takes weeks. The code isn’t the hard part. Getting it across 30 teams is.

Every repo gets its own plan

Before generating any code, Tidra runs a planning step on each repo: it clones the repo and analyzes its contents to figure out the right approach for that specific codebase. Package manager, framework, build configs, conventions in adjacent code. A Go service and a Python service in the same initiative get different implementations. A repo on CircleCI gets the right CircleCI config, not the GitHub Actions one. A repo that’s already migrated off io/ioutil doesn’t get migrated again.

Because the plan is per-repo, a single initiative can target a couple hundred heterogeneous repos and produce diffs that mostly look right on first generation. The ones that don’t can be regenerated individually with refined instructions, without starting the initiative over.

Works alongside Copilot, Cursor, and your existing tooling

Most Tidra customers use both. Copilot and Cursor handle deep work inside one repo, where one developer is iterating in their editor. Tidra handles the layer those tools weren’t built for: a change that needs to ship across every repo, owned by dozens of teams, tracked to merge.

It’s also a different layer than Renovate or Dependabot. Those tools open PRs when a new version is available. Tidra handles the code changes those PRs leave to your engineers: the breaking-change adaptations, framework migrations, and config standardizations that don’t fit a version bump.

You stay in control

Tidra drafts the plan, and you approve it before any code runs. Every diff is visible before a PR exists, and a PR only opens when you click create. Owning teams merge through the same GitHub or GitLab workflow they’d use for any other contribution. Nothing runs behind anyone’s back.

Code handling and compliance

Your codebase is among the most sensitive IP your company owns, and we’ve designed Tidra accordingly.

Repos are cloned ephemerally to generate changes, then discarded. We don’t train on your code, and your data is never used to improve our models. We’re SOC 2 Type II certified, and our audit report is available on request.

How a trial works

1. Connect your repos. GitHub or GitLab.
2. Describe the change. Tidra drafts a plan. You iterate on it until it’s right.
3. Pick the repos in scope. Filter by tag, language, framework, ownership, or recent activity.
4. Generate and review. Every diff is visible before any PR exists. Regenerate any repo with refined instructions.
5. Open PRs in bulk. Owning teams review and merge through their normal GitHub or GitLab flow.
6. Track to merge. One dashboard for CI status, review comments, blockers, and what’s still open.

Repeat as needed, all from one dashboard.

Pricing

Tidra is usage-based. Each plan includes a monthly bundle of credits that the agent draws on as it analyzes repos, generates diffs, and tracks PRs across an initiative. More repos and more complex changes use more credits. There’s no per-seat fee and no cap on the number of repos you can connect.

The two-week free trial includes a generous credit balance, typically enough to run a few real initiatives depending on their size and complexity. Paid plans bill monthly through Stripe, and your credit balance refreshes each month.

Get started

This is the release we’ve been building toward, and what we’ve seen with those early customers has convinced us it’s ready for a larger audience.

If your team is sitting on backlogs that never shrink, migrations that keep slipping, or CVEs that need to land everywhere by Friday, this is what Tidra was built for. It takes the coordination work off your team without taking their judgment out of the loop.

Connect your repos and run an initiative. The first one tends to reframe what your team thinks maintenance work should cost.