Deployment
A SaaS platform. Sensors where your workloads run.
The platform
Use it, or build on it.
Platform · SaaS
Solomon as a service
The Solomon Agentic AI Platform and Solomon SOC, run by us on AWS. Nothing to install or operate on your side.
- Multi-tenant SaaS on Amazon EKS
- One isolated tenant per customer: its own database, event streams, storage, vector memory and secrets
- Your own Solomon SOC console on your own subdomain, with single sign-on
- Telemetry and connectors reach the platform only through the Solomon gateway
Platform · PaaS
Build on Solomon
Use the same platform from your own code and products, through the gateway and the official SDKs.
- SolomonPy (Python) and SolomonJS (TypeScript and Node)
- Developer keys from the VIntercept portal
- The same tenant isolation and deterministic action checks as the SaaS
Your environment
How your estate connects.
Mix and match: connect clouds and tools agentlessly, and add the eBPF Client to the workloads that need prevention.
Agentless
Cloud accounts and existing tools
Connect clouds and the security tools you already own, with read-only access where that is all that is needed.
- AWS through a cross-account IAM role, Google Cloud through a read-only service account, Azure through a Reader service principal
- 35 native Solomon OmniMesh connectors for identity, endpoint, cloud, network, SIEM and ticketing tools
- Credentials stored per tenant in Vault
Linux hosts
Solomon eBPF Client on servers and VMs
The kernel-level sensor for Linux, installed as a system service on each host.
- Signed .deb and .rpm packages, running as a systemd service
- Tested on Amazon Linux 2023 and 2, RHEL 9, Ubuntu 20.04, 22.04 and 24.04
- x86_64 (Intel) and arm64 (AWS Graviton)
- OCSF telemetry over mTLS, spooled locally while the platform is unreachable
Kubernetes
Solomon eBPF Client on Kubernetes nodes
Protect nodes and pods on Amazon EKS and self-managed clusters.
- A Helm-installed DaemonSet, or the systemd service on each node
- Amazon EKS and k3s nodes
- Policies scoped to pods by label, namespace or service account
Other requirements
Need something else?
Self-hosted, single-tenant or air-gapped deployments of the platform are not a standard offering today. If your data residency or regulatory requirements need one, tell us what you need and we will tell you honestly what is possible.
Let us help you choose.
The right setup depends on your environment, size and constraints. We work it out with you during the guided pilot.