HubFly Architecture: A Deep Dive

A deep technical breakdown of how HubFly works, the architecture behind it, and what makes it fast, reliable, and unique.


Introduction

HubFly was built with a singular objective: to deliver a modern, reliable, and developer centric hosting platform capable of handling substantial workloads with speed and precision.

High Level Architecture

HubFly operates as a distributed system of specialized services. Click on the nodes below to explore each component.

Select a component to view details


Core Components

HubLock Storage

HubLock serves as the foundational storage backbone. It provides a Virtual File System optimized for speed and reliability, with encryption both at rest and in transit.

Virtual File SystemEncryptedShared

HubFly-Storage

An open-source component built in Go to handle dynamic Docker volume creation. Features dynamic sizing, auto-cleanup, and usage statistics.

GoDynamic Volumes

HubFly-Builder

Ingests build jobs and processes them using BuildKit. Auto-detects project types and generates Dockerfiles if missing.

BuildKitAuto-Detection

Reverse Proxy

A lightweight routing layer built on NGINX and Certbot, wrapped with a custom Go REST API. Handles zero-config SSL and protocol support.

NGINXZero-Config SSL

System Integration

Each project is assigned a dedicated isolated Private network.

  • Containers within the network communicate freely.
  • The Proxy Manager controls ingress.
  • This mimics a Virtual Private Cloud (VPC) environment for maximum security.

For more details on our architecture and engineering decisions, check out our Technical Blog.