Free trial · No credit card required
Run Tidra against your own repos
Connect GitHub or GitLab, plan a change, and see PRs against your actual repositories. Every change lands as a draft PR for your team to review and merge on their own schedule.
Start your trial
Connect your repos, describe the change, and go.
What to try first
Most teams pick a real but contained initiative for their first trial run. Three options that work well:
A dependency upgrade you've been putting off
A version bump that affects 10 to 50 services. Specific enough to be safe; widespread enough to feel the value. Examples: a runtime version bump, a deprecated library swap, a framework minor version upgrade.
A configuration standardization
A small change applied across many repos. Examples: standardizing CODEOWNERS files, updating monitoring configs, refreshing Dependabot settings, adding service metadata tags.
A targeted security or compliance fix
A patch applied to all affected services. Examples: a CVE remediation, a hardening change to a shared base image, an audit-related metadata update.
You can scope your first initiative as narrow or as broad as you want. Most teams ship their first one within a few days of signing up.
From signup to your first PR in a day
Connect GitHub or GitLab, sync your repos, and write what needs to change. Most teams ship their first initiative within a day of signing up.
You stay in control
Tidra never merges anything. Every change lands as a draft PR for your team to review, comment on, and merge using the same workflow they'd use for any other PR.
Your code stays yours
We don't keep your code beyond what's needed to generate the change, and we don't train our models on customer code. SOC 2 Type II audited.
Frequently asked questions
How long is the free trial?
Two weeks, with full access to run Tidra against your repos. No credit card required to start.
What can I do during the trial?
Run real initiatives against your real repos. Generate code, create PRs, track them to merge, send notifications. The product you use in the trial is the product you'd use after.
What state are the PRs in when Tidra creates them?
PRs are opened in either open or draft state. Your team reviews, approves, and merges them using their normal workflow. You decide what gets merged and when.
How long does setup take?
Most teams are running Tidra against their first repos within 10 minutes of connecting GitHub or GitLab. No new tooling to install, no changes to your existing CI configuration.
What types of maintenance can Tidra run?
Dependency upgrades, runtime version migrations, CI/CD migrations, security patches, configuration standardization, and custom maintenance you define. If it can be expressed as a repeatable code change, Tidra can execute it across your org.
Is my codebase stored or used for training?
No. Tidra clones repos to generate changes but does not retain your code. We do not train models on customer data.
What happens after the trial?
You can subscribe and upgrade directly in the app. If you'd prefer a conversation about pricing or want to discuss what you ran during the trial, we can set one up. No automatic billing, no surprise charges.
How is pricing structured?
Pricing scales with the number of repos and initiatives. Most mid-market teams (50 to 500 engineers, 100 to 1,000 repos) land in a predictable annual range we can quote in five minutes.
Ready to run Tidra on your repos?
Connect GitHub or GitLab and ship your first PR today.