View
Deployment shape
VPS, router, phone, and browser validation views show where AMPG sits in the stack.
A VPS can publish clearnet, Tor, I2P, Gemini, and Reticulum outputs from one AMPG plan.
Adaptive Multi-Protocol Gateway
One site source, many transport outputs, one staged deploy spine from package install to published health checks.
publish over clearnet without losing the map.
A VPS can publish clearnet, Tor, I2P, Gemini, and Reticulum outputs from one AMPG plan.
Topology Theater
Deployment maps and protocol maps share one visual language: moving routes, clear nodes, and transport-specific paths.
View
VPS, router, phone, and browser validation views show where AMPG sits in the stack.
A VPS can publish clearnet, Tor, I2P, Gemini, and Reticulum outputs from one AMPG plan.
Transport
Each transport gets its own animated path instead of a static comparison table.
Clearnet requests resolve DNS, reach HTTPS ingress, and read AMPG clearnet output.
Network topologies
ampgateway.site is the target for a full public example with
clearnet, Tor, I2P, Gemini, and Reticulum routes managed from one deploy plan.
ampgateway.website is the target for a home or lab deployment
that shows Dynamic DNS, router constraints, and transports that avoid
inbound ports.
Android and Termux can run user-space daemons for small static sites, demos, and transport experiments on hardware that would otherwise sit idle.
AMPG can deploy only Tor, only I2P, only Gemini, or a selected subset when the operator wants a narrow surface.
Example domains
Visual hub
Public explanation site with interactive topology views, deployment flow, and links into the clean docs.
ampgateway.onlineVPS example
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
Planned home-network reference deployment for Dynamic DNS, port-forwarding choices, and transports that do not need clearnet inbound reachability.
ampgateway.websiteDeploy spine
Generate clearnet, privacy HTML, Gemtext, and other selected outputs.
Install selected daemon packages with allowlisted platform commands.
Copy approved generated config into AMPG-owned state.
Install AMPG-named service files after config exists.
Start AMPG-owned services with structured platform commands.
Capture daemon-written onion, I2P, or other public identities.
Verify published fixture URLs through the selected transport profiles.
Public docs
AMPG publishes clean public docs, generated references, and website sources in GitHub repositories. Private planning and deployment notes stay outside the public docs tree.