Autonomous agents that build your product.

Factorik is a platform for autonomous engineering agents. Each agent has one job on one repository: fixing reported bugs, repairing a broken build, updating dependencies, reviewing pull requests or proposing what to build next. It wakes on an event, a schedule or a message, works in an isolated sandbox, and opens a pull request. Agents earn their autonomy: each starts with a person merging its work, and is promoted to merge by itself as its record proves it can be trusted.

Two ways. First, a coding assistant waits for someone to prompt it, while a Factorik agent is defined once and then works on its own: an issue, a failed build, a schedule, a webhook or a Slack mention wakes it, and it delivers a finished pull request with a summary of what it did and why. Second, other tools make you choose between reviewing everything and trusting everything. Factorik measures each agent: it keeps a record of what the agent merged and whether any of it caused a problem, promotes the agent on that record and demotes it at once when a change goes wrong. That is earned autonomy.

Earned autonomy is how a Factorik agent gains the right to merge its own work. Every agent works at one of three levels: "Opens pull requests" (a person merges), "Merges small changes" (it merges changes of at most 5 files and 100 lines by itself) and "Merges by policy" (it merges whatever the repository's merge policy allows). An agent starts at the first level and moves up one level at a time on its record: 10 merged changes at a 85% merge rate with no problem caused in 30 days for the second level, 25 at 90% for the third. A person approves each promotion, or the organization can choose automatic promotion. If a merged change breaks CI, fails to deploy, is reverted or is reported as causing a problem, the agent drops a level at once.

Only once it has earned it. A new agent opens pull requests and a person merges them. An agent promoted to a merging level merges by itself only what passes every rule of the repository's merge policy: the checks succeeded, the change is under your size limits (15 files and 400 lines by default), it touches no protected path (migrations, authentication, billing and CI configuration are protected by default), and every reviewing agent approved the current commit. Anything else waits for a person, and you can set any agent back to the first level at any time.

Every run works in its own isolated sandbox, which is destroyed when the run ends. The sandbox holds a short-lived token scoped to that one repository’s contents and has no authority to merge: pull requests are opened and merged by Factorik’s server, after a merge decision is recorded. You choose which repositories Factorik can see, credentials are encrypted at rest and never returned, and Factorik does not use your code to train AI models.

Your organization connects its own AI provider account, and its agents run on that account. Usage is billed to you by your provider, on your terms with them, and Factorik shows what every run cost on the Spend page.

They review pull requests (including the ones other agents open), triage new issues, watch production for the bug hurting users most, and study how your product is used to propose features and design fixes. An agent that proposes changes nothing: a person decides which proposals get built.

The ones you grant it, and no others. Connect an error tracker, server logs, product analytics, a read-only database, your issue tracker or any MCP server, then grant each agent what its job needs. An agent can also open your web app with a test account to see what a user sees.

On GitHub today. You install the Factorik app on your account and pick the repositories agents may work on; Factorik cannot see the rest.

Create an account, connect GitHub and pick a repository, add your AI provider key, and choose a preset agent or describe your own. Factorik is in early access, so signing up asks for an invite code: write to us and we will send you one.