Case study

EchoTek

Self-hosted automation backbone — n8n and related services under the echotek.co.za ops domain.

PublishedOwner / Builder · 2026Jacques (ops infra)

Infrastructure / connected automation topology

Live reference

n8nVPSDockerAPIs

Metrics omitted until confirmed.

Context

EchoTek is the studio’s connected automation host — the place ForgeOS and other n8n workflows actually run. Think topology and uptime, not a consumer landing page.

Approach

  • Self-host orchestration (n8n) behind api.echotek.co.za
  • Keep workflow repos and VPS config separate from client marketing sites
  • Treat the API host as infrastructure evidence, not a vanity domain claim

Outcome

Confirmed automation base URL used by ForgeOS env docs. Public marketing microsite remains light / TBC; the portfolio points at the real ops endpoint the systems use.

Stack notes

  • n8n on VPS
  • Docker-oriented ops
  • Shared API surface for studio automations

← All work·Start a project conversation