Start with required routed throughput under the features you will actually enable. Count the right Ethernet and fibre interfaces, PoE needs, rack format, power redundancy, VPN workload and expected configuration lifetime.
Size for the configured workload
Routing performance changes with firewall rules, queues, VPN encryption, connection tracking and other enabled services. Define expected internet and inter-site traffic, concurrent connections and growth before selecting the platform.
- Required copper and fibre interface speeds
- Firewall, NAT, VPN and traffic-management workload
- PoE input or output and total power requirements
- Desktop, outdoor or rack installation and cooling
Check RouterOS and operational fit
Confirm the RouterOS licence and features required, the supported software lifecycle, configuration backup, monitoring and the skills available to operate the device safely. A lower purchase price does not help if the chosen model creates an unsupported edge.
Plan resilience around the router
Consider dual power, spare hardware, configuration recovery and the primary and backup access paths. Liberty-i can check a proposed model against the interfaces and service design before an order is placed.
Prepare for a useful design conversation
Bring evidence rather than a preferred product model. A short discovery call is more productive when it covers the sites, users, applications and operational consequences involved. Existing diagrams, circuit details, recent fault patterns and realistic growth expectations help distinguish a capacity problem from a coverage, configuration, resilience or support problem.
- Sites, opening hours and important business periods
- Current services, equipment and known constraints
- Critical applications and the impact of interruption
- Internal owners, support expectations, budget range and target date
Turn the requirement into a design
Liberty-i will use that context to identify dependencies, explain realistic options and record the assumptions that affect cost or delivery. The result should be a supportable design with clear ownership, acceptance tests and next steps—not simply a shopping list.