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 Theater

Animated maps.

Deployment maps and protocol maps share one visual language: moving routes, clear nodes, and transport-specific paths.

View

Deployment shape

VPS, router, phone, and browser validation views show where AMPG sits in the stack.

View

A VPS shape starts with one source tree, renders transport outputs, then hands them to service-specific daemons on the host.

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.

VPS 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.site

Behind-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.website

Deploy spine

Narrow stages, visible state, reversible thinking.

  1. Build

    Generate clearnet, privacy HTML, Gemtext, and other selected outputs.

  2. Packages

    Install selected daemon packages with allowlisted platform commands.

  3. State

    Copy approved generated config into AMPG-owned state.

  4. Supervisor

    Install AMPG-named service files after config exists.

  5. Start

    Start AMPG-owned services with structured platform commands.

  6. Addresses

    Capture daemon-written onion, I2P, or other public identities.

  7. Health

    Verify published fixture URLs through the selected transport profiles.

Public docs

Source, docs, and websites stay public and reproducible.

AMPG publishes clean public docs, generated references, and website sources in GitHub repositories. Private planning and deployment notes stay outside the public docs tree.