MOJO Best Practices¶
This guide outlines hardware, network, and OS requirements to run MOJO reliably.
Quick Rule
Use Minimum specs for evaluation and lab environments. Target Optimal specs for production deployments.
Hardware Requirements¶
| Component | Minimum | Optimal (Recommended) |
|---|---|---|
| CPU | 8 cores | 16‑core Intel Xeon Scalable (Ice Lake+) or AMD EPYC 7003+ |
| Memory | 16 GB | 64 GB ECC DDR4 or DDR5 (target DDR5 for new deployments) |
| Storage (OS) | 80 GB | 2 × 256 GB PCIe NVMe (Gen4+) SSD in RAID 1 |
| Storage (Data) | — | 2 × 2 TB PCIe NVMe (Gen4+) SSD in RAID 1 |
Network Interfaces¶
| Tier | Minimum | Optimal |
|---|---|---|
| Trunk | 1 × 1 GbE | 1 × 25 GbE (Management, Provisioning, Services, BMC VLANs) |
| VLAN | Minimum | Optimal |
|---|---|---|
| Management | 1 × 1 GbE | 1 × 1 GbE |
| Provisioning | 1 × 1 GbE | 1 × 25 GbE |
| Services | 1 × 1 GbE | 1 × 25 GbE |
| BMC | 1 × 1 GbE | 1 × 10 GbE |
Network Requirements¶
| Specification | Minimum | Optimal (Recommended) |
|---|---|---|
| Switch | Enterprise-grade, >14 Mpps, 20 Gbps switching capacity | Enterprise L3, ≥75 Mpps, ≥100 Gbps, 25 GbE downlinks, 100 GbE uplinks |
| VLAN | 802.1q support | 802.1q support |
| Internet | Required | Required |
Operating System¶
| Minimum | Optimal (Recommended) |
|---|---|
| Debian 13/12, RHEL 10/9, Ubuntu 24/22 | Debian 13/12, RHEL 10/9, or Ubuntu Server 24.04/22.04 LTS |
Production Deployments
Always target Optimal specifications for fleets with more than 50 servers or high-frequency provisioning workloads.
These requirements provide a clear guideline for users intending to deploy Metify MOJO, outlining the specifications necessary for both minimum functionality and optimal performance.
Deployment & Architecture Considerations¶
Installation Types¶
MOJO is available in two deployment models: Software Appliance and Hardware Appliance.
Software Appliance (Recommended)¶
The most common and preferred enterprise deployment. Download and install MOJO directly onto one of your existing servers — no dedicated hardware required. MOJO operates as a self-contained software appliance, packaging all platform components into a containerized stack that runs on any Docker-compatible Linux host.
The software appliance is ideal for:
- Enterprise data centers — Deploy on existing rack-mounted servers alongside your current infrastructure.
- Cloud environments — Run MOJO on virtual machines in AWS, Azure, GCP, or any cloud provider.
- Remote and branch offices — Lightweight footprint allows deployment on modest hardware at distributed sites.
- Evaluation and proof-of-concept — Get up and running quickly without dedicated hardware procurement.
See the installation documentation for setup instructions.
Hardware Appliance¶
A purpose-built, pre-configured physical appliance shipped directly to your site and ready to deploy out of the box. Hardware appliances are fully certified and supported by Metify, with configurations tailored to a wide range of deployment scenarios:
- Data center — Rack-mounted appliances designed for large-scale, centralized infrastructure management.
- Edge and remote sites — Compact, ruggedized units for space-constrained environments such as branch offices, retail locations, or remote facilities.
- Telecommunications — Hardened appliances built for cell tower, central office, and network point-of-presence deployments.
- IoT and industrial — Specialized form factors for managing IoT gateways, industrial controllers, and distributed sensor networks.
- Hybrid environments — Appliances that bridge on-premises and cloud infrastructure, providing unified management across hybrid architectures.
Configurations vary widely depending on use case and scale requirements. The hardware appliance is not available for evaluation purposes. Please contact us at support@metify.io to discuss your deployment needs.
Architecture¶
MOJO is a microservices-based platform designed to be highly available and scalable. The platform is composed of several microservices that work together to provide the functionality of the platform. The microservices are designed to be stateless and can be scaled horizontally to meet the demands of the infrastructure.
Components¶
| Component | Role |
|---|---|
| API Server | Main entry point for all API requests, routing to the appropriate microservice |
| Database | Stores hardware inventory, configuration, and state |
| Worker | Executes tasks such as firmware updates, BIOS configuration, and OS provisioning |
| Scheduler | Schedules tasks to be executed by the worker |
| Discovery Service | Discovers hardware on the network |
| iPXE Server | Provides network boot services for OS provisioning |