self-hosted
EnsureFix reads the ticket, writes the code, reviews the diff for bugs and security issues, and opens the pull request. You review and merge.
It runs on your own infrastructure — your servers, your repositories, your provider keys.
Session expires mid-checkout
0m 00s
src/auth/session.ts
+14 −6export async function refresh(s: Session) {- if (s.expiresAt < Date.now()) return null;+ const skew = 30_000; // clock drift guard+ if (s.expiresAt - skew < Date.now()) {+ return renew(s.refreshToken);+ }return s;}
Checks
16/16
Coverage
+2.4%
Risk
SAFE
The queue nobody gets to
Every team carries a queue of one-line bugs, flaky tests and dependency bumps. None of them is worth a sprint slot on its own. Together they are months of work that never happens.
None of these is hard. Every one of them is someone’s afternoon, and nobody has the afternoon.
why teams switch
Completion tools and chat windows help you write a line. EnsureFix owns the whole errand, from the ticket to the branch, with the audit trail to prove it.
The pipeline
Issues arrive from wherever your team files them. Eight agents plan the change, write it, review the diff, scan it for vulnerabilities and prove it with tests, then hand you a branch to merge.
0
Specialised agents
0
Checks before a PR opens
0
Stages per run
AES-256
Credential encryption
Under the hood
Six stages, each one an agent with a narrow job and a written trace. You decide where to approve and where to let it run.
Webhook from Jira, GitHub or Azure DevOps opens a run.
intake
The codebase is analysed, the files identified, a plan written.
planner
Production code, self-healing when the tests come back red.
coder · tester
Security scan, 16-point validation, a confidence score.
reviewer · security
Branch pushed, CI watched, failures fixed automatically.
publisher
What you accepted and what you sent back both change the weights.
learning engine
What EnsureFix does
Fix tickets, review pull requests, catch security issues. Adopt one and add the others when you're ready. They share the same pipeline and the same audit trail.
Point EnsureFix at a ticket. It works out what to change, writes the code, checks it for bugs, and opens a PR. You review the diff and merge.
Every pull request gets reviewed: inline comments on the diff, security issues flagged, style violations caught. A reviewer that never gets tired.
Catches hardcoded secrets, SQL injection, XSS, insecure Docker configs, vulnerable dependencies and licence issues, on every commit.
Beyond the core
The pipeline earns its keep on tickets and reviews. These are the things teams end up using every day once it's in.
Test generation
Codebase Q&A
DORA metrics
Browser reproduction
Learns from feedback
Reasoning traces
Review
Every diff, human-written or agent-written, gets the same treatment. Findings land as inline comments with a severity, the rule they tripped, and a patch you can apply in one click.
SQL built from request input
api/orders.ts:88
Unbounded file read into memory
lib/upload.ts:34
Naming and structure consistent
ui/Cart.tsx:12
when it gets it wrong
Confidence is scored before anything is applied, and the score decides what happens next. Two of the three outcomes end with a person, not a commit.
auto_apply
High confidence, low blast radius, every check green.
The branch is pushed and the pull request opens. You review it like any other.
needs_review
The change is larger than expected, or a check came back ambiguous.
Nothing is pushed. The diff, the confidence breakdown and the reasoning trace wait for a person.
block
A security finding, a forbidden path, or a pattern this repo has rejected before.
The run stops and says why. Overriding it takes an explicit acknowledgement.
Measurement
Reasoning traces show why each decision was made. DORA metrics show what it did to your delivery. Per-token costs show what it spent doing it.
Where the run time goes
Deployment frequency
Lead time for change
Change failure rate
Mean time to restore
Getting started
where it runs
EnsureFix installs as Docker containers inside your own network. There is no hosted tier to sign up for, and no copy of your code on our side.
Stays with you
Leaves, because you point it there
Try it first
30 days
A full-feature evaluation that starts by itself on install — no key, no sign-up, no card. When it ends the deployment goes read-only and your data is preserved.
What happens after 30 days →Common workflows
Pick whichever hurts most. The others are a setting away once the first one is earning its keep.
Point EnsureFix at your bug tickets. It reads the issue, traces the root cause, generates a fix, validates it against 16 safety checks, and opens a PR.
Average fix time: 4 minutes
When CI breaks, EnsureFix reads the failure logs, diagnoses the issue, generates a fix and pushes, often before anyone notices.
60 to 70% of CI failures auto-resolved
Two hundred low-priority tickets gathering dust? Run them in batches while the team stays on the architecture work.
50+ tickets processed per week
Encrypted credentials
No code leaves
Full audit trail
Self-hosted
the same queue, a week later
The backlog from the top of this page, run through the pipeline. Same five items, same repository, times taken from the runs themselves.
on your own infrastructure
Install the bundle on a server you own and evaluate the whole product for 30 days. No sign-up, no card, no call required first.