Priced around the deployment, not the seat.
Where Rokkhe runs, what it may reach, and who has to approve its actions all change what delivery costs. We scope those first and quote against them — rather than publish a number the product cannot stand behind.
Evaluation
A time-boxed authorized engagement that shows how Rokkhe maps, proves, and retains evidence inside your environment.
- Authorized target and scope design
- Validated findings with the evidence pack
- Security architecture walkthrough
- A clear deployment recommendation
Team
Connect pentesting, SOC investigation, and remediation for one security team working from a single queue.
- Agentic SOC cases and investigations
- Native security telemetry adapters
- Threat intelligence and detection workflows
- Workspace audit and approval boundaries
- Deployment and operating-model design
Enterprise
Deploy the platform, its integrations, and a private inference path inside the boundary where your controls already apply.
- Cloud or on-premises deployment
- Private model inference path
- Dedicated data, retention, and support plan
- Security architecture and rollout review
Four things move the number
Nothing here is a surprise line item. These are the variables we work through before anyone signs anything.
Where it runs
Your cloud, your on-premises network, or an air-gapped environment — each carries a different delivery and support shape.
What it may reach
The number of repositories, live targets, and telemetry sources in the authorized scope.
Who approves
Whether response stays advisory, or containment runs behind an independent approval boundary you configure.
Model path
Provider-configured inference, or a private path where prompts and source never leave your boundary.
One platform. Clear responsibility boundaries.
The software can be shared; control ownership cannot. Every model below makes infrastructure, evidence, and response authority explicit.
You operate
Infrastructure, model keys, backups, access, monitoring, updates, and incident response stay yours in a self-hosted deployment.
We scope together
Team deployments define integrations, data paths, retention, rollout gates, and support expectations before any commercial commitment.
Evidence decides
Security and compliance claims need current operating evidence. No tier quietly converts software controls into a certification.