Product
What Encode does with an issue, step by step.
Encode is an autonomous software engineer: it takes an issue from your Git environment and brings back a pull request that has been checked. This page walks through what happens in between, and what you see while it works.
01The pipeline
Six steps, each with something to show for it.
Every issue takes the same route. Each step leaves a record in the dashboard, so you can check the reasoning, not just the result.
Issue
Encode takes issues from your team's Works withForgejo · self-hosted or hostedGitea · 1.19 or newerAvailable at launchGitHubGitLab · GitLab.com and self-managed through a git connection you set up in the dashboard. You can also add a task in the dashboard directly. Each one joins the queue for your Workers.
Research
It reads the issue, the files the change touches and the conventions around them, and looks at how similar changes were made before. When an issue leaves a real decision open, it asks instead of guessing.
Plan
Before any code is written, the change is broken into small steps a reviewer can follow: which files change, which tests are added, and how the result will be checked.
Build
Each task gets its own branch in its own checkout on the node, so tasks never step on each other. It commits as it works through the plan, so the history reads like the plan.
Verify
The whole change runs through your own type check, linter, tests and production build. Web apps are also loaded in a headless browser. Anything that fails goes back to Build with the error, not to you.
Pull request
The pull request links the issue and explains what changed and how it was checked. With Human Verification, a human engineer reviews the work before it is delivered to you.
02Verification
What “verified” means.
Two layers. The first runs on every change on both plans. The second is a person, on plans with Human Verification.
Automatic, on every change
- Type checkYour project's own type checker, over the whole change.
- LinterYour lint rules, as your team runs them.
- TestsYour test suite, plus the tests the plan added.
- Production buildThe build you ship, so a change that only works in development is caught.
- Browser checkFor web apps: the app is loaded in a headless browser and the changed screens are checked.
By a person, with Human Verification
- Review by an engineerA human engineer reviews every finished task before it is delivered to you.
- Sent back with notesA change that falls short goes back to Encode with notes, not to your team.
Human verification is included: one of our engineers reviews every change, and nothing is merged without their approval.
03Where it runs
Run by Encode, on its own infrastructure.
Workers run on Encode's own infrastructure, so there is nothing to install on your side. Your Git environment, Encode's server and the Workers connect as shown below.
- 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.
04The dashboard
Everything Encode does, in one place.
The Encode dashboard is where your team follows the work, answers Encode's questions and adds Workers.
- Overview
- Who is working on what right now, and what needs your attention, such as a question from Encode.
- Tasks
- Every task with its place in the pipeline, its plan, its checks and its discussion.
- Projects
- Your repositories, with their tasks and recent activity.
- Workers
- Each Worker and the task it is on. Add Workers as the backlog grows.
- Team
- The people in your organisation who follow the work, and their roles.
Available January 2027
Pre-orders open soon.
Leave your email and we will tell you the moment pre-orders open.