AppTelePorter.AI

Prerequisites

• Docker Engine installed and running on your Linux host.
• Your user must be in the docker group (or use sudo for docker commands).
• Port 3000 available on the host.
• Port 1514 available (optional — only if using the Device Beacon syslog receiver).

Edition Overview

AppTelePorter ships in two editions. This guide uses the Lite edition in all examples. To install the Max edition instead, replace appteleporter_lite with appteleporter_max in every command.

Step 1 — Pull the Docker Image

Open a terminal and pull the latest image:

docker pull networkevolution/appteleporter_lite:latest

docker pull networkevolution/appteleporter_lite:latest

Wait for the download to complete before proceeding.

Step 2 — Create the Data Directory

Create a directory on your host machine where AppTelePorter will store all persistent data — plugins, MCP servers, the encrypted vault, chat history, and configuration.

mkdir -p ~/appteleporter-data

mkdir -p ~/appteleporter-data

This directory is volume-mounted into the container. Your data persists across container restarts and upgrades — just pull the new image and re-run with the same volume path. The folder structure is auto-populated on first run.

Step 3 — Start the Container

Choose one of the two commands below based on whether you need the Device Beacon syslog receiver.

Port reference:

What is Device Beacon? A built-in add-on that listens on port 1514 for syslog messages (RFC 3164/5424), extracts device identity and status, and maintains a live device inventory in the UI. If you don’t need it, skip the 1514 port mapping. It can also be disabled at any time from Settings → Add-On Settings → Device Beacon.

Without Device Beacon

docker run -d --name appteleporter \
  -v ~/appteleporter-data:/app/backend/appteleporter-data \
  -p 3000:3000 \
  --restart unless-stopped \
  networkevolution/appteleporter_lite:latest

docker run -d --name appteleporter \
  -v ~/appteleporter-data:/app/backend/appteleporter-data \
  -p 3000:3000 \
  --restart unless-stopped \
  networkevolution/appteleporter_lite:latest

With Device Beacon (Syslog Receiver)

docker run -d --name appteleporter \
  -v ~/appteleporter-data:/app/backend/appteleporter-data \
  -p 3000:3000 \
  -p 1514:1514/tcp \
  -p 1514:1514/udp \
  --restart unless-stopped \
  networkevolution/appteleporter_lite:latest

docker run -d --name appteleporter \
  -v ~/appteleporter-data:/app/backend/appteleporter-data \
  -p 3000:3000 \
  -p 1514:1514/tcp \
  -p 1514:1514/udp \
  --restart unless-stopped \
  networkevolution/appteleporter_lite:latest

Verify the container is running:

docker ps -a

docker ps -a

You should see appteleporter in the list with status Up.

Step 4 — Open the UI and Complete First-Time Setup

Open your browser and go to:

http://localhost:3000

http://localhost:3000

Note: The standard container serves on HTTP. Custom SSL/HTTPS builds tailored to specific organisational requirements are available — contact appteleporter.ai for details.

Step 4a — Set the Vault Master Password

The first screen prompts you to create a vault master password. This password encrypts everything AppTelePorter stores:

• All device and API credentials (SSH usernames, passwords, API keys, host addresses)
• User accounts and access tokens
• LLM provider API keys and model settings
• Application session signing secrets

⚠️ This password cannot be recovered — ever. Store it somewhere safe.

AppTelePorter never stores your master password on disk or in a database. Your password is processed through Argon2id (a memory-hard key derivation function) to produce a 256-bit encryption key, which encrypts the entire vault as a single AES-encrypted blob. The key is then discarded. Only a bcrypt hash is kept for unlock-time verification.

There is no password reset, no recovery email, and no backdoor. If you lose it, all stored credentials and accounts must be recreated from scratch.

Enter a strong master password and confirm it to proceed.

Step 4b — Create the First Admin User

After setting the vault password, you are prompted to create the first admin user — the account you’ll use to log in to the AppTelePorter interface.

Set a username and a strong password. Additional users can be added later from Settings → Users.

Step 4c — Configure Your LLM Provider (Lite Edition Only)

Max edition users: Skip this step. The Max edition includes a bundled local model and is ready to use immediately after login.

For the Lite edition, the AI cannot process any requests until you connect it to an LLM provider. Navigate to:

Settings → LLM Settings

Select your preferred provider and enter the corresponding API key:

Click Test Connection to verify the key is working. Once confirmed, AppTelePorter is ready to use.

Need support for a provider not listed? Contact info@networkevolution.in — it will be treated as a feature enhancement request.

You’re Ready

AppTelePorter is now running. You can start building your own tools using Tool Studio or use the existing tools from ecosystem

Your network. Your AI. Your data. Built by Network Evolution