Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
An open-source API development workspace that runs in the browser: send REST requests, GraphQL queries, WebSocket, Server-Sent Events, Socket.IO and MQTT connections, organise them into collections and share them with a team. The self-hosted Community Edition is MIT-licensed; SAML single sign-on, OpenID Connect, audit logs and access controls belong to the paid Enterprise Edition.
Runs on a VPS from $12/mo (Kamatera 4GB, 4 GB RAM) · prices checked Sep 2026
Pick Hoppscotch when you want a browser-based API client that your team controls: REST, GraphQL, WebSocket, Server-Sent Events, Socket.IO and MQTT requests, collections and folders, environments, and shared team workspaces, with the data kept in your own PostgreSQL. The Community Edition is MIT-licensed and ships as a single all-in-one container (app, admin dashboard and NestJS backend) plus Postgres; the docs say one CPU core and 2 GB of RAM is enough to host it, and it idled at well under 0.5 GB on our test server. SAML single sign-on, OpenID Connect, audit logs and access controls such as domain whitelisting are Enterprise Edition features.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Hoppscotch Community Edition 2026.9.0 — the official all-in-one image plus PostgreSQL, with the migration step from the repo's compose file. Replace SERVER_IP with your server's IP or domain.
DB_PASS=$(openssl rand -hex 16)
cat > .env <<EOF
DATABASE_URL=postgresql://postgres:${DB_PASS}@hoppscotch-db:5432/hoppscotch
DATA_ENCRYPTION_KEY=$(openssl rand -hex 16)
WHITELISTED_ORIGINS=http://SERVER_IP:3170,http://SERVER_IP:3000,http://SERVER_IP:3100,app://localhost_3200,app://hoppscotch
VITE_BASE_URL=http://SERVER_IP:3000
VITE_SHORTCODE_BASE_URL=http://SERVER_IP:3000
VITE_ADMIN_URL=http://SERVER_IP:3100
VITE_BACKEND_GQL_URL=http://SERVER_IP:3170/graphql
VITE_BACKEND_WS_URL=ws://SERVER_IP:3170/graphql
VITE_BACKEND_API_URL=http://SERVER_IP:3170/v1
EOF
cat > docker-compose.yml <<EOF
services:
hoppscotch-db:
image: postgres:15
restart: unless-stopped
user: postgres
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: ${DB_PASS}
POSTGRES_DB: hoppscotch
volumes:
- pgdata:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres -d hoppscotch"]
interval: 5s
timeout: 5s
retries: 10
hoppscotch-migrate:
image: hoppscotch/hoppscotch:2026.9.0
env_file: .env
depends_on:
hoppscotch-db:
condition: service_healthy
command: sh -c "pnpm exec prisma migrate deploy"
hoppscotch-aio:
image: hoppscotch/hoppscotch:2026.9.0
restart: unless-stopped
env_file: .env
depends_on:
hoppscotch-migrate:
condition: service_completed_successfully
ports:
- "3000:3000"
- "3100:3100"
- "3170:3170"
volumes:
pgdata:
EOF
docker compose up -d
# the container restarts itself once on first boot (it populates its config table, then exits for a restart), so keep the restart policy; the first account to log in at http://SERVER_IP:3100 (admin dashboard) becomes the administrator; the app is at http://SERVER_IP:3000Hoppscotch's self-hosting docs flag these things to settle before a team relies on it: