# opsen

> Financial infrastructure for software engineering: opsen meters what a company pays for GitHub, Copilot, Actions, GitLab, Azure DevOps, Atlassian, JetBrains, CircleCI and coding agents, finds what is paid for and not used, and takes it out when someone approves. Its MCP server is at https://opsen.dev/mcp.

## Get started
- [Overview](https://opsen.dev/docs/index.md): What opsen measures, what it finds, and what it will change.
- [Quickstart](https://opsen.dev/docs/quickstart.md): From install to a priced report in a few minutes.
- [How the audit works](https://opsen.dev/docs/how-it-works.md): What opsen reads, the windows it looks over, how figures are priced, and what it holds back.

## Findings
- [Seats and invitations](https://opsen.dev/docs/seats.md): Dormant members, dormant outside collaborators, and invitations that hold a seat.
- [Copilot seats](https://opsen.dev/docs/copilot.md): Licences with no activity in the last 30 days, and reclaiming them.
- [Actions minutes](https://opsen.dev/docs/actions-minutes.md): Superseded pull request runs, schedules on dormant repositories, and jobs that hang.
- [Claude Code spend](https://opsen.dev/docs/claude-code.md): Cost per person and per pull request, and people paying for two coding assistants.
- [Cursor](https://opsen.dev/docs/cursor.md): Cursor seats, usage spend per member, and seats nobody used.
- [OpenAI](https://opsen.dev/docs/openai.md): OpenAI API spend, including Codex, by project and line item.

## Platforms
- [GitLab](https://opsen.dev/docs/gitlab.md): Billable seats, Duo seats and compute minutes on gitlab.com or self-managed, and who is not using them.
- [Azure DevOps](https://opsen.dev/docs/azure-devops.md): Basic and Test Plans seats, Visual Studio subscribers, and who has not signed in.
- [Atlassian](https://opsen.dev/docs/atlassian.md): Jira, Confluence, Service Management and Bitbucket users, and who has not opened them in 90 days.
- [JetBrains](https://opsen.dev/docs/jetbrains.md): Every IDE licence, who holds it, and licences that never check in.
- [CircleCI](https://opsen.dev/docs/circleci.md): Credits by project and workflow, and workflows that spend their credits failing.

## Acting on findings
- [Actions and fixes](https://opsen.dev/docs/actions.md): Every change opsen can make, the API call behind it, and how to undo it.
- [Budgets and alerts](https://opsen.dev/docs/budgets.md): A monthly limit for each source of spend, and an email before one is crossed.
- [Sharing reports](https://opsen.dev/docs/sharing.md): Read-only links, invitations, asking an owner, pull request notes, the README badge, Slack and API keys.

## Administration
- [Signing in](https://opsen.dev/docs/sign-in.md): GitHub, Google, GitLab, Microsoft, single sign-on or a code by email. One account, no passwords.
- [Single sign-on](https://opsen.dev/docs/sso.md): Okta, Microsoft Entra ID, Google Workspace or any OIDC or SAML 2.0 provider, with verified domains, roles and enforcement.
- [Audit log](https://opsen.dev/docs/audit-log.md): Every sign-in, access change, setting and action, with who, when and from where. Export as CSV or stream as JSON.

## Developers
- [MCP, plugins and API](https://opsen.dev/docs/mcp.md): Ask opsen from Claude Code, Cursor, Codex or any MCP client, or read it over a REST API.
- [Report JSON](https://opsen.dev/docs/report-json.md): The report as JSON, for dashboards, spreadsheets and alerts.

## Reference
- [Permissions](https://opsen.dev/docs/permissions.md): Every GitHub permission opsen requests, and the call that needs it.
- [Prices](https://opsen.dev/docs/prices.md): The list prices the audit multiplies by, where they came from, and how to replace them with yours.
- [Security and data](https://opsen.dev/docs/security.md): What is stored, how secrets are protected, and who can see what.
- [Billing](https://opsen.dev/docs/billing.md): What is free, what is paid, and how the fee is worked out.
- [Troubleshooting](https://opsen.dev/docs/faq.md): The questions that come up, and what to check.