Applications
| Name | Port | Container | Status | Database | Domain | Modified |
|---|---|---|---|---|---|---|
| zerolink | 3001 | zerolink-3001 | healthy | postgresql | — | 3/23/2026 |
| aux-voice-assistant | 3002 | aux-voice-assistant | healthy | postgresql | — | 3/23/2026 |
| zerocore | 3003 | zerocore-3003 | healthy | postgresql | — | 3/23/2026 |
| zeroflow | 3004 | zeroflow-official | healthy | — | — | 2/27/2026 |
| autogen-studio | 3005 | autogen-studio-3005 | healthy | — | — | 1/19/2026 |
| gmaps-scraper | 3006 | gmaps-scraper-3006 | healthy | — | — | 3/23/2026 |
| zeroui-plane | 3007 | plane-proxy-1 | healthy | postgresql | plane.zeroshot.studio | 4/24/2026 |
| zerovps-dashboard | 3008 | zerovps-dashboard-3008 | healthy | — | ops.zeroshot.studio | 2/28/2026 |
| zerolabs | 3009 | zerolabs-3009 | healthy | postgresql | labs.zeroshot.studio | 4/25/2026 |
| link-staging | 3010 | link-staging-3010 | healthy | postgresql | — | 3/23/2026 |
| zerocv-offer | 3011 | zerocv-offer-3011 | down | — | — | 3/9/2026 |
| idea-vault | 3012 | idea-vault-3012 | healthy | — | — | 3/27/2026 |
| zerovps-landing | 3013 | zerovps-landing | unhealthy | — | — | 3/27/2026 |
| zeroseo | 3014 | zeroseo-3014 | unhealthy | — | — | 3/27/2026 |
| zero-content-pipeline | 3015 | zero-content-pipeline | healthy | — | — | 4/21/2026 |
| zero-box | 3016 | zero-box-3016 | healthy | — | zerobox.zeroshot.studio | 4/18/2026 |
| activepieces-test | 3017 | activepieces-test-3017 | healthy | PGLITE (embedded) | activepieces-test.zeroshot.studio | 4/18/2026 |
| dify-test | 3018 | dify-test-nginx-1 | healthy | postgresql | dify-test.zeroshot.studio | 4/18/2026 |
| zeroui-chat | 3019 | zeroui-chat | healthy | sqlite | chat.zeroshot.studio | 4/24/2026 |
| google-mcp | 3020 | google-mcp-3020 | healthy | — | zeroshot.studio/mcp | 2/3/2026 |
| zero-creative | 3021 | zero-creative | healthy | — | — | 4/3/2026 |
| zero-creative-mcp | 3022 | zero-creative-mcp | healthy | — | — | 4/3/2026 |
| zeromemory | 3050 | zeromemory-api-1 | healthy | postgresql | — | 3/2/2026 |
| zeromemory-mcp | 3051 | zeromemory-mcp | healthy | — | — | 3/18/2026 |
| zerolabs-mcp | 3052 | zerolabs-mcp | healthy | — | — | 4/15/2026 |
| zero-signals | 3060 | zero-signals | healthy | postgresql | — | 3/18/2026 |
| zero-signals-mcp | 3061 | zero-signals-mcp | healthy | — | — | 3/18/2026 |
| zerovault | 4001 | zerovault-4001 | healthy | postgresql | vault.zeroshot.studio | 3/8/2026 |
| zerorelay | 8765 | healthy | — | — | 4/15/2026 | |
| openclaw | 8788 | hibernated | — | — | 3/23/2026 | |
| minio | 9000 | infra-minio | healthy | — | — | 1/19/2026 |
| wordpress-jg | — | wordpress-jg | removed | mariadb | — | 2/2/2026 |
| payload-cms | — | decommissioned | — | — | 3/23/2026 | |
| health-monitor | — | zerovps-health-monitor | healthy | — | — | 2/27/2026 |
| zerotraining | — | healthy | — | labs.zeroshot.studio/workshop | 3/23/2026 | |
| plane | — | removed | postgresql (internal plane-db container) | plan.zeroshot.studio | 4/21/2026 | |
| zeroui-orchestrator | — | removed | postgresql | — | 4/23/2026 | |
| ollama | 11434 | ollama | healthy | — | — | 3/9/2026 |
zerolinkhealthy
Port3001
Containerzerolink-3001
Path/opt/apps/zerolink-3001
Healthhttp://localhost:3001/health
aux-voice-assistanthealthy
Port3002
Containeraux-voice-assistant
Path/opt/apps/zeroaux-3002/aux-voice-assistant
Healthhttp://localhost:3002/health
zerocorehealthy
Port3003
Containerzerocore-3003
Path/opt/apps/zerocore-3003
Healthhttp://localhost:3003/health
zeroflowhealthy
Port3004
Containerzeroflow-official
Path/opt/apps/zeroflow-official
Healthhttp://localhost:3004/healthz
Noten8n workflow automation - healthcheck added 2026-02-27 (MAINT-2026-001)
autogen-studiohealthy
Port3005
Containerautogen-studio-3005
Path/opt/apps/autogen-studio-3005
Healthhttp://localhost:3005/health
gmaps-scraperhealthy
Port3006
Containergmaps-scraper-3006
Path/opt/apps/google-maps-scraper
Healthhttp://localhost:3006/health
zeroui-planehealthy
Port3007
Containerplane-proxy-1
Path/opt/apps/zeroui/.data/plane-selfhost/plane-app
Healthhttp://127.0.0.1:3007/
NoteDirect-auth Plane runtime redeployed on 2026-04-23 from the local ZeroUI source. The live compose project now runs from `/opt/apps/zeroui/.data/plane-selfhost/plane-app` with its environment file at `/opt/apps/zeroui-plane/plane.vps-plesk.env`; preserved Plane state was restored from `/opt/preserved-data/20260423_161300-zeroui-stack-removal/zeroui-plane/data`; and the checked-in `plane_default` subnet is pinned to `10.240.6.0/24` to avoid the VPS bridge address-pool exhaustion hit during the first redeploy attempt. Security hardening deploy `e698690` narrows `TRUSTED_PROXIES`, pins the bundled MinIO image by digest, and keeps the public proxy on a `pids_limit`, while intentionally leaving Caddy's default Linux capability path intact because `no-new-privileges` blocked the image from starting. Follow-up deploy `672f676` sets `SESSION_COOKIE_NAME=plane-session-id` so Plane native auth no longer collides with stale generic `session-id` browser cookies. On 2026-04-24 the PI services were recreated so `plane-pi-api-1`, `plane-pi-worker-1`, and `plane-pi-beat-1` also picked up `SESSION_COOKIE_NAME=plane-session-id`, stopping the PI session-check loop that was driving `/api/instances/` 429 responses.
zerovps-dashboardhealthy
Port3008
Containerzerovps-dashboard-3008
Path/opt/apps/zerovps-dashboard
Healthhttp://127.0.0.1:3008/
Resources0.5 CPU, 256M
NoteZeroVPS observability dashboard — read-only, Next.js on port 3008
zerolabshealthy
Port3009
Containerzerolabs-3009
Path/opt/apps/zerolabs-3009
Healthhttp://localhost:3009/
NoteZeroLabs — Next.js blog + signals dashboard. Reclaimed port 3009 from Payload CMS (2026-03-13). MinIO bucket blog-files.
link-staginghealthy
Port3010
Containerlink-staging-3010
Path/opt/apps/link-staging
Healthhttp://localhost:3010/health
NoteStaging environment for zerolink
zerocv-offerdown
Port3011
Containerzerocv-offer-3011
Path/opt/apps/zerocv-offer
Healthhttp://localhost:3011/
Resources0.25 CPU, 64M
NoteZeroCV offer/landing page — PARKED (no traffic). Container stopped, can restart anytime. Static nginx:alpine on staging port 3011.
idea-vaulthealthy
Port3012
Containeridea-vault-3012
Path/opt/apps/zerovault-4001
Healthhttp://localhost:3012/
NoteIdea Vault — sub-component of ZeroVault on staging port 3012. Sidecar: idea-vault-rate-limit-redis.
zerovps-landingunhealthy
Port3013
Containerzerovps-landing
Path/home/claude/zerovps-landing
Healthhttp://localhost:3013/
NoteZeroVPS landing page on staging port 3013. Healthcheck fails due to IPv6/IPv4 mismatch (app running fine, Docker healthcheck uses ::1 but server binds IPv4 only). Fix: add --add-host=host.docker.internal:host-gateway or switch healthcheck to 127.0.0.1.
zeroseounhealthy
Port3014
Containerzeroseo-3014
Path/home/claude/zeroseo
Healthhttp://localhost:3014/
NoteZeroSEO on staging port 3014. UNHEALTHY: ERR_DLOPEN_FAILED — better-sqlite3 native module requires glibc but container uses musl (Alpine). Fix: rebuild on node:22-slim (Debian) instead of Alpine, or use a glibc-compatible base.
zero-content-pipelinehealthy
Port3015
Containerzero-content-pipeline
Path/opt/apps/zero-content-pipeline
Healthhttp://127.0.0.1:3015/health
NoteZero Module for Codex-native ZeroLabs publishing. API is localhost-only on :3015; worker is relay-connected as content_codex and publishes to ZeroLabs over authenticated MCP/API.
zero-boxhealthy
Port3016
Containerzero-box-3016
Path/opt/apps/zero-box
Healthhttp://127.0.0.1:3016/
NoteStatic ZeroBox mini-site deployed from the ZeroMini OpenClaw workspace snapshot and now auto-deploys from subtree branch `zerimini-live` in `zeroshotstudio/ZeroBox`. Zee reaches the app shell via forced-command SSH user `zee-zero-box`, which drops directly into the `zero-box-3016` container mounted at /workspace. Clean-URL route resolution and live-domain metadata were corrected on 2026-04-18, the live bundle includes the `/app/` shell pages, trust pages, and `dist/backend` package, and GitHub Actions now syncs the `projects/zerobox` subtree from ZeroMini to `/opt/apps/zero-box/workspace`, rebuilds, and refreshes the live container automatically on each committed ZeroMini change. Latest verified live deploy: GitHub branch commit `74cf463` (`Upgrade ZeroBox app to workspace UI`), sourced from ZeroMini workspace commit `a29b0b9`.
activepieces-testhealthy
Port3017
Containeractivepieces-test-3017
Path/opt/apps/activepieces-test
Healthhttp://127.0.0.1:3017/api/v1/health
NoteActivepieces staging install for testing using the official single-container topology (`AP_DB_TYPE=PGLITE`, `AP_REDIS_TYPE=MEMORY`). Upstream repo was cloned to `/opt/apps/activepieces-test/upstream` at tag `0.81.4` / commit `bf9e179`, but that image failed PGLITE startup on this VPS (`information_schema.tables` missing), so the live runtime uses `activepieces/activepieces:latest` instead.
dify-testhealthy
Port3018
Containerdify-test-nginx-1
Path/opt/apps/dify-test
Healthhttp://127.0.0.1:3018/apps
NoteDify Community Edition staging install from upstream release `1.13.3`, with the deploy surface copied from `/opt/apps/dify-test/upstream/docker` into `/opt/apps/dify-test`. Public HTTPS is terminated by Plesk while Dify's internal nginx listens on `127.0.0.1:3018`. The official bundled PostgreSQL, Redis, Weaviate, sandbox, plugin daemon, worker, and web services are all running inside the stack. VPS-specific patches: plugin debugging port is bound to localhost only (`127.0.0.1:53018`), and Docker networks are pinned to `10.240.0.0/24` and `10.240.1.0/24` because the host's automatic bridge address pools were exhausted.
zeroui-chathealthy
Port3019
Containerzeroui-chat
Path/opt/apps/zeroui
Healthhttp://127.0.0.1:3019/health
NoteDirect-auth Open WebUI runtime redeployed on 2026-04-23 from the local ZeroUI source as the new production chat surface. Live app code is staged at `/opt/apps/zeroui`, preserved Open WebUI and Qdrant state was restored from `/opt/preserved-data/20260423_161300-zeroui-stack-removal/zeroui/data/{open-webui,qdrant}`, and Plesk now proxies `chat.zeroshot.studio` straight to `127.0.0.1:3019` with no shared Authentik/oauth2-proxy wrapper. Security hardening deploy `e698690` pins the WebUI/Qdrant/Searxng images by digest, keeps signup disabled, and drops all Linux capabilities for the chat-side containers. Follow-up deploy `06f7fa0` restores the direct Chat custom gateway contract by pinning `zerovps/default`, routing Open WebUI to the existing ZeroVPS Codex gateway through `zerovps.gateway:18812`, and reapplying the Chat/Plane sidebar crosslink assets after container start.
google-mcphealthy
Port3020
Containergoogle-mcp-3020
Path/opt/apps/google-mcp-3020
Healthhttp://localhost:3020/health
NoteGoogle Workspace MCP Server - centralized Drive/Gmail access for all apps
zero-creativehealthy
Port3021
Containerzero-creative
Path/opt/apps/zero-creative
Healthhttp://127.0.0.1:3021/health
NoteLive Zero Module for shared visual runtime jobs. API is localhost-only on :3021 and serves ZeroContentPipeline over Docker networking; paired MCP service is on :3022.
zero-creative-mcphealthy
Port3022
Containerzero-creative-mcp
Path/opt/apps/zero-creative/mcp
Healthhttp://127.0.0.1:3022/health
NoteLive MCP service for ZeroCreative. Streamable HTTP on /mcp with bearer auth, bound to VPS localhost on :3022.
zeromemoryhealthy
Port3050
Containerzeromemory-api-1
Path/opt/apps/zeromemory
Healthhttp://localhost:3050/health
Notepgvector memory/RAG API — own PostgreSQL on port 5433. Embeddings: nomic-embed-text (768d) via local Ollama, replacing OpenAI text-embedding-3-small
zeromemory-mcphealthy
Port3051
Containerzeromemory-mcp
Path/home/claude/ZeroVPS/mcp-server-zeromemory-remote
Healthhttp://127.0.0.1:3050/health
zerolabs-mcphealthy
Port3052
Containerzerolabs-mcp
Path/opt/ZeroLabsMCP
Healthhttp://127.0.0.1:3009/
NoteStandalone ZeroLabs MCP wrapper repo. Streamable HTTP on Tailscale IP 100.127.106.41:3052 with bearer auth, wired in .mcp.json as 'zerolabs'. GitHub Actions deploys main to /opt/ZeroLabsMCP, and the wrapper forwards to the public ZeroLabs origin because host loopback port 3009 is unreachable from the container network.
zero-signalshealthy
Port3060
Containerzero-signals
Path/opt/apps/zero-signals
Healthhttp://localhost:3060/health
Resources1 CPU, 512M
NoteZero Module: Reddit content signals pipeline. API + worker + MCP. Collection via ZeroMini (residential IP), analysis on VPS.
zero-signals-mcphealthy
Port3061
Containerzero-signals-mcp
Path/opt/apps/zero-signals/mcp
Healthhttp://127.0.0.1:3060/health
NoteMCP server for zero-signals. 8 tools for AI agent access to Reddit signals data.
zerovaulthealthy
Port4001
Containerzerovault-4001
Path/opt/apps/zerovault-4001
Healthhttp://localhost:4001/
Resources1 CPU, 512M
NoteZeroVault — blank Next.js 16 + dedicated Postgres 17. New port block 4000+. Sub-component: idea-vault on port 3012.
zerorelayhealthy
Port8765
Container
Path/opt/zerorelay
Health
NoteZeroRelay — Tailscale-only WebSocket chat relay on 100.127.106.41:8765. Native Python, not Docker. Systemd services: zerorelay.service (broker), zerobridge.service (OpenClaw bridge), claude-bridge.service, codex-bridge.service, telegram-bridge.service. External ZeroContentPipeline worker also connects as content_codex.
openclawhibernated
Port8788
Container
Path/opt/openclaw
Health
NoteHIBERNATED 2026-03-23 — transitioning to ZeroMini. Gateway dead, 13 cron jobs disabled, config-watchdog killed. Ollama runs independently (keep alive for ZeroMemory/ZeroSignals). Do not delete /opt/openclaw.
miniohealthy
Port9000
Containerinfra-minio
Path/opt/apps/infrastructure
Healthhttp://localhost:9000/minio/health/live
NoteS3-compatible object storage
health-monitorhealthy
Portnone
Containerzerovps-health-monitor
Path/opt/apps/health-monitor
Healthhttp://localhost:8080/health
NoteZeroVPS health monitoring daemon — network_mode: host, listens on 0.0.0.0:8080. Alerts disabled (configure DISCORD_WEBHOOK_URL + NTFY_TOPIC in .env to enable)
zerotraininghealthy
Portnone
Container
Path/opt/apps/zerotraining
Health
NoteZeroTraining — interactive workshop platform. Served by sw-nginx at /workshop. No Docker container (native Node.js or static). Live-edit mode.
ollamahealthy
Port11434
Containerollama
Path/opt/apps/ollama
Healthhttp://localhost:11434/
Resources4 CPU, 6G
NoteOllama local LLM inference server (CPU). Models: qwen2.5:3b (L0), qwen2.5:7b (L1), qwen2.5-coder:7b (L2), nomic-embed-text (zeromemory embeddings). OLLAMA_KEEP_ALIVE=2m. Limits reduced from 14G/10cpu to 6G/4cpu (2026-03-09). Standalone container (not openclaw compose).