Skip to main content

OctoLanding

A deliberately minimal, static-only Docker image

...designed to serve as a default landing page for infrastructure entry points.

It answers a simple question safely and intentionally:

"What should someone see when they land on this?"

Instead of exposing an application, redirecting to a random service, or leaking infrastructure details, octolanding serves a single static HTML landing page — nothing more.
What it is
  • A tiny BusyBox-based HTTP container
  • Static HTML & CSS only
  • No PHP, no CGI, no server-side scripting
  • No configuration required
  • Mountable document root for easy overrides
What it's for
  • Default IP landing pages
  • HAProxy / OPNsense fallback backends
  • Gateways and DMZ entry points
  • Infrastructure courtesy pages
  • Intentional "nothing lives here" endpoints
What it is not
  • A web application
  • A CMS
  • A framework
  • A general-purpose web server
OctoLanding is meant to be boring, predictable, and safe - built once, reused everywhere, and forgotten about until it's needed.

Default and Custom Deployment

Override with your own HTML

services:
  octolanding:
    image: octoleo/octolanding:latest
    container_name: octolanding
    ports:
      - "80:80"
    volumes:
      - ./www:/www:ro
    restart: unless-stopped
Default landing page
services:
  octolanding:
    image: octoleo/octolanding:latest
    container_name: octolanding
    ports:
      - "80:80"
    restart: unless-stopped

Unlimited Static Pages

Serve any number of plain HTML files without limitation.

Zero Configuration Required

Runs immediately with no setup or environment changes.

Full Content Override via Volume

Mounting a volume completely replaces the built-in landing page.

Safe Default Fallback

If no volume is mounted, the default landing page is served automatically.

Complete /www Replacement

Mounting /www fully overrides all bundled content.

Static-Only by Design

Serves HTML and assets only — no code execution, ever.

Boring. Predictable. Safe.