AOSplane for dev agencies

One project, one client

A project holds the repositories, the agents, and the budget for that client. The organization limit is the agency’s ceiling. The project limit is the client’s. The agent limit is that harness’s. The tightest of the three is a hard cap on the task. A task that would cross it does not start. The client next door is a different project, so its remainder is not this task’s to spend.

The plan’s project count is the roster. Free is 2 projects. Starter, at $39 a month, is 5. Team, at $149, is 25. Enterprise is a custom limit. History follows the plan: 7 days, 30, 90, or 365. Those numbers are the published plans, not a measure of how many tickets an agency closes.

The client’s tickets, your gate

Start from the client’s Linear issues or Jira Cloud issues. The pull request comes back on the GitHub repository linked to that project. Claude Code and Codex both go through scope, review, and QA. The team that opens the draft sees the spec, the review notes, QA’s results, and the cost of the task. They merge it, or the client’s reviewer does, on GitHub. Agents cannot push.

Opening a pull request from a ticket is something Linear’s agent, Copilot, and Rovo Dev also do. The agency reason to add AOSplane is the gate and the cap, not a new way to file a pull request. What the gate checks.

Whose model account

Connect the account the work should bill: the agency’s, or one you hold for that client. Claude Code uses an Anthropic account. Codex uses an OpenAI account. Bedrock, Claude Platform on AWS, Azure OpenAI, and other compatible providers are the other documented options. The provider’s invoice is the provider’s. AOSplane’s bill is platform usage, by the second, against the plan’s monthly credit. This page does not describe a client invoice AOSplane generates. You reconcile the provider’s bill yourself.

On Starter and up, the knowledge base can hold that client’s conventions. The product manager can read it while it writes a spec. It cannot write code.

What the console is not

The console is the agency’s. The client sees the pull request on GitHub, with the proof the gate attached. There is no separate client login described on this site. Slack, where it has rolled out, can pin a channel to a project, an agent, and rules for what members may do. A project API key lets that client’s CI start and follow a session, in that one project and one environment.

Claude Code for the people doing the work, and the spend cap in practice. Paid plans start with a call. Free is self-serve. Pricing.