The Binarly Transparency Platform ships in two deployment models. Most organizations start with SaaS, which requires no infrastructure investment. On-premises deployments are available for customers whose data classification policies, network boundaries, or regulatory requirements prohibit the use of cloud-hosted services.Documentation Index
Fetch the complete documentation index at: https://docs.binarly.io/llms.txt
Use this file to discover all available pages before exploring further.
SaaS
Binarly hosts and operates the platform on your behalf. Each customer instance is fully isolated — no multi-tenancy, no shared data storage, no cross-customer access of any kind. Anonymous, aggregate performance and health telemetry is collected to maintain cluster availability; beyond that, customers retain complete control over their platform and the data within it. SaaS is the right choice when your organization can route binary artifacts to an external service. The benefits:- No infrastructure to provision. No Kubernetes cluster, persistent storage, or database to stand up or maintain.
- Automatic updates. New detection rules, platform features, and threat intelligence are delivered without action on your part.
- Instant onboarding. Accounts are activated by logging in. CI/CD integrations are a single API token away.
- Live threat intelligence. The platform has continuous access to Binarly’s threat feeds and research-backed detection updates.
On-premises
On-premises deployments run the same platform inside your own infrastructure. The installation is Kubernetes-based and mirrors SaaS functionality, with narrow exceptions for features that require external connectivity — live threat intelligence feeds and remote-assisted support, for example. On-premises is appropriate when data must stay within organizational or sovereign boundaries:- Classified and government environments where policy mandates that analysis artifacts never leave controlled networks.
- Air-gapped networks with no permissible path to an external service.
- Regulated industries where compliance frameworks prohibit cloud processing of sensitive firmware or software artifacts.
- Internally developed source code that cannot be transmitted outside the organization under IP or contractual terms.
| SaaS | On-premises | On-premises air-gapped | |
|---|---|---|---|
| Live threat intelligence | ✓ | Partial | — |
| Automatic updates | ✓ | Partial | — |
| AI-assisted analysis | ✓ | Partial | — |
| Remote support | ✓ | Partial | — |
| Dev/SecOps integration | ✓ | ✓ | ✓ |
| Self-managed infrastructure | — | ✓ | ✓ |
Partial means the feature is available when the on-premises deployment has outbound internet access. Air-gapped deployments receive threat intelligence and detection rule updates through periodic offline update packages delivered by Binarly.