SECURITY / DATA HANDLING
Your data never leaves.
The strongest data-handling posture is the one where there is no data to handle. Arclane runs in your account and sends nothing out.
HANDLING / WHERE
- Runs entirely inside your VPC. Egress is zero bytes by default.
- Stateless solver, stop and fleet data live in your systems, not ours.
- No telemetry, no licence phone-home, no usage beacons.
- Retention is whatever your own storage policy says; we hold nothing.
SUPPLY / CHAIN
- Images
- signed (cosign)
- SBOM
- published per release
- Base image
- distroless, non-root
- Root FS
- read-only
- CVE scanning
- every build
DATA FLOW / IN, NEVER OUT
Everything happens inside the fence.
Three arrows, all internal. There is no fourth arrow pointing at us.
IN
Read your systems
Stops and fleet come from your TMS, OMS, or a CSV, over your own network.
COMPUTE
Solve in your VPC
The container plans on your hardware. State is held in memory, then discarded.
OUT
Write your systems
The plan and reason codes go back to your dispatch, your apps, your storage.
No fourth arrow: 0 bytes to any Arclane or Zeceholdings endpoint. There is no telemetry beacon to block.
Questionnaire pack
Procurement asks the same questions every time. We keep answered SIG, CAIQ, and a plain-language data-flow diagram ready to send, because zero egress makes most of the form short.
Request the pack