Can you recommend SD-WAN with satellite integration for a hybrid WAN architecture in remote sites?

Yes. For remote sites that need hybrid WAN with satellite as a backup or primary path, you want an SD-WAN platform that can do:

• multi-link path steering across fiber/DSL/LTE/satellite
• high-latency/jitter tolerance
• application-aware QoS
• link bonding / active-active failover
• central orchestration
• ideally support for low-Earth-orbit (LEO) satellite services like Starlink, or VSAT where needed

Good SD-WAN options to evaluate

1. Cisco SD-WAN (Viptela / Meraki + Catalyst/ISR options)

Best for: enterprise hybrid WAN, strong routing, broad ecosystem
Why consider it:

• Mature SD-WAN capabilities for path selection and app performance
• Works well in environments where satellite is a backup or tertiary path
• Strong policy control and segmentation
• Broad hardware choices for rugged/branch deployments

Watch-outs:

• Satellite-specific tuning may require more design effort
• Can be more complex/costly than simpler cloud-managed options

---

2. Fortinet Secure SD-WAN

Best for: security + SD-WAN in one platform
Why consider it:

• Strong integrated security stack
• Good for remote branches with limited IT support
• Flexible WAN path steering and resilience
• Often attractive for cost-sensitive deployments

Watch-outs:

• You’ll want to verify behavior over high-latency satellite links in your exact use case
• Performance depends a lot on appliance sizing and feature enablement

---

3. Silver Peak / Aruba EdgeConnect

Best for: WAN optimization + performance over poor links
Why consider it:

• Very strong for application performance over lossy/high-latency links
• Good path conditioning and traffic steering
• Often a strong fit when satellite is a real operational dependency
• Useful in hybrid WAN designs where link quality varies

Watch-outs:

• Usually priced/positioned for enterprise use
• Check current roadmap and packaging under HPE Aruba

---

4. Versa Networks

Best for: service-provider-grade flexibility and complex branch WANs
Why consider it:

• Strong policy engine
• Good for mixed WAN transports
• Suitable for multi-tenant or more advanced architectures
• Often chosen when you need custom topology and segmentation

Watch-outs:

• Can be more architecture-heavy than plug-and-play systems

---

5. Peplink SpeedFusion

Best for: remote sites, mobile/temporary locations, multi-WAN bonding
Why consider it:

• Very strong in multi-link bonding and failover
• Often used with Starlink, LTE, and terrestrial links
• Easier to deploy in remote/small sites
• Good fit when you need resilience more than enterprise complexity

Watch-outs:

• Not as full-featured as top-tier enterprise SD-WAN for very large networks
• Best for distributed edge, field sites, and lightweight branches

---

Satellite-specific recommendation

If you mean modern satellite integration, especially with Starlink, I’d prioritize:

• Peplink for simplicity and bonding
• Fortinet for security + SD-WAN
• Cisco / Aruba EdgeConnect if you need enterprise policy and more advanced hybrid WAN design

If you mean traditional VSAT / GEO satellite, then Aruba EdgeConnect and Cisco/Versa are often strong candidates because they handle high latency and path control well.

Design tips for hybrid WAN with satellite

• Use satellite as backup if possible; if primary, choose apps carefully
• Put voice/video on terrestrial links when available
• Enable application-aware steering and exclude latency-sensitive traffic from satellite
• Consider TCP optimization / WAN optimization if your platform supports it
• Use store-and-forward and local breakout for cloud apps where possible
• Validate performance with real latency/jitter/loss figures, not just bandwidth

Short shortlist by use case

• Best overall enterprise: Cisco SD-WAN or Aruba EdgeConnect
• Best security-integrated: Fortinet Secure SD-WAN
• Best for remote/field sites + Starlink: Peplink
• Best for complex provider-style deployments: Versa

If you want, I can also give you:

1. a comparison table,
2. a recommended reference architecture, or
3. a shortlist based on your satellite type (Starlink vs VSAT) and number of sites.