- Weekly rule updates
- Unlimited local runs
- 1,000 API queries / hour
- GitHub issues. We read them.
For maintainers, researchers, and anyone getting started.
Start on Community →A private VirusTotal for your build pipeline: send a package, a hash, or the artifact itself, and get one explainable verdict. Nothing you send is shared, sold, or searchable by anyone else. In the lab, atomdrift catches 88% of zero-day malware; the next best engine, 68%.
Pricing
Same Apache-2.0 engine and public rules on every tier, run locally without limit. You pay for rule freshness, throughput, support, and rights — at a rate that stays fixed while you subscribe.
For maintainers, researchers, and anyone getting started.
Start on Community →For your own security, CI gates, and developer workflows.
Start with Business →For products and services other people depend on.
Start with Critical →Malicious packages are often pulled within hours of publication; the builds that already consumed them are not. Open-source rulesets ship weekly; subscribers get each rule the hour it clears QA.
Beamline puts atomdrift behind one HTTP call for CI gates, registries, IDEs, and security products: send a PURL, a SHA-256, or the artifact itself. When code cannot leave the building, run the same engine locally — as a CLI, a service, or Rust libraries — with nothing depending on a network, or on us.
Every verdict is deterministic and explainable: a hostile finding names the rule, file, byte offset, source line, and behavior behind it. Pin tool, rule, and model versions and the scan is reproducible.
API documentation →Business and Critical include support for the tools and their APIs: patches, upgrades, and integration help from the maintainers. An engineer replies within two business days — the next business day on Critical, with a phone number for when production is down.
No deck, no discovery call — unless you want one.