By Global ITN · 18 November 2026

Should a Singapore office choose Meraki MX or FortiGate?

Choose Meraki MX or FortiGate by testing which platform meets your security, connectivity and operating requirements with a workflow your team can maintain. Compare complete designs, including management, subscriptions and migration, rather than selecting a winner from brand names or headline throughput.

Illustration of Meraki MX design, FortiGate design, One requirement set, using compare equipment and workflow composition

Begin with the team operating the network

Ask who will make routine changes, investigate incidents and approve firmware updates. Include the Singapore office, any regional IT team and external support providers in that discussion.

Cisco lists centralised management among MX capabilities, while Fortinet documents shared and device-specific policy packages through FortiManager. Cisco MX licensing guide Fortinet policy management

Use a demonstration to compare the tasks your team actually performs. Have an administrator trace a blocked application, change a branch rule and review a proposed configuration update. Assess permissions, audit evidence and recovery steps as part of that exercise.

Illustration of Local operations, Regional IT, Support provider, using team equipment and workflow composition

Compare the required security policy

Write one requirement list for both proposals. Include segmentation, filtering, intrusion prevention, remote access and any encrypted traffic inspection requirement. Ask where each control runs and what hardware, firmware, subscription or external integration it needs.

Avoid assuming that similarly named functions inspect traffic in the same way. Request a worked example for important applications, with any limitations and exceptions documented.

Define how security events reach the people responsible for responding. A product feature list does not establish who will monitor it or what happens after an alert.

Illustration of Same policy checklist, Application traffic, Inspection and controls, using policy equipment and workflow composition

Test SD-WAN against business behaviour

Describe the applications and paths the office needs: local internet access, branch-to-hub traffic, cloud networks and remote workers. Identify what should happen when a circuit degrades or fails.

The Fortinet SD-WAN ordering guide distinguishes appliance selection and optional service components. Ask for an explicit entitlement map instead of treating the phrase SD-WAN as a complete specification. Fortinet SD-WAN ordering guide

For a deeper comparison, use our FortiGate SD-WAN subscription guide and Meraki MX licence-tier guide. Give both proposals the same failure and recovery tests.

Illustration of Normal application path, Degraded circuit, Business behaviour, using routes equipment and workflow composition

Size the two designs on comparable workloads

Supply measured demand, simultaneous devices, VPN topology and growth assumptions to both designers. Require their performance comparisons to describe enabled security controls and test conditions.

Cisco’s sizing guidance cautions that performance changes with software and features, and recommends validation for the actual environment. Cisco MX sizing guide

Request a pilot when the outcome depends on unusual traffic, inspection or third-party interoperability. Record which findings come from documentation and which come from the pilot.

Illustration of Comparable measured demand, Document test conditions, using performance equipment and workflow composition

Compare total cost and change effort

Ask for a like-for-like quote covering hardware, licences or subscriptions, support, implementation, migration, configuration, testing, documentation and any ongoing management. Clarify renewal terms and ownership. Meraki offers several licensing models—Subscription, Co-Termination and Per-Device Licensing—described in Cisco’s licensing FAQs. FortiGate proposals should state which security subscriptions and support services are included and their renewal basis.

Include migration and operating effort in the decision. Replacing an existing firewall can require policy translation, VPN changes, network reconfiguration, user communications and a rollback plan. A low equipment price may not represent the lowest cost if the move requires extensive rework or new skills. Ask for a written design and acceptance criteria.

Include migration and ownership in the decision

Inventory policies, public IP dependencies, authentication, VPN peers and logging before selecting a platform. Identify configuration that must be redesigned, then assign testing and rollback responsibilities.

Check who owns the customer accounts and who receives renewal notices. Ask how internal administrators retain access and how an outgoing service provider’s permissions will be removed.

Compare the support scope as carefully as the appliances. Vendor support, ongoing operations and an engineer attending the office are separate responsibilities that should appear in the agreed plan.

Illustration of Existing dependencies, Proposed platform, Assign ownership, using migration equipment and workflow composition

Simple selection checklist

  • Define whether the scope is a firewall, branch network or multi-site SD-WAN.
  • List the required security, VPN, WAN, wireless and reporting features.
  • Confirm the exact model, licence tier, subscriptions and support scope.
  • Compare performance under the intended security profile.
  • Review the team’s existing skills and the provider’s proposed operating model.
  • Include implementation, migration, testing, renewals and ongoing support in total cost.
  • Agree a documented design, acceptance tests and rollback approach.

There is no universal winner. If your priority is cloud-based central administration across a distributed Meraki estate, that may favour evaluating Meraki first. If your requirements are centred on a Fortinet security design or existing Fortinet operations, evaluate FortiGate closely. In either case, select only after checking the specific design and commercial terms.

How GlobalITN helps

GlobalITN has supported Singapore businesses since 2013, supplying and renewing Cisco Meraki and Fortinet licences and hardware, with our own engineers across Singapore, Hong Kong, Australia and Vietnam for survey, deployment and on-the-ground support. We can help scope either platform around your operating model and coordinate the survey, deployment and on-site acceptance work your design requires.

Explore our Cisco Meraki services and our FortiGate sizing guide, FortiGate project support, or send your requirements through our contact page.

Frequently asked questions

Is one platform always better for small offices?

No. Office size does not decide security requirements or operating capability. Test a complete design against the business needs.

Should we choose the same brand as our Wi-Fi?

Evaluate any management benefits, but also check security, interoperability and support. Existing Wi-Fi alone is not a complete firewall selection criterion.

Can we reuse the old firewall configuration?

Treat it as a requirements reference. Validate each rule and integration on the new platform rather than assuming direct compatibility.

What should a pilot prove?

Prioritise application access, security enforcement, VPN interoperability, circuit failure and troubleshooting. Include the administrator who will operate the network after handover.

Is Meraki easier to manage than FortiGate?

That depends on the team, design and existing skills. Meraki Dashboard provides cloud-based administration; FortiGate uses FortiOS and Fortinet’s management approach.

Which is more secure for a Singapore SME?

Neither brand is automatically more secure. Security depends on the selected model, licence or subscription, configuration, updates and operational practices.

Can Meraki and FortiGate be used together?

They can be part of the same wider network design in some environments, but routing, security boundaries, management ownership and support responsibilities should be documented.

What should I compare in vendor quotations?

Compare exact models, features, licences, subscriptions, performance assumptions, implementation, migration, support, renewal terms and ongoing management.