QA
Need to know how it's meant to work? Ask engr.
Ask how any feature is meant to behave, get test-ready documents, and report a bug in plain words. You hear back when the fix reaches your QA site.
engr.ai · engineer
Your next engineer costs $200 a month.
Ask your code anything. It ships on your say-so.
engr is an AI engineer your whole team can ask. QA, product managers and developers ask how any of your apps works, get its documents, report bugs and get changes made. A developer approves every change before it is built, and nothing ships until the right person signs it off.
Ask engr
Priya · QA
How is a refund over the limit meant to be approved?
engr
It goes to the finance manager first. If they don't answer within a day, it moves to their deputy. The customer sees “Awaiting approval” until then.
For your whole team.
Your engineers' time goes on answering questions, writing documents and making small fixes for everyone else. engr takes that on, for everyone who works on your apps.
Product managers
Need the user guide? Ask engr.
Ask what an app does today. Get user guides, release notes and briefs written from the current code, in your branding. Found a bug? Say so.
Developers
Hand off the fix. Review what comes back.
Ask about code you haven't read yet and get the files and lines. Hand off fixes and enhancements, then review and approve what engr builds.
Engineering leaders
Your engineers stop being the help desk.
Approve plans by risk level and approve releases. See what shipped and what is waiting on whom, across all your apps.
Ask it. Get the document. Get it fixed.
How does an approval reach the person who has to answer it?
engr · When a request is submitted, the app looks up who approves that amount for that team and emails them with Approve and Reject buttons. It also shows on their “Waiting on you” page.
approvals/route.ts:57 · notify/email.ts:112
Answers about your apps, from the code
Anyone on a project asks in plain language. engr reads that app's actual code and answers, usually in a minute or two. People who don't read code get business language with no file names. Developers also get the files and lines it came from.
User guide
Customer Portal
Your logoWritten from today's code
Documents, on request
Ask for a user guide, a solution brief, release notes, a code walkthrough deck, a demo script or the whole hand-over set. A current copy comes straight back; otherwise engr writes a fresh one from today's code, with your logo, colours and contact details.
Fix: refund total ignores the discountLEVEL 1
- ✓Assessed
- ✓Approved
- ✓Built
- ✓Reviewed
- ✓Merged
- 6On QAwaiting on QA
- 7Live
Bug fixes and changes, with your approvals
A developer asks for a change, or QA or a PM reports a bug and a developer takes it. engr plans it, builds it on its own branch, and moves it through review, QA and release, stopping for the right person at every step.
It ships on your say-so.
A developer takes every bug. Every change is approved for its risk level. Every release is signed off by a person. Approvals arrive by email with the buttons in them, and on a “Waiting on you” page.
- 1
Assess
What will change, how risky it is, how QA should test it, how to undo it. Nothing is touched yet.
- 2
Approve the plan
The plan goes to the right approvers for its risk level.
- 3
Build
engr builds it on its own branch and opens a merge or pull request.
- 4
Code review
The result goes to your reviewers.
- 5
Merge
Merged once the merge is approved.
- 6
QA
Put on your QA site for testing.
- 7
Release
Released to production once the release is approved, then checked: production is actually serving the change.
Every change has a risk level.
The highest level a change touches decides who approves it. An admin can limit a developer to Level 1 or Level 2.
Level 1
Screens, wording and logic.
Level 2
The database, backward compatibility and dependencies.
Level 3
Architecture, security and sign-in, and infrastructure.
Many apps. The right people.
One engr covers all your apps. Each app has its own repository, branches, QA and production sites, approvers and branding. People say which app they mean, and engr works it out from their words or asks.
QAAsks questions, gets documents, reports bugs.
PMAsks questions, gets documents, reports bugs.
DEVAll of that, and asks for changes. Can be limited to Level 1 or Level 2.
Each person sees only the requests, documents and approvals of the apps they are on.
Runs where your code is.
engr works with your code where it already lives, and deploys the way your apps already deploy: on their own when a branch changes, as on Vercel, or through your deployment pipeline.
GitLabGitHubBitbucket
Our cloud or your network
The engine that reads and changes your code runs on one server, which can sit behind your firewall. It can push its own branches and nothing else; merging waits for your approvals.
Your Claude account
engr runs on Claude. Use a Claude subscription, or an Anthropic API key for a whole team.
Every step is recorded: who asked, what was assessed, who approved each step and when, and what reached production.
$200a month
engr and its server. Your Claude account comes on top: a subscription or an API key.
- Answers about your apps, from the code
- User guides, release notes, briefs and walkthroughs on request
- Bug fixes and changes, approved by risk level
- All your apps, with QA, PM and developer access for each
- Approvals by email and on a “Waiting on you” page
- Questions on a schedule: “Every Monday, email me the release notes.”
- Its own server, in our cloud or inside your network
Billed monthly. Want to talk first? Talk to us.
What happens next.
- 1
Get engr
Pay by card. Tell us your company and what you'd ask engr first.
- 2
Check your email
A confirmation arrives straight away: your instructions are on the way.
- 3
We set up your engr
Your own server, your account and your workspace.
- 4
Your instructions arrive
Sign in, connect your code, add your team, ask your first question.
Talk to us.
Want to see engr on your own apps first, or run it inside your network? Tell us what you'd ask it, and we'll reply by email.