Skip to main content

​
Self-hosted

The Argyros community binary lets you run the full routing engine on your own server. It exposes the same API as the hosted instance — same endpoints, same response shapes — with no shared infrastructure.
Hosted API vs self-hosted. Use the hosted API for managed infrastructure with no ops overhead. Choose self-hosted if you need full control, want to avoid third-party rate limits, or are building systems that can’t depend on an external service.

​
Hosted vs self-hosted

Hosted APISelf-Hosted
AuthAPI key (per plan)Community license key
Rate limitsGateway-enforced per planBuilt into the binary, per license
InfrastructureManaged by ArgyrosYour server
RPC providerManaged by ArgyrosFluxRPC (your key)
CostSubscriptionRPC fees only
SLACoveredYour responsibility

​
Requirements

RequirementWhere to get it
FluxRPC keyfluxrpc.com
Community license keylicense.argyros.xyz
Linux server (amd64 or arm64)Any VPS or bare metal
The binary validates both at startup and refuses to start if either is missing or invalid.

​
Quickstart

1

Copy the env file

curl -O https://raw.githubusercontent.com/argyros-ag/argyros-community/main/.env.example
cp .env.example .env
2

Fill in your credentials

Open .env and set:
RPC_URL=https://eu.fogo.fluxrpc.com?key=YOUR_FLUX_RPC_KEY
YELLOWSTONE_TOKEN=YOUR_FLUX_RPC_KEY
COMMUNITY_LICENSE_KEY=argycom_xxxxxxxxxxxxxxxxxxxx
COMMUNITY_LICENSE_API=https://license.argyros.xyz
3

Run

curl -O https://raw.githubusercontent.com/argyros-ag/argyros-community/main/docker-compose.yml
docker compose up -d
curl http://localhost:8080/health
# → {"status":"ok"}

Full deployment guide

Nginx, SSL, systemd, referral fees, and the complete configuration reference.

argyros-community on GitHub

Docker images, binary releases, and the .env.example reference.
Last modified on June 30, 2026