Seven layers of network. Levelrail runs three.

The mark has three rails. A network has seven layers. We own layer 7 and layer 3, and part of layer 4. Below is exactly where that stops.

In plain words: a request to your app passes through these layers, top to bottom. We run the top and the middle, and we say clearly where our part ends.

  1. L7 Application Levelrail Ingress, TLS, HTTP balancing, firewall
  2. L6 Presentation Yours Encodings and compression, inside your app
  3. L5 Session Yours User sessions, inside your app
  4. L4 Transport Partly Agent link (mTLS), host firewall (ufw). No TCP balancing yet
  5. L3 Network Levelrail WireGuard mesh (beta), private networks, mesh DNS
  6. L2 Data link Yours Switches and VLANs, your host or provider
  7. L1 Physical Yours Cards, cables, power, your hardware
  • Levelrail
  • Partly
  • Yours

L7 ApplicationLevelrail

Every request meets Caddy first.

Ingress is built into the control plane, so there is no separate proxy to run and nothing for config to drift from. It is the layer most of your users actually touch.

In plain words: when someone opens your site, Levelrail answers first, adds the padlock, and hands the visit to a healthy copy of your app.

The load balancer page for an app: clients reach a round robin proxy that splits traffic between two healthy replicas, with latency, connections and a per upstream status table. The load balancer page for an app: clients reach a round robin proxy that splits traffic between two healthy replicas, with latency, connections and a per upstream status table.
  1. Client
  2. Firewall rules
  3. Caddy and TLS
  4. Balancer
  5. Replica
  • TLS and certificates

    Certificates through the embedded Caddy. TLS defaults to an internal issuer; the public Let’s Encrypt issuer has had one live verification run, and renewal is not yet exercised live.

    Read the docs
  • Domain routing

    Point DNS at the server, add the domain to an app, and routing follows desired state. No proxy container, no config to drift.

    Read the docs
  • HTTP load balancing

    More than one replica is balanced round robin by default, with health checks, retries and sticky sessions. Experimental.

    Read the docs
  • Request firewall

    Ordered rules, IP lists, automatic temporary bans, a browser challenge and bot handling, with a live view of what was blocked.

    Read the docs

L4 TransportPartly

Layer 4 is half built, and we show the half that is missing.

In plain words: your servers phone home over a locked, outbound-only line. We can also lock down the main server's ports. Balancing raw TCP traffic is the part we have not built.

levelrail-cli
levelrail-cli firewall statuslevelrail-cli firewall enable --dry-run# prints the commands, changes nothinglevelrail-cli firewall enable

The dashboard has the same switch under Settings, Firewall. Turning it on allows SSH first.

Your server
Your server: any machine running Docker. It calls out to Levelrail, so nobody needs to open a port to it.
Levelrail server
Levelrail server: the control plane. It answers calls from your servers and never dials in.
TCP load balancingHTTP only today Not built
Host firewall opt-in, ufw
  • Agent link

    Each node opens one outbound mutual TLS connection to the control plane. No inbound ports on managed servers.

  • Host firewall

    Opt-in. Manages ports on the control plane host through ufw, with a lockout guard that refuses to close ports it needs. It only touches rules it tagged.

  • TCP load balancing Not built

    Not built. Balancing today is HTTP only, at layer 7. A raw TCP service gets no balancer from us yet.

L3 NetworkLevelrail

One private network across your machines.

A home server, a cheap VPS and a cloud VM can sit on one mesh with stable names. It is the part of the stack that is still earning trust, so each line below says what it is not.

In plain words: your machines can talk to each other as if they shared one office network, even when they are in different places.

mesh dns
# each app gets a mesh nameedge-cache.<zone>        10.181.0.1marketing-site.<zone>    10.181.0.1docs-sample-db.<zone>    10.181.0.1

WireGuard meshBeta

Home server marketing-site.zone
Home server: a spare PC or mini server at home. It joins the mesh and gets a private address.
VPS edge-cache.zone
VPS: a rented server on the internet. Apps on it reach the others by name, not by public address.
Cloud VM docs-sample-db.zone
Cloud VM: a virtual machine at any cloud. Traffic between machines is encrypted with WireGuard.
  • WireGuard mesh Beta

    Nodes get a mesh address and peer config. Single node is the well-tested path; the mesh is not battle-tested yet.

    Read the docs
  • Private networks

    Name which apps may talk to which. Same node, this is a Docker network per rule. Across nodes it gates name resolution, not packets.

    Read the docs
  • Mesh DNS

    Apps get stable names that resolve across machines, like the names above. Direct IP access over the mesh is not filtered.

    Read the docs

L6 L5 L2 L1Yours

What stays yours.

Four layers sit inside your app or beneath your server. We do not touch them, and we will not pretend to.

  • L6 Presentation

    Encodings and compression happen inside your app. Nothing to set here.

  • L5 Session

    User sessions belong to your app. Sticky routing is the only touch.

  • L2 Data link

    Switches, VLANs and MAC addressing. Your host or your provider.

  • L1 Physical

    Cards, cables and power. Your hardware, or your VPS provider.