Clearnet
Visitor browser
DNS
HTTPS ingress
Web server
AMPG clearnet output
Best when a public domain and inbound web reachability are available.
Adaptive Multi-Protocol Gateway
AMPGateway
One site source, many transport outputs, one staged deploy spine from package install to published health checks.
publish over clearnet without losing the map.
Topology
A VPS can publish clearnet, Tor, I2P, Gemini, and Reticulum outputs from one AMPG plan.
Topology theatre
The animated maps, unobstructed.
The same live topology views from the hero are given a full clean stage here, so the moving routes, nodes, and deployment shapes can be read directly.
View
A VPS can publish clearnet, Tor, I2P, Gemini, and Reticulum outputs from one AMPG plan.
Protocol maps
How traffic moves on each transport.
These are the big maps: what the client talks to, where AMPG output sits, and which network pieces carry the request.
Tor onion
Tor Browser
Tor circuits
Onion service
Local HTTP
AMPG privacy HTML
The public address is the onion name; the origin can stay behind local loopback.
I2P tunnel
I2P browser
b32 destination
I2P tunnels
i2pd server tunnel
AMPG privacy HTML
The b32 address points at the I2P destination, not a normal DNS hostname.
Gemini
Gemini client
TLS capsule
Gemini daemon
Gemtext tree
AMPG text render
Small pages, simple links, and text-first structure make the capsule readable.
Reticulum
RNS client
Reticulum mesh
Destination hash
NomadNet node
AMPG Micron output
Identity is destination-based, and content should stay compact by default.
Single transport
Source site
AMPG selection
One renderer
One daemon
One published route
Useful for Tor-only, I2P-only, Gemini-only, or Reticulum-focused sites.
Network topologies
Deploy from a clean VPS, a laptop behind a router, or an old phone.
Full VPS
ampgateway.site is the target for a full public example with
clearnet, Tor, I2P, Gemini, and Reticulum routes managed from one deploy plan.
Behind router
ampgateway.website is the target for a home or lab deployment
that shows Dynamic DNS, router constraints, and transports that avoid
inbound ports.
Mobile server
Android and Termux can run user-space daemons for small static sites, demos, and transport experiments on hardware that would otherwise sit idle.
Single transport
AMPG can deploy only Tor, only I2P, only Gemini, or a selected subset when the operator wants a narrow surface.
Example domains
Three public names, three jobs.
Visual hub
ampgateway.online
Public explanation site with interactive topology views, deployment flow, and links into the clean docs.
ampgateway.onlineVPS example
ampgateway.site
Planned all-transport reference deployment on a normal server, useful for showing the complete package, state, supervisor, start, address, and health path.
ampgateway.siteBehind-router example
ampgateway.website
Planned home-network reference deployment for Dynamic DNS, port-forwarding choices, and transports that do not need clearnet inbound reachability.
ampgateway.websiteDeploy spine
Narrow stages, visible state, reversible thinking.
- Build
Generate clearnet, privacy HTML, Gemtext, and other selected outputs.
- Packages
Install selected daemon packages with allowlisted platform commands.
- State
Copy approved generated config into AMPG-owned state.
- Supervisor
Install AMPG-named service files after config exists.
- Start
Start AMPG-owned services with structured platform commands.
- Addresses
Capture daemon-written onion, I2P, or other public identities.
- Health
Verify published fixture URLs through the selected transport profiles.
Public docs
The visual site stays tied to the public spec.
The source for this page lives in the AMPG repository and can be rendered by AMPG like any other static site. The Markdown docs stay concise; this site turns the same concepts into topology-first views.