Pricing and billing

Every plan has Monitor with real-time alerts, the review, Optimize, results recorded from every eval run, the evalship check, badges, PR comments, eval flaws, gating, untested change detection, failure patterns and the weekly report. There are no limits on evals, runs or pull requests: past a plan's events, PR comments keep everything but the model's notes, and the rules keep checking production calls. Production calls and steps are never billed, up to a fair-use limit. For a quote beyond what Business includes, write to sales@evalship.com. The review and Optimize are free for every repository, because your coding agent runs them with your own model subscription and keys.

Launch offer: it ended on November 10, 2026. Accounts that took it keep their discount for as long as they stay subscribed, including after switching plans. Additional usage is billed in full.

Users

Free covers 2 users; Pro and Business take any number. A user is anyone who did either of these on an enabled private repository:

• opened a pull request, or pushed to one they opened;
• signed in to evalship and opened its dashboard, settings, runs, pull requests or evals.

Bots (logins ending in [bot], and GitHub's Copilot coding agent) don't count, and public repositories never do. On Free, the Members page marks who counts, pull request authors who never signed in included.

A user counts until an account owner or organization owner removes them on the Members page, whether or not they're still active. Removing someone also ends their invite, if they had one. If they open a pull request or one of the repositories on evalship again, they count again.

Inviting people

Account owners and organization owners add people on the Members page: members of the GitHub organization in one click, and anyone by email.

• The invite email has a link to join, with GitHub or with that email address. It works once, for 7 days. After that, they get a new link on the sign-in page; links from there work once, for 15 minutes.
• An invite covers every repository in the account: dashboards, runs, pull requests and the review. Settings, billing and invites stay with the owners.
• Joining with GitHub also shows them the repositories they can access there. Someone who joined by email can connect GitHub later from their dashboard. Their invites stay.
• An invited person counts as a user once they open a private repository's reports.
• Removing someone on the Members page ends their access right away, and they stop counting as a user.

Someone without GitHub, such as a manager setting evalship up for their team, can sign up by email on the sign-in page and create an organization on evalship. They own it: they invite their team, and an owner of the team's GitHub organization installs the GitHub App and connects the two on evalship's Get started page. Everyone in the evalship organization then sees the GitHub organization's repositories on evalship, and its creator stays an owner, with billing.

Private repositories

Pro and Business cover any number of private repositories. Free covers one: the first whose setup starts. Picking it in "Set up a repo", connecting it from the setup prompt, or its first review arriving turns it on. "Turn off" on Billing frees its place.

On Free, the account's other private repositories are locked, and their dashboards don't open, until an upgrade or until the other one is turned off. A locked private repository, or one on Free while the account has more than two users, still gets:

• results recorded from every eval workflow run;
• a neutral evalship check titled "PR comments are off for this private repo", saying why, with a link to Billing;
• badges, with the badge token.

It doesn't get a PR comment, eval flaws, a gate, untested change detection or failure patterns. On Free, when the account has more than two users, its private repository keeps its dashboard but pauses this way until it moves to a paid plan or an owner removes a user. Account owners get an email when a repository that had PR comments pauses, as after moving back to Free with more than one private repository.

Additional usage

A paid plan never stops at its events: each 1,000 past the plan's pool is $1. That's the only additional usage: users and repositories are never charged. Billing shows the count, and its upcoming bill what it adds.

Events past the pool count for the month they're in. Each whole 1,000 is billed at the end of the month: on a monthly plan with the next invoice, so the first invoice is the plan's price alone, and on a yearly plan as a usage invoice of its own. A trial has no additional usage: the model stops at the pool. The launch discount doesn't apply to additional usage.

When additional usage costs more than the next plan up, switching saves money: 90,000 events in a month cost $99 on Pro, what Business costs with 100,000 included.

Events

Events are the model's work for you: 1 for each production AI call it checks, and about 40 for each pull request push it writes notes on. Free has 5,000 a month, Pro 20,000 and Business 100,000, for the whole account. Past them, a paid plan keeps going as additional usage, and on Free the model stops until the pool resets. Events has what counts, what never does, and when the pool resets.

Eval history

Each run keeps its test cases' results (pass or fail, score, input and output) for as long as the plan's eval history: 30 days on Free, one year on Pro and two years on Business. Older ones are deleted nightly, except the latest run on the default branch, which the next pull request compares with. Run summaries stay, so trend charts, pass rates and PR comments keep working. After switching to a plan with a shorter history, results past it go the next night; Billing asks before the switch. When a subscription ends, its plan's history stays for 30 days, then Free's applies.

Support

• Self-serve on Free: the docs. Report bugs to hello@evalship.com.
• Priority email on Pro: write to hello@evalship.com, answered before Free.
• Shared Slack channel on Business, with the people who build evalship. Ask for it at hello@evalship.com with your Slack workspace's name.

Choosing a plan

Billing shows the plan, the events used, the upcoming bill and what each plan covers.

• A paid plan, from Free, opens a checkout at Polar with a 7-day trial the first time.
• Switching between paid plans, or between monthly and yearly billing, changes the subscription in place. Polar prorates the difference, and a launch discount stays.

Billed yearly

Every paid plan can be billed once a year for 10 months' price, so 2 months are free: Pro is $290 a year and Business $990. Pick Yearly above the plans on the homepage or on Billing.

• Events are the same monthly pool as on a monthly plan, reset each month from the day the year started.
• Additional usage costs the same as on a monthly plan: $1 per 1,000 events past the pool. It's billed at the end of each month, on a usage invoice of its own.
• Back to Free is canceling the subscription in the billing portal.

The subscription belongs to the GitHub account or organization that installed the App. For a personal account, only that user can enable or disable repositories and change the plan; for an organization, its owners can, on GitHub or on evalship. Everyone with access to a repository can use evalship on it.

Billing

Billing runs through Polar, which is the merchant of record: Polar charges the card, handles VAT and sales tax, and issues invoices. On evalship, Billing's Invoices, payment and cancellation button takes account owners and organization owners to the Polar customer portal, where they can download invoices, change the payment method and cancel.

Uninstalling the GitHub App cancels the subscription at the end of its billing period, and a trial ends without a charge. Reinstalling before then keeps it.

If a payment fails, PR comments keep working while the subscription is past due. When the subscription ends, the account goes back to Free. 30 days later, eval results older than Free's 30-day eval history are deleted; everything else stays.

Questions about billing: hello@evalship.com.