@epicscan €0.25Lightweight sanity scan
For everyday changes. EpicScan scans the changed files with one fast pass.
Real per-scan costs: published after benchmarks
Early access · No subscriptions · Pay per scan
Budget-driven code security.Set your price in the PR. We fit the audit to it.
No seats and no monthly plan. Comment @epicscan €0.50 --max-delay 5m on a pull or merge request, and EpicScan plans how deep to scan so it fits your cap and your deadline. You pay only what the scan actually cost.
Early access, still in development. The open-source scanner runs today from the command line and from your own CI. The GitLab merge-request job and the GitHub Action are in private testing. The @epicscan comment command, budget and deadline caps, and prepaid credits are what we are building next. Nothing can be bought yet, and every example and number on this page is illustrative. Questions? Email [email protected].
Example of an EpicScan report
Illustrative example: mock output showing the intended flow, not a real scan result.
reviewer-janeLooking at the C++ changes. @epicscan €0.50 --max-delay 5m
EpicScan Bot (example)Use-after-free in interpreter.cpp:142
Severity: High · Cap: €0.50 · Max delay: 5 min
Scan and credit summary€0.161 of €0.50 cap
| Step | Detail | Cost | Status |
|---|---|---|---|
| Context and scan | Changed files | €0.041 | Within cap |
| Skeptical triage | 5 rounds | €0.120 | Completed |
| Credit deducted | Prepaid pool | −€0.161 | Remaining: €248.34 |
Roadmap: the comment command is in development.
Control every scan from the comment thread
Developers, reviewers and project leads set the budget and the deadline where the review already happens.
@epicscan €0.50 --max-delay 5mDeep scan with a deadline
For release candidates. Aims to finish within 5 minutes and spends up to €0.50 on deeper context, scanning and multi-round triage. If time runs out, you get a partial report instead of a stuck pipeline.
Real per-scan costs: published after benchmarks
@epicscan €5.00 --depth deepThe deepest scan your budget allows
For core or security-sensitive code. Spends the larger cap on wider context and more triage rounds; the report lists exactly what was covered.
Real per-scan costs: published after benchmarks
New here? Read how it works.
Pay per scan, not per seat
No idle seats. You pay for the scans that actually run.
ZERO WASTE
Charged only when a scan runs
RoadmapNo licences for developers who rarely open a pull request. Credit is deducted only when a scan runs, based on what it actually cost. If a scan fails, nothing is charged.
Our hardware, or yours
In testingHosted scans run on our own Mac Studio machines in the Czech Republic. Prefer your own setup? Point the scanner at your own model endpoint. Your code goes only where you choose. Where does my code go?
Deadline-aware scans
RoadmapWith --max-delay 5m, EpicScan will not hold up your pipeline. As the deadline nears, it stops starting new work and posts a partial report of what it covered.
Skips unchanged files
RoadmapRe-scans will skip files that have not changed, so you never pay twice for the same code.
Built for GitHub and GitLab
Live · CLI in your CIRun the open-source scanner from any CI job today. A GitLab merge-request job and a GitHub Action are in private testing. The @epicscan comment trigger comes next.
Simple prepaid credits
RoadmapTop up a prepaid balance, and each scan deducts only its actual cost. Team-level budget caps may follow.
A note on accuracy. AI scanners can flag issues that turn out to be harmless (false positives) and can miss real ones (false negatives). The engine is tuned for C and C++ memory-safety bugs and is less effective in other languages. Findings of medium severity and above go through five rounds of skeptical triage before they reach you. Treat results as strong leads for a human reviewer, not as verdicts.
Where does my code go?
Only where you choose. Hosted scans run on our own Mac Studio machines in the Czech Republic, and your code is not kept after the scan. Self-hosted scans never leave your network.
Our own hardware
Mac Studio machines owned and operated by Epicworks s.r.o. in the Czech Republic. No third-party AI service sees your code.
Not kept after the scan
Your code is deleted when the scan ends and never used to train models. Request logs are kept for up to 30 days.
Or keep it on-prem
The scanner is open source (Apache-2.0). Run it on your own machines and your code never leaves your network.
Simple prepaid credit packs
Draft early-access prices. Nothing can be bought yet.
Developer Starter
€25
prepaid credit
Team Shared Pool
Recommended€250
prepaid credit
Enterprise / Self-hosted
Custom
your infrastructure
Get early access
Tell us where your code lives. We will email you when EpicScan is ready for your platform. No newsletter, no tracking.
Questions
Is EpicScan available now?
The open-source scanner is, and you can run it today. Hosted scans, the comment command and credits are in development. Join early access to try them first.
Which languages work best?
C and C++ today. The engine was built to find memory-safety bugs such as buffer overflows and use-after-free. Other languages work, but with weaker results.
Does it replace a security audit?
No. EpicScan finds strong leads quickly and cheaply. A human still decides what is real.
What will a scan cost?
You set the cap, and a scan never costs more than that. Typical costs per scan will be published after benchmarks.
Can I run it on my own hardware?
Yes. The scanner is open source under Apache-2.0. Self-hosted support with your own model endpoint is in testing.
Who is behind EpicScan?
Epicworks s.r.o., a Czech company. EpicScan is built on nano-analyzer, the open-source scanner by AISLE, and is not affiliated with AISLE.