Two scheduled feature releases each year.
Maintenance releases ship as required. Security fixes are not held for feature windows.
JAN–JUNJUL–DEC
Engineers answer support
Useful answers from people who know the subsystem.
Support requests go directly to someone familiar with the relevant product area. Complex problems may go directly to the engineer responsible for the code involved.
Contact support- 01 exact product version
- 02 operating system or target
- 03 relevant configuration
- 04 timestamps and packet captures
- 05 expected behavior
- 06 observed behavior
“It doesn’t work” is accepted.
It will generate follow-up questions.
01 / RELEASE POLICY
Different systems require different clocks.
Release speed is not a goal by itself. Supported software should move at a rate its deployment environment can absorb.
Slower releases. Longer support.
Embedded customers have correctly explained that updating twelve thousand physical devices is not equivalent to updating a web application.
SUPPORTED BRANCH
02 / COMPATIBILITY
Do not break the network because a cleaner protocol can be imagined.
New fields are generally additive. Readers ignore fields they do not understand. Writers do not assume every reader was compiled last Tuesday.
OLD READER←known_field=42
new_field=17→NEW READER
new_field=17→NEW READER
03 / SECURITY
Data movement is explicit.
FleetWatch agents use administratively defined collectors. They do not discover arbitrary external services or silently fall back to vendor-operated infrastructure.
No connection to us required
Self-hosted deployments operate without connectivity to Insight-Technology.
Offline operation available
Offline license activation and signed update packages are available for isolated installations.
Direct engineering contact
Security issues affecting supported releases can be reported directly to the engineering team.
04 / HARDENED BUILDS
One maintained source tree. Less exposed surface.
For regulated, offline, and sensitive environments, hardened FleetWatch and ChipWatch builds can reduce diagnostics, strip metadata, constrain feature sets, and add binary hardening.
Security fixes are carried across standard and hardened product lines. Reproducible-build documentation and offline media are available through Enterprise Support.
We do not describe obscurity as cryptography.01Reduced diagnostic output
02Stripped metadata
03Customer-specific feature sets
04Signed offline update packages
05Additional binary hardening
06Reproducible-build documentation
SUPPORT & SECURITY
Send enough information to reproduce it.
Please do not attach a 4 GB virtual-machine image without warning. This request exists because somebody did.
sales@insight-technology.org