MergeCost documentation
MergeCost comments the estimated monthly AWS and LLM cost of each pull request, with the exact line that causes it and a suggested fix. It measures what your code does in your own CI, using the tests you already have.
How it fits into your workflow
- You install the MergeCost GitHub App on a repository and merge the setup pull request it opens.
- On every pull request, a GitHub Actions job runs your tests on the base and head commits and records, per endpoint, database queries, LLM tokens, outbound API calls, log volume and response size.
- MergeCost prices the difference with your traffic and current AWS/LLM prices and posts one comment on the PR, updated on every push.
Where to start
- Quickstart — first cost comment in a few minutes.
- Supported stacks — frameworks, test runners, databases and LLM providers.
- Configuration — traffic, collection sizes, database cost, budget gates.
- How the estimate works — formulas and confidence levels.
- Troubleshooting — common CI and setup issues.
- Security & data — what is sent, what never leaves your CI.
Requirement: MergeCost prices the endpoints your tests call. Your repository needs API tests (for example Django's test client, FastAPI's
TestClient, Flask's test_client() or supertest).