Pricing
Start free. Scale as you grow.
Every plan includes the full eBPF instrumentation engine, runtime dependency reachability, and behavioral alerts. No per-agent fees.
Pilot
Free
90-day free pilot, no credit card required
5 monitored services, 1 environment
- eBPF kernel instrumentation
- Runtime dependency map
- Reachability-based CVE alerts
- 7-day alert history
- Slack integration
- Community help
Team
$850/mo
Monthly billing, cancel anytime
20 monitored services, 2 clusters
- All Pilot features
- Behavior baseline alerts
- Real-time exploit blocks
- 90-day alert history
- JIRA, PagerDuty, SIEM
- Supply-chain detection
- Priority Slack and email
Enterprise
Custom
Annual contract, volume pricing
Unlimited nodes, multi-region
- All Team features
- Unlimited alert history
- Custom behavior policies
- SSO and SCIM provisioning
- On-prem deployment
- Dedicated success engineer
- Security architecture docs on request
FAQ
Pricing questions, answered
A monitored service is a distinct workload or deployment instrumented by the Oligo agent, such as a Kubernetes Deployment, a DaemonSet pod set, or a standalone application process. Staging and development replicas of a production service count separately. Unsure how to count your environment? Contact us and we will review it with you before the pilot.
Yes. Pilot supports production evaluation. eBPF instrumentation defaults to monitor-only mode: it observes and alerts without blocking. Once the baseline is trusted, enable blocking policies per-cluster.
Team costs $850 per month and is invoiced monthly. Cancel anytime with no early-termination fee. If you exceed 20 services, contact us. We will move you to Enterprise instead of stopping instrumentation mid-sprint.
The Oligo DaemonSet needs privileged pod access to load eBPF programs into the kernel, as is standard for kernel-level observability tools. We support Kubernetes Node Authorization and provide security documentation for reviewing the blast radius before deployment.
Yes, for Enterprise customers. The Oligo analysis engine and data plane can run entirely within your VPC, with no external data egress. Events stay stored and processed in your environment. Contact sales to discuss architecture and compliance requirements.
Questions? Talk to our team first.
We will guide you through deployment and show exactly what the runtime graph looks like in your environment.