The Anvil!

Challenge:

Marine vessels rely on high-latency, low-bandwidth satellite connections (e.g., VSAT, Inmarsat), often with prolonged periods of complete disconnection. This renders most cloud-dependent systems less reliable.

Anvil! Capability:

• Fully Autonomous Operation: The Anvil! platform runs entirely on-vessel eliminating any dependency on internet or cloud services.
• Local Provisioning & Recovery: All provisioning, orchestration, and fault recovery are handled autonomously by self-contained infrastructure.
• Deferred Remote Sync: Metrics and logs can be stored locally and queued for transfer when bandwidth becomes available.

Challenge:

As the industry becomes more dependent on digitization, vessels are running more and more on-vessel applications and servers. This requires multiple applications and servers that take up space and require individual management. Marine environments are often limited in space, power, and on-board expertise.  

Anvil! Capability:

• The Anvil! can host and consolidate multiple servers and application on a single platform.
• Compact Footprint: Operates with as few as two nodes and a controller; the system fits within tight spatial constraints.
• Only one platform to manage – Designed to run autonomously and self-manage.
• Simple management interface.

Challenge:

Vessel crews are not trained to manage complex IT infrastructure. Remote troubleshooting is often hindered by latency, bandwidth limitations, or time zone delays.

Anvil! Capability:

• Self-Healing Automation: Fully autonomous, self-healing system with automated fault detection and recovery. The system continuously monitors health and automatically detects and remediates failures (e.g., service restarts, node fencing, VM failovers).
• Designed to survive multiple failures for extended periods. Fully redundant infrastructure.
• Model-Based Rebuilds: Systems can be restored using predefined configurations, removing the need for specialized IT intervention.
• Web-Based Interface (Striker): A simplified dashboard allows non-technical users to monitor and interact with the platform securely both locally and remotely.

Challenge:

Marine environments introduce factors that can be hostile – salt, vibration, heat, and unconditioned power—conditions not ideal for standard data center equipment.

Anvil! Capability:

• Hardware Flexibility: Supports multiple grades of equipment: CoTS, ruggedized, marine-grade, or fanless systems.
• Low power draw; Can fit into tight, unconditioned enclosures.
• Hardware selection and environmental hardening are customizable by the client or integrator. Anvil! is designed to support a wide range of equipment.

Challenge:

Older equipment uses proprietary protocols or inconsistent data formats, making integration with modern platforms complex.

Anvil! Capability:

• Non-Disruptive Deployment: Anvil! can coexist with legacy systems without requiring modification.
• VM Encapsulation: Legacy applications can be run in virtual machines for improved manageability and isolation.
• Custom Scripting Support: Integration hooks allow for protocol adapters or automation bridges to existing applications and / or equipment.
• No disruption to existing infrastructure.

Challenge:

Shipboard data may not sync with shoreside systems for days. Meanwhile, configuration drift can develop between vessels.

Anvil! Capability:

• Local State Retention: Logs, metrics, and system history can be stored locally and survive extended disconnects.
• Config Enforcement: The system state is maintained according to a defined model, ensuring consistency across installations.
• Offline Rebuild Support: System definitions can be applied or refreshed as soon as connectivity resumes or during port stops.

Challenge:

Vessels must comply with cyber risk management guidelines which are difficult to audit in disconnected environments.

Anvil! Capability:

• Comprehensive Logging: All system activity (e.g., reboots, failovers, configuration changes) is logged locally.
• Offline-First Compliance: Data never leaves the vessel unless explicitly exported, supporting data residency requirements.
• Configuration Traceability: Changes are tracked in versioned configuration files suitable for regulatory review.

Challenge:

Legacy systems often lack security controls. Poor segmentation, shared credentials, and outdated software increase the attack surface.

Anvil! Capability:

• Network Isolation Support: The Anvil! platform can be deployed on dedicated or segmented networks (VLANs), limiting IT crossover risk.
• Access Control: SSH key-only authentication and role-based access help prevent unauthorized use.
• Immutable System Models: Configuration is enforced from a controlled definition, limiting drift and potential tampering.
• VMs and applications are isolated from the host platform.

Challenge:

IT Infrastructure is often tied to specific vendors or application. This reduces flexibility to choose optimum applications or infrastructure.  

Anvil! Capability:

The Anvil! is completely hardware and application agnostic.  

• Operates on various hardware grades and equipment vendors.
• Compatible with any modern OS and application.
• Compatible with legacy OS and applications. 
• Custom application interfacing available enabling compatibility with other vessel devices.

Challenge:

IT budgets are scrutinized. ROI must be clearly demonstrated, especially in environments where IT is seen as overhead.

Anvil! Capability:

• No Licensing Fees: Anvil! is open-source, and commercial support is optional—ideal for CapEx-focused models.
• Automation Reduces Costs: Less reliance on remote or onsite IT personnel.
• Downtime Mitigation: Ensures service continuity, protecting operational revenue and compliance uptime.
• Repair planning: Failed equipment can be scheduled for repair during convenient and cost-effective windows.

Challenge:

Short port windows and the need for regulatory approval can slow down or prevent new system installs.

Anvil! Capability:

• Rapid Deployment: Systems can be provisioned with all VMs and applications in advance and activated onboard in minutes.
• Transportable Clusters: Clusters can be shipped pre-imaged and validated prior to installation.
• Pre-Approved Configuration Models: Setup files can be reviewed and tested before vessel integration.