Skip to content
+1 (813) 330-0469 support@layeronecloud.com
Products / Cloud Firewall

One managed edge for your whole network.

A Cloud Firewall sits in front of a private network and does five jobs in one box: a stateful firewall, a NAT gateway, DHCP, a load balancer with free HTTPS, and a VPN. It holds one public IP; everything behind it stays private and reaches the internet through it. From $0.0136/hr, billed from account credit.

One public IP Stateful firewall Billed hourly
  • Stateful firewall
  • NAT and port forwards
  • DHCP and DNS
  • Load balancer with HTTPS
  • WireGuard and Tailscale VPN
One box, five jobs

Everything your network edge needs.

Put a Cloud Firewall in front of a private network and you have a single gateway for the whole thing. It serves LayerOne applications, managed databases, and your own servers and VMs alike. Nothing behind it needs a public address of its own.

Stateful firewall

Ordered allow and block rules between the internet, your private network, and the VPN. Outbound is allowed and inbound is blocked by default, so you open only what you mean to. Reorder rules, match on protocol, port and CIDR, and reuse named address objects.

NAT gateway

Outbound masquerade gives every workload internet access with no public address of its own. Add inbound port forwards to send a port on the public address to a specific host and port inside the network.

DHCP and DNS

Hand out addresses, gateway and DNS on the network from a pool you set, with fixed reservations for the devices that need them. Run a resolver on the firewall with your own records and split-horizon forwarding.

Load balancer with HTTPS

Publish a service on a domain and the firewall issues a free Let's Encrypt certificate for it automatically. Built on Traefik, it routes to one or more backends on the network and spreads traffic across them.

VPN into the network

Reach private workloads from your own devices over WireGuard, with a ready-to-use config per device, or join the firewall to your Tailscale tailnet and advertise its networks as subnet routes. No workload has to face the internet.

Logging to your SIEM

Forward the firewall's own record, SSH logins, system messages, and dropped-packet events, to an external syslog collector over UDP or TCP, so a SIEM or a compliance archive keeps its logs.

A Cloud Firewall is a routed gateway in front of a whole network, not the per-server Firewall tab on a single VPS. You can run both. Reach for a Cloud Firewall when you want one address and one gateway for a group of private workloads.

How it works

Attach a network, provision, and you have an edge.

A Cloud Firewall serves a private network, so you point it at one and bring it online. There is no size to pick up front and no address to allocate; the firewall takes its own public IP when it provisions.

1. Create and attach

Name the firewall and attach one of your private networks. Its address on that network becomes the gateway it serves to everything else there. One firewall can serve up to four networks.

2. Provision

Provision it and LayerOne builds the guest, assigns its public IPv4 address, and applies your configuration. The page updates as it goes, from provisioning to running.

3. Open what you need

Add firewall rules, port forwards, DHCP, load-balancer routes and VPN access from the portal. Every change is pushed to the running firewall for you.

Throughput tiers

Size it to your traffic.

A Cloud Firewall runs at one of three tiers, each capping the public link at a higher rate with more vCPU and memory behind it. Move between tiers at any time; the change applies as the firewall reprovisions, with a brief restart.

Cloud Firewall
Standard

2.5 Gbit/s public throughput

$ 0.0136 /hr
About $10.00/mo at 730 hours, billed from account credit
  • 2.5 Gbit/s public link
  • 1 vCPU
  • 2 GB RAM
  • 1 public IPv4
  • Firewall, NAT, DHCP, LB, VPN
Create Standard
Cloud Firewall
Max

10 Gbit/s public throughput

$ 0.0547 /hr
About $40.00/mo at 730 hours, billed from account credit
  • 10 Gbit/s public link
  • 4 vCPU
  • 16 GB RAM
  • 1 public IPv4
  • Firewall, NAT, DHCP, LB, VPN
Create Max

Billing is metered by the hour from account credit and starts only when the firewall comes online. The public IPv4 address it holds is billed separately, the same as any other dedicated address.

One address, one gateway

Private by default.
Published on purpose.

Everything behind a Cloud Firewall stays private. Workloads reach the internet through its NAT, and the internet reaches them only through a port forward or a load-balancer route you add. One public address, protected by LayerOne's always-on L3/L4 DDoS mitigation.

01 / Consolidate

One edge for many workloads

Trade a public IP and a firewall on every server for a single gateway in front of the network. Applications, databases and your own VMs share one address and one rule set.

02 / Publish

Ship a service on a domain

Point a domain at the firewall, add a route, and it terminates HTTPS with a free certificate and load-balances to your backends. No reverse proxy to run yourself.

03 / Reach in

Private access for your team

Bring up a WireGuard or Tailscale VPN and reach databases and admin panels over the tunnel, with nothing exposed to the internet to do it.

Questions

Straight answers.

Full documentation

What is a LayerOne Cloud Firewall?

A managed guest that sits at the edge of one of your private networks and does five jobs in one box: a stateful firewall, a NAT gateway, a DHCP server, a load balancer with free HTTPS, and a VPN gateway over WireGuard or Tailscale. It holds one public IPv4 address, and everything behind it stays private.

How is it different from a server's own firewall?

A server's Firewall tab filters traffic at that one server's network card. A Cloud Firewall is a separate routed gateway in front of a whole private network, so one address and one rule set serve every workload behind it. You can run both; reach for a Cloud Firewall when you want a single edge for a group of private workloads rather than a rule set bolted to each one.

What sits behind a Cloud Firewall?

Anything on the private network it serves: a LayerOne application, a managed database, or one of your own servers or VMs. They reach the internet through its NAT with no public address of their own, and are reached from the internet only through its port forwards or its load balancer. One firewall can serve up to four private networks.

How do I manage it?

Entirely from your client portal. Every rule, route, address, DHCP scope and VPN device is set on the firewall's pages, and LayerOne applies the change to the running guest for you. A firewall cannot lock you out of its own management, because you configure it out of band from the portal.

How is a Cloud Firewall sized?

By throughput tier. Standard, Pro and Max cap the firewall's public link at 2.5, 5 and 10 Gbit/s and give it more vCPU and memory as you go up. You can move between tiers at any time; the change applies as the firewall reprovisions, with a brief restart.

How is it billed?

By the hour, drawn from your prepaid account credit, from the first time it comes online until you delete it. The hourly rate follows the tier you choose and is shown in your client area; the public IPv4 address it holds is billed separately, the same as any other dedicated address. A stopped firewall still bills while it keeps its guest and its address.

Does it issue HTTPS certificates?

Yes. The load balancer publishes a service on a domain and issues a free Let's Encrypt certificate for it automatically, once the domain's DNS points at the firewall's public address. It is built on Traefik and can spread traffic across more than one backend on the private network.

Can I reach the private network from my own devices?

Yes, over the firewall's VPN. Turn on WireGuard and download a ready-to-use config per device, or connect the firewall to your existing Tailscale tailnet and let it advertise your private networks as subnet routes. Either way you reach private workloads without exposing them to the internet.

Cloud Firewall

Give your network one managed edge.

Firewall, NAT, DHCP, a load balancer with HTTPS, and a VPN, in one gateway you manage from your client portal. One public IP, everything behind it private, billed by the hour from account credit.