Managed Onboarding
The deployment step, taken off your engineers. We build the tenant, connect the log sources, prove the data is actually arriving, and hand back a platform that is already producing alerts — then get out of the way. It is priced per deployment, so your cost is known before you quote the project rather than after.
$367.50USDper deployment
List $490 — what your customer pays. You keep the difference. · 25% off list
- Priced by
- per deployment
- Delivered as
- Your brand, your template
- Client access
- Scoped, granted by your customer
Scoped before you quote, not after you have sold it
Fixed price per deployment with a written definition of done, not an open-ended time-and-materials build.
Every log source is validated with a test event before handover — firewall, endpoint, cloud, identity — so nothing is merely configured and assumed to be working.
Baseline detections and dashboards are enabled at handover, so the tenant produces something meaningful on day one instead of after the first tuning cycle.
Retention and log-integrity settings are configured against Thai Computer Crime Act requirements where the customer needs them, on a log platform certified to Thai standard มศอ. 4003.1-2560 for computer traffic data retention systems.
The handover pack contains the architecture note, the source inventory, the credential list and a runbook, written for your engineer to operate from.
A follow-up review is booked once the tenant has seen real traffic, so the first tuning pass happens before your customer starts noticing noise.
You quote it, we operate it, you deliver it
Your price is the published list price minus 25%, on every line in the catalogue. You decide what your customer pays and keep the difference, so your margin is settled before the quotation leaves your office.
Our engineers work it from Bangkok on UTC+7, against a methodology that is written down rather than improvised per customer. A senior engineer reads every finding before it leaves the building, because you are the one who has to defend it.
Findings, reports and escalations reach you in your template with your logo on them. Your customer talks to you, and our name is not on the ticket.
What a partner checks before putting this on their price list
Do you stay involved after handover?
Only if you ask us to: the deployment ends with a working tenant and a handover pack, and running it afterwards is either your own team's job or a separate Managed SOC Operations subscription.
Who talks to the customer's IT team during the build?
You do — we take the requirements from you, send configuration questions back through you, and do not join calls with your customer. If a joint session is unavoidable, your engineer runs it with us briefed behind them.
What if the customer's environment turns out to be a mess?
The fixed price covers the deployment as scoped. Where a source cannot be connected because of something on the customer side, we document precisely what is blocking it and hand that back to you, rather than absorbing it silently and slipping the date.
How long does a deployment take?
It is driven by how quickly log sources are made available, not by our queue. You get a schedule with every customer-side dependency named up front, so the timeline you quote is one you can defend.
Does this include the platform licence?
No — the zcr licence comes from zcr.ai, and this is the delivery work of standing it up. They can be bought together but they are priced as two separate lines, so you can mark them up differently.
Can we do the deployments ourselves later?
Yes — the handover pack is deliberately written so your engineers can repeat the build without us. Buying the first few deployments and taking the rest in-house is a normal path for a reseller partner.
Pick one customer. We will run it for 60 days.
Choose a customer you already serve. We deliver Managed Exposure on their domain for two months, in your template, at no cost — so you can see exactly what your customer would receive before you sign anything.
Apply as a partner