Infrastructure Overview

ByteBite runs as containerized applications on dedicated Hetzner hardware under Proxmox. Staging is active on BYTEBITE-APP-01. Production application infrastructure is not deployed — although production DNS records already point at the edge IP.

This section is the operational source of truth for hosting, networking, TLS, deployment, and day-two operations. Application tenancy behavior is documented in Tenancy & storefront; this section focuses on the platform that runs it.

Environment status

Documentation labels facts as Verified, Configured, Planned, or Unknown where the distinction matters. See Environments for a full comparison.

High-level topology

Internet
  -> Cloudflare DNS (DNS-only, not proxied)
    -> edge.getbytebite.co (88.99.0.118)
      -> BYTEBITE-APP-01
        -> dokploy-traefik (Traefik v3.6.7, ports 80/443)
          -> Dokploy-managed routing + compose.deploy.yml Traefik labels
            -> api | storefront | dashboard | docs (Docker)
            -> Dokploy managed PostgreSQL (internal only)

Mail is planned on a separate VM (BYTEBITE-MAIL-01, 88.99.0.97). See Mail.

Component inventory

Domain inventory (staging)

All staging application records are DNS-only (grey cloud) in Cloudflare and resolve through edge.getbytebite.co → 88.99.0.118.

Wildcard DNS does not imply a tenant exists — tenant identity comes from the restaurant_domains table. See DNS and Architecture.

What is intentionally absent

Current architecture does not include Redis, BullMQ, Kubernetes, GraphQL, or microservice decomposition. These are non-goals for the current platform, not future promises.

Start here