Updated Reviewed by Charlton Swearingen, CBO
The main difference between LimaCharlie and Orca Security is how each sees a cloud workload. Orca snapshots VM disks on a schedule. LimaCharlie connects read-only to the same clouds and ties each finding to an EDR sensor that watches the machine live and can kill a process or isolate the host.
Pricing differs too. LimaCharlie charges a flat price per customer tenant, however many resources that customer has.
The quick verdict
At a glance
The main differences between the platforms, side by side.
| Capability | LimaCharlie | Orca Security |
|---|---|---|
| How it connects | Agentless, read-only API roles with 15 connectors | Agentless disk snapshots (SideScanning), plus an optional eBPF runtime sensor launched in 2025 [1] [5] |
| Posture and compliance | 300+ built-in posture rules, custom rules, and 15 frameworks with auditor CSV export | Yes [1] |
| Attack paths and identity | Security graph, toxic combinations, chokepoint ranking, effective permissions, privilege escalation, and dormant admins | Yes [1] |
| How fresh the view is | Scheduled sweeps plus on-demand refresh. GCP changes arrive in seconds through the change feed | Snapshot-based. PeerSpot reviewers cite a 24-hour scan cycle [4] |
| Runtime response | Full EDR: kill, isolate, memory and file collection, YARA, and live forensics, with a year of telemetry | Sensor detections. Process termination is the only response action Orca names [1] |
| Code security | IaC, secrets, dependencies, and container images in GitHub, GitLab, and Bitbucket | Yes [1] |
| Same console as SIEM, EDR, and email | Yes | No. CNAPP only [1] |
| Multi-tenant for MSSPs | Built in: cross-tenant fleet board, org groups, everything configurable as code | MSP portal announced in 2025-26. MSSP pricing not published |
| Pricing | Flat per customer tenant. See current pricing → | Not published. Sold per workload, usually on annual contracts [2] [3] |
Runtime visibility
A disk snapshot shows that a vulnerable package is installed. The LimaCharlie sensor shows whether it’s running, who launched it, and what it connected to, and you can stop it from the same screen. Orca now ships an optional runtime sensor, and process termination is the only response action it names.
| Capability | LimaCharlie | Orca Security |
|---|---|---|
| Vulnerabilities without a sensor | Data from AWS Inspector, Azure Defender, and GCP VM Manager | Disk snapshots [1] |
| Vulnerabilities with a sensor | Daily package inventory matched to CVEs with KEV and EPSS, plus every process that executes | Sensor detections [1] |
| Response | Kill, isolate, collect memory and files, and run YARA | Process termination [1] |
Running it as an MSSP
LimaCharlie onboards a new customer from a template in Git, shows every tenant’s cloud posture on one fleet board, and pushes one policy change to all of them. Orca announced an MSP portal in 2025-26 and doesn’t publish an MSSP pricing model.
| Capability | LimaCharlie | Orca Security |
|---|---|---|
| Multi-tenancy | Cross-tenant fleet board and org groups | MSP portal announced in 2025-26 |
| Getting started | Self-serve, with a free tier for labs and demos | Sold per workload, usually on annual contracts [3] |
| Forwarding findings | Every finding streams as an event to Splunk, Elastic, S3, GCS, BigQuery, Pub/Sub, a webhook, or syslog | CNAPP only [1] |
API and AI access
Both platforms publish APIs. Orca offers a REST API authenticated with API tokens, and some of its role and permission documentation requires an Orca support login. LimaCharlie makes every console action an API call, and cloud findings become events that can start AI agents from detection rules.
| Capability | LimaCharlie | Orca Security |
|---|---|---|
| API coverage | Every console action is an API call: REST API, LimaCharlie CLI, Python and Go SDKs, and an MCP server | REST API with token authentication, with regional endpoints [6] |
| Documentation | Public docs | Some role and permission docs require an Orca support login [6] |
Pricing model
LimaCharlie Cloud Security is a flat price per customer tenant that doesn’t grow when the customer adds VMs, and you can add EDR to any of those VMs whenever you need it. Orca’s AWS Marketplace list price is $7,000 a month for up to 100 EC2 workloads, and Vendr reports a median Orca contract of about $96,500 a year.
| What’s included | LimaCharlie | Orca Security |
|---|---|---|
| Price model | Flat per customer tenant | Per workload [2] |
| Runtime EDR | Add it to any VM, billed on usage | Optional sensor [5] |
| Buying model | Annual agreement or month to month | Usually annual contracts [3] |
Why MSSPs switch
01
The flat price covers posture, compliance, attack paths, identity, and asset inventory. It doesn’t grow when the customer spins up more VMs.
02
The sensor shows a vulnerable package running, who launched it, and what it connected to, and you can stop it from the same screen.
03
Cloud findings land in the same tenant as endpoint telemetry, cloud logs, and email security. One rule can join an exposed VM with a known-exploited CVE to the shell it just spawned.
04
Self-serve, with a free tier for labs and demos, so you can test on your own customers first.
It’s a very low barrier to entry. I’d say you can go in and experiment with it, and if you don’t like it, that’s fine. And you’re not stuck with it for a year... you don’t have to commit to a thousand endpoints for a year to just give it a shot.

Co-founder, Soteria
LimaCharlie was really designed with service providers in mind. It was multi-tenant. More important for me, it was designed to be built upon and extended and expanded.

CTO, Recon InfoSec
We’re very much in our SOC, like an MSSP, in the fact that we have multiple customers with multiple different levels. Also, when we’re looking at licensing, getting down to brass tacks, the model for a lot of vendors is not flexible to work with us as we scale up.

CEO, Black Hills Information Security
FAQ
Compare more tools
Book a demo with our team, or open a free tenant and connect a test endpoint today.
Orca Security details come from the public sources below, with the date of each source. Negotiated prices vary. Product names belong to their owners.