Skip to main content

Florete Technology

ReteLabs is developing a group of technologies collectively called Florete. It consists of the following main components:

  • Florenetes (f8s): A microservices application orchestrator similar to Kubernetes (k8s), but designed to operate on groups of autonomous agents rather than virtual machines in a data center
  • Florete Network: A post-IP network built on the principles of RINA (Recursive InterNetwork Architecture). Specifically, it implements the internal network for Florenetes called the Florete Service Mesh. It also enables inter-network communication between Florenetes instances. The public network of networks of this kind is called Nova Interrete ("New Internet")

Florenetes Architecture​

Florenetes is a distributed operating system for autonomous agents, built on a three-layer architecture. Each layer addresses specific challenges, enabling the entire system to function even under unstable connectivity and dynamic topology conditions.

Florenetes Architecture

Application Plane (Green)​

This is the layer where your applications run — from drone control systems to computer vision algorithms for robots. It includes:

  • Nodes: Physical devices like satellites, drones, robots, specialized equipment, as well as virtual machines in the cloud
  • Pods: The smallest deployable units of applications on nodes
  • CRI (Container Runtime Interface): A standard way to launch pods on nodes, compatible with Kubernetes
info

Florenetes specifics: a node can be either a single computing device or a "super-node" — a group of interconnected computers within a complex system (for example, multiple onboard computers in a single robot). For such cases, we're developing a specialized CRI implementation — the CRI-F runtime (CRI-Florenetes).

Data Plane (Purple)​

The heart of the system — the network infrastructure that enables communication between all components. This plane allows applications on different devices to communicate as if they were in the same data center, even when separated by thousands of kilometers and moving at high speeds.

At its core lies the post-IP Florete Network, synthesized from the following concepts:

info

A key advantage of Florete Network over classical IP networks is automatic adaptation to network topology changes and fast rerouting (tens of milliseconds instead of seconds) without disconnects.

Control Plane (Pink)​

This is the brain of the system, coordinating the work of all other components. It includes:

  • Path Computation Element (PCE): Calculates optimal routes and network topology
  • SPIFFE Server: Manages identity and authentication for all entities
  • Scheduler: Decides where to run applications
  • API Server: Provides a Kubernetes-compatible management interface
info

The main difference from Kubernetes: all control plane components are distributed across all cluster nodes, running as pods within the system itself. There are no dedicated master nodes — the system continues to function even when some devices are disconnected.

Current Implementation​

We're developing Florete in Rust for maximum performance and security. Currently under development are:

  • Flor: A component framework for Rust applications, the foundation of the entire system
  • Florete Forwarding: Data plane implementation
  • Florete Tunnel Daemon (ftunnel): Network daemon for nodes (analogous to ztunnel in Istio)
tip

All Florete components will be open-sourced on GitHub at https://github.com/rete-labs under the Apache 2.0 license in the near future. Technical details and developer documentation will be published on florete.tech.

Stay tuned for announcements on our blog and Telegram channel @rete_labs.

Next Steps​

Explore examples of Florenetes use cases for industrial robotics.

Florenetes is not an adaptation of cloud technologies, but a fundamentally new architecture created specifically for the world of mobile agents.