Questions, answered.
What it costs, what it touches, and what it runs on.
What is Fredrin?
Fredrin is an agentic development environment for vibe coding, a vibe coding ADE. It is the Multiplayer Software Factory: people decide, AI Workers build, and everything the team uses lives in one workspace the Workers can see.
Does Fredrin replace Claude Code, Codex, or my editor?
No. Claude Code, Codex and your shell run exactly as they are, live in every ticket, and your editor stays your editor. Fredrin ties them together with a board, isolated worktrees and pull requests, so you keep the tools you know and stop switching between them.
How do I sign up?
Signup is open, with no invite code and no waiting list. Download Fredrin for macOS, Windows or Linux, sign in with GitHub or an emailed link, and you're in.
How much does Fredrin cost?
Nothing for a solo dev or a team of up to 5: every new account lands on the Free plan at $0, with unlimited projects, workspaces and private repos. Pro is $20/mo flat for every app, remote agents and a bigger AI allowance. Team is $29/seat/mo for every member, from the 6th member. Enterprise is invoiced on custom terms and adds single sign-on, an audit log, custom roles and merge rules.
Do I need a separate AI subscription?
No. Fredrin runs Claude Code and Codex on the subscription you already pay for, so Workers use your existing plan instead of a second, metered bill.
Do I have to pay for private repos?
No. The Free plan includes unlimited private repos and projects, with no card on file. No plan charges per repo: Pro is a flat $20/mo per workspace for the extras, so there's no metered repo charge or surprise invoice line.
How do parallel agents avoid conflicting with each other?
Each ticket runs on its own branch inside its own git worktree, so agents work in isolation and never overwrite one another's changes.
Can a Worker mess up my repository?
No. Every ticket runs in its own branch and worktree, an isolated working copy, so a Worker never touches your main branch or another ticket's work. Changes come back as a pull request you glance at in the Review column and either ship or send back. Nothing reaches your base branch until you merge, and merging is what auto-completes the ticket.
What happens when a PR's build fails?
Each Worker runs its plan's acceptance checks as its final act and reports the real exit codes, which stamp CI status on the board's PR pill. If a check goes red, the ticket is flagged needs-work and the failing checks are written into the PR body. The PR still opens, so you can read the diff and the failure together. Send the ticket back with a chat message describing the fix. That resumes the Worker, which picks up your feedback and re-runs the checks until the build is green.
Which platforms does Fredrin run on?
Fredrin is a desktop app for macOS, Windows and Linux: macOS 13+ on both Apple Silicon and Intel, Windows 10+ (x64), and Linux on x64 as an AppImage (make it executable and run it, no package manager needed). The board itself runs against your own GitHub repositories, so your code and Project Context always stay in your repos.