One license. Every client repo.
Run the DevIntern worker on your own machines across every client you serve. Tickets in each client's tracker become pull requests in that client's repo, with that client's credentials. You pay for your developers, not your client list.
Team, for up to 10 of your developers
billed to your agency
On clients, repos, or trackers
no per-client fee
Supporter, for a freelancer
own and freelance client work
Money-back on subscriptions
Team and Business plans
Built for many clients at once
One worker. Each client kept on its own board, repo, and keys.
Every client on its own board
Each client's tracker is its own team in one workspace: Jira for one, Linear for another, GitHub Issues for a third. Polling cursors and dedupe stay separate per board, and comments and status changes go back to the board the ticket came from.
One worker · one team per client board.
Each client's credentials, layered per run
Put a client's GitHub token and tracker credentials in that client's repo or team env file. They are layered into that client's runs and review requests only, on top of a shared file that holds your agency's own settings.
Repo and team env layers · owner-only files.
Their AI contract or yours
The coding agent is chosen per repo, team, or schedule, so a client that mandates Claude Code, Codex, Cursor, or OpenCode gets that agent while the rest of your work runs on your default. Pipelines are per repo too.
4 agents · per-repo override · one config line.
Throughput on fixed-price work
Ready tickets become pull requests your engineers review instead of write from scratch. Vague tickets are flagged back to the client's tracker with questions before any code is written, so the agent never burns budget guessing.
Feasibility gate · optional self-review · review-comment follow-up.
How it runs
Set up once per client, then let the tickets flow.
-
1 · Set up
- Install the worker on a machine you control and add each client's repo with its own env file.
- Add a team per client board so tickets, cursors, and comments stay separate.
-
2 · Run
- Ready tickets in each client's tracker become pull requests in that client's repo.
- Your engineers review; with automation on, review comments come back as commits on the same branch.
-
3 · Report
- Per-ticket run logs show what shipped for which client: feasibility decision, PR link, review outcome.
- Use them for status updates or invoices. They stay on your disk.
Client separation, stated plainly
Credentials are scoped per client run. The filesystem is shared with your OS user, so here is exactly where the line sits.
- Keep only your agency's own settings in the shared workspace env file, because every run inherits it.
- Give each client a repo or team env file with that client's GitHub token and tracker credentials. Those values reach that client's runs and API requests only.
- The coding agent runs as your OS user and can read any file that user can. When a contract requires hard separation, run that client on its own worker under a separate OS user or devbox.
- Code, tickets, and diffs never touch our servers. Every credential is sent only to its own vendor's API.
Licensing questions agencies ask
- Who counts toward the developer limit?
- Anyone on your side, employee or contractor, who runs DevIntern, files or takes its tickets, or reviews its pull requests. Client staff don't count if they only file tickets for you or review and merge the work you deliver.
- Is there a per-client or per-repo fee?
- No. Team covers up to 10 of your developers and Business up to 30, across as many clients, repos, and trackers as you serve.
- I freelance on my own. Which license?
- The one-time $99 Supporter License covers your own repos and your freelance client work, as long as you take the tickets and review the pull requests yourself. Bring on a second person and you need Team.
- Can I use Supporter on my employer's repos?
- No. Your employer isn't a client, and neither is a company whose team you work in day to day, even as a contractor. That company needs its own Team or Business license.
- Can my clients use the worker directly?
- No. You run the worker and review its work before you hand it over. Clients get the results (code, pull requests, ticket comments), not access to the worker, its dashboard, or its credentials.
- What if the client wants to keep running it?
- Your license covers your use. A client that runs DevIntern itself, during or after the project, gets its own license, and interactive use is free for their whole team. The consultants playbook covers that handoff.
- Who owns the code it writes?
- We claim no rights in the output. Between you and us it belongs to you or your client, as your own contract with them provides.
The binding wording is in the terms of service.
Bring your next client's backlog.
Interactive use is free, and signing in starts a 14-day worker pilot with no card. When it earns its keep, Team covers ten of your developers for $99 a month across every client, with a 30-day money-back guarantee.
Self-hosted · each client's tracker and repo · no per-client fee · 30-day money-back.
Works with the tracker your team already uses
Also evaluating DevIntern for another audience?