Edge As a Service

Izuma Networks lets you deploy applications to the Edge in minutes.

Edge computing allows us to move applications closer to the actual event.

That results in faster more real-time information with less network utilization.

  •  Better scalability
  •  Improved solution redundancy
  •  Less application latency/lag
  •  Less bandwidth usage/cost

Edge computing is generally defined as computing, the hardware, applications and networking, taking place close to an end-user or event. In short, organizations across the world are using edge computing to:

  • process data at greater scale with less cost
  • process data faster
  • make real-time decisions
  • unify the physical world with the digital one
  • meet different types of regulatory compliance

Gartner predicts that by 2025 at least 50% of enterprise-related data will come from and/or be processed at the edge.

With these known advantages at hand, building an edge strategy to solve problems is probably a good idea. But as all teams find, developing and deploying edge applications can become a significant project. At Izuma Networks we have worked hard to develop an edge solution that fits into modern IT and DevOps team’s workflows, and which does not lock customers into proprietary standards.

An Edge Service Offering: Standards-based, very few proprietary APIs

Izuma Networks provides a turn-key solution for deploying applications at the edge. Our Edge-as-a-Service (EaaS) offering allows development teams to immediately focus on developing the business logic of important applications that will live at the edge. Our offering is based on Kubernetes (k8s), the industry standard way of orchestrating application containers. When using our services to deploy apps at the edge, teams simply use normal k8s APIs. This means a huge amount of tools and existing knowledge can be leveraged.

Izuma’s Network’s Edge as a Service (EaaS) in a nutshell.

  •  Deploy containerized applications
  •  Hyperscaler independent: Deploy on your platform of choice.
  •  Robust systems management
  •  Root of Trust security
  •  Open source Apache 2.0 runtime
  •  x86 or Arm
  •  Runs on almost any Linux variation

Chances are your edge strategy involves:

  • Various locations
  • A myriad of different hardware types
  • A strong focus on security

Additionally “edge” may mean running applications on:

  • One or more servers at remote locations
  • On smaller hardware such as “gateway class” machines or even machines as small as a Raspberry Pi
  • Dispersed instances with a hyperscaler in various geographies or availability zones.

All of these things can constitute edge, and in all cases Izuma Networks can greatly simplify deployments.

Kubernetes for Edge: Run containers on any Linux machine, managed as a single cluster.

Tiny Linux gatway hardware. Edge servers. Micro data centers. Remote hyperscaler instances.

Izuma Networks takes care of the time-consuming and DevOps heavy task of maintaining and running Kubernetes, and the difficult engineering of making Kubernetes run at the edge, while greatly improving security and manageability.

How it works:

  • Izuma Networks spins up a private instance of Izuma Cloud for you team.
  • Izuma Cloud is a NoOps solution. So we manage the DevOps of the cluster itself. We also offer a co-DevOps solution and an on-premise solution for isolated networks or special deployments.
  • Izuma Cloud provides a full Kubernetes cluster which will scale as needed.
  • Izuma Edge, a Linux runtime stack, can be installed on most versions of Linux in minutes.
  • Once installed, any Izuma Edge machine becomes a k8s node in the Izuma Cloud instance.

Izuma Cloud allows you to manage a single Kubernetes cluster, globally, across WANs / Firewalls / WAFs with k8s nodes being on even the smallest Linux hardware.

How We Built It

We built Izuma Edge based on real-world needs from multi-national organizations that deploy applications across the world in thousands of locations. We focused on:

  • Very strong security at the Edge, with a Zero Trust design at each node.
  • Highly durable connectivity for each node. Each node’s connectivity must handle: strict firewall, NAT and WAF implementations, low bandwidth, moderately unreliable networks
  • The ability to handle frequent periods of disconnectivity with aplomb: power outages, staff just unplugging it, etc.
  • A standard k8s design where DevOps teams familiar with Docker containers and k8s could immediately use the product and take their best practices with them to our platform.

To meet these goals Izuma Cloud and Izuma Edge are built on these core pieces of technology:

The Edge: Single Cluster vs Multi-Cloud

Most solutions on the market for Kubernetes at the Edge, or Edge-as-a-Service, focus on utilizing tools in what is called “Multi-cloud.”

These solutions involve spinning up an entire k8s cluster at each edge location. Customers then use a proprietary “multi-cloud” toolset, which Gartner has recently termed as Multicloud Networking Software (MCNS), to manage multiple k8s clusters. Some of these deployments may be traditional k8s clusters at a hyperscaler, and others may be the “edge clusters.” The “edge clusters” are variations of mainline Kubernetes, a popular example being k3s. While these solutions can work well, depending on your deployment needs, bear in mind - every time you create a new cluster you increase management complexity and increase risk by expanding the surface area hackers can attack.

And we aren’t the only ones saying “multi-cloud” adds complexity.

“The huge cost and complexity of a multicloud implementation is effectively a negative distraction from what you should actually be doing that would improve your uptime and reduce your risks…"
- Lydia Leong, Gartner
TechRepublic, Oct ‘21

Izuma Networks takes a different approach. With over a decade’s worth of patented security and systems technology, we have developed a standards-based k8s cluster that allows deploying applications across the Internet while still having the ease of manageability of a single Kubernetes cluster.

It’s still possible and sometimes desirable to have multiple k8s clusters. In this case - by using Izuma Cloud you can instead break clusters up by the purposes they serve or the groups which have operational responsibility - which is a more security-centric way of organization (as an example, look at our MDC use-case). Clusters are not confined to a specific location/data center or a managed WAN. Nor do DevOps teams need to be concerned with special networking needs or third party SD-WAN systems for remote nodes. All Izuma Edge nodes in the Izuma Cloud cluster talk back to the cluster’s control plane and other nodes over HTTPS using two-way TLS (mTLS). Additional systems management features are part of Izuma Edge, easing DevOps team’s deployments more.

The Increased Importance of Edge Security

Along with the growth of edge comes the risk of increased attack surfaces for malicious actors. It’s imperative to have a security-by-design solution when deploying edge applications. Izuma Edge builds on years of experience and development of the Izuma Cloud product.

Read more about our Edge security model.