Skip to main content

​
Managed Intelligence: The Agent Lifecycle

The Myrmex Endpoint Agent is designed for zero-touch operation. Once deployed, it maintains itself, ensuring that your infrastructure is always protected by the latest security primitives without requiring manual intervention from your IT team.

​
Support Matrix

The Myrmex Endpoint Agent is a truly cross-platform binary. Whether you are running legacy servers or modern cloud instances, the agent adapts to the environment.
FamilyArchitecturesSupported Versions
Windowsx64Windows 10/11, Server 2016+
Linuxx64Ubuntu, Debian, RHEL, CentOS, Oracle Linux, Amazon Linux, Fedora
macOSarm64macOS 10.15 (Catalina) and later

​
🚀 Installation: Zero to Protected

Deployment is standardized across all platforms using a Universal Installer. This script automatically detects your OS, distribution, and architecture to deliver the correct package.

​
1. Token-Based Authentication

To start an installation, the Myrmex Platform generates an Ephemeral Installation Token. This token:
  • Is valid for 24 hours.
  • Is scoped to your specific organization.
  • Eliminates the need to share long-term administrative credentials during deployment.

​
2. Automatic Configuration

The installer handles everything:
  • Environment Detection: Identifies if it’s running on Linux, Windows, or macOS.
  • Package Installation: Uses native managers (DEB, RPM, MSI, or PKG).
  • Service Setup: Configures the agent to start automatically on boot.
  • Secure Link: Establishes the first encrypted connection to the Myrmex Cloud.

​
🔄 Continuous Updates

Myrmex uses a Supervisor Architecture to ensure your agents are always up to date without impacting system stability.

​
The Auto-Update Loop

The agent includes a dedicated supervisor process (myrmex_supervisor) that monitors for new versions every 24 hours (configurable). When a new version is released:
  1. Background Download: The supervisor downloads the appropriate artifact for the OS/Architecture/Distribution and verifies its integrity via SHA-256 checksums.
  2. Backup & Versioning: A backup of the current binary is created. On Windows, the version_info.json is audited to track the internal build state.
  3. Atomic Swap: The agent service is briefly paused, the binary is replaced, and the service is restarted.
  4. Health Check: The supervisor monitors the new version. If it fails to connect to fleet.myrmex.ai or shows abnormal resource usage, the system triggers an automatic rollback.

​
Safety Guarantees

  • No Manual Reboots: Updates are applied at the service level; no system reboot is required.
  • Fail-Safe Rollback: If an update fails, the agent automatically restores the previous stable version within seconds.
  • Bandwidth Aware: Downloads are throttled to ensure they don’t impact your network performance.

​
🛡️ Security throughout the Lifecycle

  • End-to-End Encryption: Updates are delivered over TLS 1.3 encrypted channels.
  • Code Integrity: Every package is cryptographically signed and validated before installation.
  • Zero Persistence: Sensitive credentials are never stored in plain text on the endpoint; they exist only in secure memory during operation.
For detailed step-by-step instructions on your first deployment, visit the Installation Guide.