Autonomous software engineer
Issues in.
Verified pull requests out.
Encode takes issues from your team's Works withForgejo · self-hosted or hostedGitea · 1.19 or newerAvailable at launchGitHubGitLab · GitLab.com and self-managed, reads the code, plans the change, builds it and checks it, then opens a pull request with the evidence. Encode runs it all on its own infrastructure: nothing to install.
Available January 2027. Pre-orders open soon.
Add idempotency keys to POST /invoices
- issuepicked up from the issue queuedone at 09:14
- research23 files read, 4 call sites founddone at 09:16
- plan5 steps, 3 files, 6 new testsdone at 09:19
- buildbranch encode/412-idempotencydone at 09:41
- verifytypes, lint, tests, buildnow
- pull reqwaiting for verification–
- Nothing to installEncode runs your Workers on its own infrastructure. You connect a repository and add tasks.
- Every change is a pull requestA branch, a written plan and the check results, for your team to review.
- No usage capsOne flat monthly price per Worker. No tokens to count.
- Checked by a personWith Human Verification, an engineer reviews every finished task.
01How a task runs
One pipeline, the same six steps for every issue.
Encode is not a chat assistant. It works through a fixed sequence, records what it did at each step, and only moves on when the step's result holds up.
Issue
Picks up an issue from your Works withForgejo · self-hosted or hostedGitea · 1.19 or newerAvailable at launchGitHubGitLab · GitLab.com and self-managed, with its description, labels and discussion.
out: task in the queue
Research
Maps the repository and reads the code the issue touches before changing anything.
out: relevant code, conventions
Plan
Writes a step-by-step plan: files to change, tests to add, how success is checked.
out: written plan
Build
Makes the change on its own branch in a clean checkout, committing as it goes.
out: branch with commits
Verify
Runs your type check, linter, tests and build. Failures go back to Build.
out: verification log
Pull request
Opens a pull request that explains the change and how it was checked.
out: pull request, ready for review
Verified means your own checks passed: type check, linter, tests and build, and a browser check for web apps. With Human Verification, a human engineer also reviews the change before you see it.
02Workers
Capacity you add one Worker at a time.
A Worker is one slot that takes an issue through the whole pipeline. Add Workers and issues run side by side instead of one after another.
- Unit
- One Worker works on one issue at a time, from research to pull request.
- Output
- Around a 40-hour work week of output per Worker, on well-scoped issues. Task sizes vary.
- Scale
- Workers run in parallel. Four Workers take four issues at once.
- Control
- The queue, live progress and Encode's questions, in the Encode dashboard.
03Where it runs
Run by Encode. Nothing to install.
Encode's Workers run on Encode's own infrastructure, each task in its own checkout. You connect your Git environment once and follow everything from the dashboard.
- Your side
Works withForgejo · self-hosted or hostedGitea · 1.19 or newerAvailable at launchGitHubGitLab · GitLab.com and self-managed
Issues, branches and pull requests stay in your own repositories.
- Encode
Encode server
Keeps your git connections, queues tasks for your Workers and hosts your dashboard.
- Encode
Workers
Encode's own infrastructure, where your Workers build and test each change in its own checkout.
Nothing to install
Encode runs and maintains the Workers. You connect a repository; there is no agent to install or keep up to date.
A branch per task
Every task works on its own branch in its own checkout, so tasks never step on each other or on your work.
Nothing ships unchecked
Your type check, tests and build run before a pull request is opened. Failures go back to Build.
One dashboard
Queue, live progress and Encode's questions in one place.
04What to expect
A junior engineer, and we say so.
Encode does well on the work a capable junior engineer does well. Here is where it stands today, so you can decide which issues to give it.
Encode asked during Plan
A request repeats a key that was used before, but with a different body. Should it get the first response again, or be refused with 422? The issue does not say.
- Return the first response
- Picked: Refuse with 422
Product owner answered
Refuse it. A changed body under the same key is a client bug we want to see.
Best on well-scoped issues
Bug fixes, endpoints, screens, tests, migrations: issues with a clear outcome. Large redesigns work best split into several issues.
It asks when it is unsure
When an issue leaves a real decision open, Encode asks in the task's discussion and waits for your answer, rather than shipping its own interpretation.
A human checks the work
Every change on a plan with Human Verification is reviewed by one of our engineers before it reaches you. Nothing is merged without their approval.
05Pricing
Priced per Worker, per month or per year.
One flat price per Worker, monthly or yearly, with no usage caps and no token counting. Pre-orders open soon: leave your email and we will tell you the moment they do.
Encode opens to the public in January 2027. We will announce the exact date once the last pre-release improvements are done, and people on the notification list hear it first.
| Per Worker, per yearPrices excl. VAT. No usage caps, no token counting. | Autonomous Junior Software Engineer€36,000/ year excl. VAT€3,000 a month, billed yearlyNot at launchNotify me when Autonomous Junior Software Engineer becomes available | Autonomous Junior Software Engineer + Human Verification€42,000/ year excl. VAT€3,500 a month, billed yearlyAvailable January 2027Pre-orders open soon for Autonomous Junior Software Engineer + Human Verification: get notified |
|---|---|---|
| Around a 40-hour human work week of output | Included | Included |
| Works through your issues autonomously | Included | Included |
| Plans, builds, tests and verifies each change | Included | Included |
| Commits to your git repositories | Included | Included |
| No session or usage caps | Included | Included |
| Built-in validation pipeline | Included | Included |
| Every finished task checked by a human engineer | Not included | Included |
| Changes sent back with notes when they fall short | Not included | Included |
Both plans
- IncludedAround a 40-hour human work week of output
- IncludedWorks through your issues autonomously
- IncludedPlans, builds, tests and verifies each change
- IncludedCommits to your git repositories
- IncludedNo session or usage caps
- IncludedBuilt-in validation pipeline
Only with Human Verification
- IncludedEvery finished task checked by a human engineer
- IncludedChanges sent back with notes when they fall short
At launch every Worker includes human verification: one of our engineers reviews every change, and nothing is merged without their approval. The Autonomous Junior Software Engineer without it is not part of the launch; its "Notify me" link asks us to tell you when it becomes available.
Pre-orders open soon.
Leave your email and we will tell you the moment pre-orders open.
- Leave your work email and how many Workers you expect to need.
- We email you the moment pre-orders open, and again when Encode launches in January 2027.
- Pre-order then, or ignore it. The notification list is deleted three months after subscriptions open, and no entry is kept longer than 12 months.
Before you pre-order
Why January 2027 and not an exact date?
Encode is improving quickly in its final pre-release weeks. We would rather set the date once the remaining work is finished than move it later. People on the notification list hear the date first.
When can I pre-order?
Pre-orders open soon. Leave your email in the form above and we will tell you the moment they do. Leaving your email is not an order and commits you to nothing.
I already have a subscription. Does this change anything?
Your subscription, the dashboard and the billing portal keep working as before. Adding Workers opens again with subscriptions in January 2027; if you need one sooner, email us.
What exactly is a Worker?
One subscription: a slot that takes one issue at a time through the whole pipeline, from research to pull request. Add Workers to run more issues side by side.
Do we have to run our own hardware?
No. Encode runs the Workers on its own infrastructure. You connect your Git environment and add tasks in the dashboard; there is nothing to install.
Which Git environments does Encode work with?
Forgejo and Gitea today. GitHub and GitLab are in development and available at launch. Encode takes issues from your team's Git environment through a git connection set up in the dashboard. Ask us through the contact page if yours is not listed.