ctHelixCAD™ Portable is the portable variant of ctHelixCAD™ — same dispatcher console, same feature set, same security posture. Built for private security firms, event operations, command posts, smaller agencies, and EOC-table backup deployments.
Launches alongside ctHelixCAD™. Portability and full security, in the same release window.
Where it stands
ctHelixCAD™ Portable ships in the same release window as the primary ctHelixCAD™. Same codebase, same feature library, same security primitives — designed from day one with portable deployments and smaller-organization operations in mind.
Two SKUs of one product, sized to the shape of the operation. If your team has a launch-window deployment in mind — security detail, event season, command post, or backup-CAD posture — get in touch.
Who it's for
Most CAD systems force a choice between enterprise scale and field portability. ctHelixCAD™ Portable refuses the tradeoff — the full feature set and the full security posture, packaged for the operations the 24/7 dispatch center isn’t the right answer for.
Stadium events, executive protection details, campus and venue security. A self-contained CAD on the firm’s own hardware — encrypted at rest, full audit, no shared cloud. The after-action report writes itself, and the client gets a single defensible PDF.
Run from a hardened mini-PC or ruggedized laptop at the operational table. Bring it on-site for the day, the weekend, or the season. Encrypted at rest, snapshotted to your backup target, then archived between deployments.
County fairs, festivals, marathons, holiday markets. Spin up a self-contained deployment for the event, pack it down at the close. Same configuration year over year — clone last year’s plan in under a minute.
Volunteer fire departments, small-town PD, campus safety, transit authority ops. Full dispatch capability without the infrastructure footprint of a 24/7 dispatch center.
A monthly market, a quarterly drill, a seasonal detail. Bring it back when you need it. Numbering tokens keep each cycle uniquely tagged without operator math.
Primary CAD goes down. A pre-staged portable instance comes up on the EOC table in minutes — pre-loaded rosters, pre-built CFS codes, ready to take traffic. Full incident log to reconcile when primary returns.
Variant, not a fork
Portable isn’t a separate product line — it’s a packaging variant of ctHelixCAD™. The dispatcher surface, the audit model, and the configuration library are identical. Operators who learn one already know the other.
What changes is the deployment shape: single self-contained host, encrypted at rest, snapshotted and archived between cycles. Everything above that line is the same code your full-time deployment runs.
The dispatcher console is the ctHelixCAD™ console. Unit board, incident lifecycle, transport flow, status engine, PDF reporting — what an operator learns on one runs the other.
Posts, rosters, CFS codes, numbering tokens, weather alerts, mileage tracking, transport workflow, audit trail, mobile companion. The full ctHelixCAD™ feature library, with EMS Transport available as an add-on.
Every mutation timestamped and attributed. The after-action document writes itself, in the same defensible format the 24/7 dispatch deployment produces.
Encrypted at rest, TLS in transit, Argon2id credentials, role-based permissions, isolated mobile auth surface. Portable doesn’t mean reduced security — every primitive is inherited unchanged from the primary release.
A 20-minute demo with the team who built it. Bring the operation you're sizing it for — event ops, security detail, command post, smaller agency, or backup CAD.
