Find serious bugs and vulnerabilities in your codebase.
1000s of AI agents scan your codebase to find bugs and security issues.
cubic automatically notifies the user or team who introduced an issue.
Fits into your workflow.
Automatically create PRs for detected issues, or create tickets to developers who introduced a bug.
Issues are automatically resolved when a fix is merged.
Repeat on a schedule or before a big release
Run scans on a schedule to catch new issues.
Catch bugs and vulnerabilities with deep codebase scans
Gives developers everything they need to triage and fix issues fast.
Triage
Triaged issues with clear explanations, so you can focus on what matters most.
Assign
cubic identifies and notifies the issue owner.
Fix
Integrates with AI IDEs to fix locally, or use AI cloud agents to create fix PRs.
Frequently asked questions
Your question not answered here? Email us.
What counts as a reviewed line?
Reviewed lines are the PR code changes cubic actually reviews, not repository size, total file size, or lines generated by AI. For most PRs, this means the added and deleted lines in the diff that cubic reads during review. Generated files, vendored code, binaries, ignored files, skipped files, and failed or cancelled reviews do not count. Incremental reviews only count newly reviewed changes; manual reruns count again.
When does usage reset?
Reviewed-line usage resets with the billing period.
Do generated or ignored files count?
No. Generated files, vendored code, binaries, and files ignored by cubic configuration do not meaningfully count toward reviewed-line usage.
What programming languages do you support?
cubic is language-agnostic and supports all popular programming languages, including JavaScript, TypeScript, Python, Go, Ruby, Java, and C#.
Do you have an open source plan?
Yes, cubic is free for public repositories. Just connect cubic to a public repository to get AI reviews.
