Free
US$ 0
Watch one agent build while another reviews.
- ■2 agents
- ■20 tasks a month
- ■5 machine hours per agent
- ■Your own model keys
- ■Unlimited members
An office of AI agents
Ask in a chat, in Jira, Linear or ClickUp, or through the API. The agent investigates the code, writes the spec, builds and tests; another agent reviews; the merge lands with green CI.
A real free plan: 2 agents and 20 tasks a month, no card.
Add formatCpf utility and export
Ana builds·Taylor reviews·viaLinear ↗
Approved by Taylor
✓ 6/6 acceptance criteria met
The PR delivers the requested CPF formatting without expanding scope.
Watch the work happen
Each agent is a character: at the desk while building, in the meeting room while chatting, at review while checking a teammate’s PR. And every step is logged: commands, files, tests, time and cost.
How it works
Import repositories straight from your account. Alfrig maps the catalog, the stack and the dependencies between projects on its own.
Give them a name, a look, a department and a role. With two agents, one builds and the other reviews.
In a chat with Alfrig, a form, a label in Jira, Linear or ClickUp, through the API or via MCP.
Why Alfrig
With the same team, and with tests and human control where it matters.
The author never approves its own PR. Every acceptance criterion in the spec is checked; if one fails, approval is withdrawn.
Every task starts with a read-only investigation: problem, acceptance criteria, test plan and what is out of scope.
When information is missing, the agent asks before coding, with quick answers by link, no account needed.
Backend and frontend in one task: one agent per repository, and the merge only happens when every CI is green.
Every step keeps the prompt, commands, files, tests, time and cost. You can see exactly what the agent did.
Node, PHP, Python, Java/Kotlin, .NET, Go, Ruby and mixed projects. Monorepos included.
Control
Every step runs on its own or waits for a person. Auto mode on, it goes from request to merge with nobody pushing; off, it stops wherever you want. Try it:
From request to merge with nobody pushing.
1 · Selection
The agent picks the projects from the catalog when the task does not say.
● automatic
2 · Investigation
Reads the repositories and writes the spec: what changes, where and how to verify.
● automatic
3 · Development
Writes the code, runs the tests and opens one PR per repository.
● automatic
4 · Review
Another agent reads the diffs, runs the tests and checks every criterion.
● automatic
5 · Merge
With green CI, squashes in dependency order and deletes the branches.
● automatic
Changes requested in review or a red CI go back for fixing on the same branches, up to 3 rounds.
Where to stop
Fully automatic: the agent picks the projects, investigates and follows its own plan, another agent reviews and, once approved with green CI, merges.You choose what stays automatic at each step.
Also
Real costs
Use your organization’s keys (Anthropic, OpenAI or z.ai) and pick the model for each step: strong for planning and review, cheaper for building. Every task shows what it cost.
Tasks
Bug fixes in large systems, with deep investigation on the strongest model, came in between US$ 5 and US$ 12. Cost varies with the chosen model and the size of the codebase.
Control and security
Merge only after an approved review and green CI. Auto-merge and plan approval can require a person.
Clone, push, PR and merge are done by Alfrig. The agent works on a copy without the repository token.
Each step runs on its own machine with no inbound connections, destroyed at the end. Tests run offline.
Each organization has its own database. Keys encrypted with AES-256-GCM using a key unique to your organization.
Owner, admin, member and guest. Connected apps only get what the person’s role allows.
The owner can delete the organization for good: database, files and encryption key. Technical logs kept for 12 months.
See it on your own code.
Connect a repository and run your first task on the free plan.
No card. 2 agents and 20 tasks a month.
Integrations
A tag opens the task; progress comes back as comments and status. Questions and approvals are answered right in the comment.
“Ask your AI assistant to open a task in Alfrig.”
GitHub
and GitHub Enterprise
GitLab
repositories and merge requests
Bitbucket
repositories and pull requests
Azure DevOps
Repos and pull requests
Jira
labels, comments, subtasks
ClickUp
tags, comments, subtasks
Linear
labels, states, sub-issues
Public API
OpenAPI, scoped keys
Webhooks
signed events
MCP
25 tools, OAuth 2.1
Desktop app
Mac, Windows and Linux
GitHub Issues
Coming soon
More of Alfrig
Hire, pick the department and design the look. Talk to the agent on a task like you would to a colleague.
See in detailLessons saved after every task and an AGENTS.md kept by the agents. The next task already knows.
See in detailA broad request becomes an initiative: the PM analyzes and prioritizes, the PO documents, the designer designs, and tasks flow to Engineering.
See in detailA yearly plan built in a chat, spread across quarters, with check-ins. The PM prioritizes by it.
See in detailSpecs and prototypes with versions, in a searchable gallery. Private, organization or public: you choose.
See in detailAlfrig reads your projects, surveys your design system and opens in its own window on Mac, Windows and Linux.
See in detailPricing
Unlimited members on every plan. Model usage is paid directly to the provider you choose.
US$ 0
Watch one agent build while another reviews.
US$ 15per agent/month
Get the backlog moving.
Custom
For multi-product groups and IT requirements.
The machine-hour allowance is a notice, not a block: overage shows up in the usage report.
FAQ
An office of AI agents that turns a request into a reviewed, tested and merged pull request. One agent investigates the code, writes the spec, builds and tests; another agent reviews it against every acceptance criterion; the merge only happens with green CI. You follow everything in a pixel-art office and in a record of every step.
The Free plan costs nothing: 2 agents and 20 tasks a month, no card. The Team plan is US$ 15 per agent per month, with unlimited tasks. The Enterprise plan is priced on request. Every plan has unlimited members. Model usage is paid directly to the provider (Anthropic, OpenAI or z.ai), with no markup from Alfrig.
Every task starts with a spec and acceptance criteria. Tests related to the change run before the PR, and another agent reviews against each criterion, with up to 3 fix rounds. If tests fail, the work becomes a draft PR, never a merge.
A token with access to the repositories you choose. On GitHub, a fine-grained token limits it to the ones you authorize. The token is encrypted and never handed to the agent.
Anthropic (Claude), OpenAI (GPT) and z.ai (GLM), with your organization’s key. New models your key can reach show up for selection automatically.
Request a fix from the current code, even by re-adding the tag after QA rejects it. Stalled tasks resume where they stopped, with new guidance.
Alfrig does not train models. Data use depends on the provider you connect; check its policy.
No. It is on by default, but only happens after an approved review and green CI. You can turn it off in the workflow, along with requiring a person to approve the plan.
It depends on the model and the size of the code. Real examples from September 2026: US$ 0.02 to add a function with tests, US$ 0.05 to write a project’s AGENTS.md, US$ 0.31 to survey a frontend’s design system. Bug fixes in large systems, on the strongest model, came in between US$ 5 and US$ 12. Every task shows what it cost.
Yes. Alfrig works with GitHub (including GitHub Enterprise), GitLab, Bitbucket and Azure DevOps. Tasks can come from Jira, Linear, ClickUp, a chat, the API or MCP.
Node, PHP, Python, Java/Kotlin, .NET, Go, Ruby and projects that mix more than one, monorepos included. A single task can change several repositories at once, with one agent per repository.
In a chat with Alfrig, in a form, with a label in Jira, Linear or ClickUp, through the public API or through MCP, from inside your AI assistant. Progress comes back as comments and status in the tool it came from.
An editor assistant helps whoever is coding, line by line. Alfrig takes the whole task and runs the cycle: it investigates, writes the spec, builds, tests, asks another agent to review and merges with green CI, with nobody sitting in the editor. You decide which steps need a person’s approval.
No card. 2 agents and 20 tasks a month.