Services
Some run it themselves.
We are here either way.
CloudPeek is a platform first, and it stands on its own. Services are an option, not a requirement: specialists behind the product who can deploy into hard constraints, support your accreditation route, and take as much or as little of the running as you want to hand over.
Operating model
One platform. Three ways to run it.
Self managed
Your team, our platform
Licence CloudPeek and run it inside your own SOC. Your workflows, your playbooks, your dial settings. Support, upgrades and the connector builder come with it.
Co managed
Shared running
Our engineers build and tune workflows alongside your analysts, on your data. You keep every decision; the capability transfers to your team as you go. Where most engagements start.
Fully managed
Managed agentic operations
CloudPeek specialists operate the platform on your behalf. Same headcount, considerably greater throughput, and your data never leaves your estate. Step down a tier whenever you are ready.
Move between tiers as your team grows into it. The platform, the record and the control model stay the same in all three.
Strategic services
The work around the platform.
Deployment engineering
Into your boundary, not near it
Cloud first, on premises, sovereign hosted or fully air gapped. Sensitive network deployment patterns, delivered by people who have done it where reconnecting is not an option.
Accreditation route
Evidence shaped to your regime
The append only record, export packs and documentation shaped to your assurance regime, so the platform arrives with the evidence your accreditors and auditors ask for.
Workflow engineering
Playbooks built on your data
Workflows and playbooks designed, tested and promoted against your alerts and your estate, with your analysts trained on the promotion track as part of the engagement.
Model strategy
The right model, where you need it
Frontier, sovereign or CloudPeek’s own small language models: selection, hosting and evaluation inside your boundary, with no external model calls required at any point.
How it starts
From briefing to production.
01 · Briefing
What you run, what hurts, where the constraints are.
02 · Scoping
Environment, integrations, autonomy posture and the accreditation route.
03 · Pilot
In your environment, on your data. Bring a week of alerts nobody got to.
04 · Production
At the autonomy level you choose, with the record on from day one.
