About a-team Marketing Services
The knowledge platform for the financial technology industry
The knowledge platform for the financial technology industry

A-Team Insight Blogs

Metamako Adds MetaProtect Firewall to Portfolio of FPGA Network Appliances

Subscribe to our newsletter

Metamako has extended its portfolio of field programmable gate array (FPGA) enabled network solutions with MetaProtect Firewall, a network appliance designed to deliver ultra-fast firewall protection and solve problems including situations where a firewall is mandatory but ultra-low latency and high port density are also required.

The firewall solution takes Metamako into the security space for the first time and builds on its growth plans including the company’s recent and inaugural acquisition of Chicago-based xCelor’s hardware business.

MetaProtect is a 48-port (x10GbE) network appliance that performs packet filtering in 130 nanoseconds, as well as comprehensive logging for the filters. It is flexible in how it can be configured, including the ability to specify ports that don’t need to be filtered, in which case packets are passed through in 5 nanoseconds.

Dave Snowdon, founder and chief technology officer at Metamako, says: “Clients have seen the benefits of using our low-latency devices and asked if we could improve their firewall architecture. We were able to draw on our flexible FPGA platforms and app infrastructure to very quickly build the right product for those customers and the result is MetaProtect – a low latency firewall.”

Considering situations that mandate a firewall, Snowdon suggests exchanges in Asia, for example the Korean Stock Exchange (KRX), which stipulate that a broker must ‘own and manage’ a firewall between a client’s trading servers and the exchange. The latency penalty that this introduces is a problem for trading participants, but it can be eased using Metamako’s ultra-low latency, high-density firewall solution to improve exchange-facing architecture.

Key functionality of MetaProtect includes: ultra-low latency filtering with average latency of 130 nanoseconds (1 rule) to 155 nanoseconds (510 rules); extreme determinism, a tightly bound maximum latency for each configuration; up to 510 rules per port; extensive packet statistics for all ports for advanced network monitoring; and comprehensive logging, including logged statistics of permitted and denied packets.

Subscribe to our newsletter

Related content

WEBINAR

Recorded Webinar: How to move to a modern, component based trading architecture using a Buy AND Build approach

To remain competitive in today’s electronic markets, firms need trading architectures that support rapid innovation, effortless integration of new capabilities, and the agility to respond to shifting market demands. This is prompting technology leaders to move beyond the traditional “Buy vs. Build” debate, a false dichotomy that oversimplifies the choice between generic, off-the-shelf platforms and...

BLOG

The Matching Engine Was Never the Hard Part: What 24/7 Really Demands of Exchange Architecture

The framing has become familiar. Digital asset exchanges, prediction markets and retail-driven platforms have normalised continuous trading. Traditional venues, with their nightly batch cycles and weekly maintenance windows, are now playing catch-up as they extend hours, tokenise assets and reach for new distribution models. The conventional answer is to point at the matching engine and...

EVENT

Eagle Alpha Alternative Data Conference, Spring, New York, hosted by A-Team Group

Now in its 9th year, the Eagle Alpha Alternative Data Conference managed by A-Team Group, is the premier content forum and networking event for investment firms and hedge funds.

GUIDE

Enterprise Data Management, 2009 Edition

This year has truly been a year of change for the data management community. Regulators and industry participants alike have been keenly focused on the importance of data with regards to compliance and risk management considerations. The UK Financial Services Authority’s fining of Barclays for transaction reporting failures as a result of inconsistent underlying reference...