Skip to content
Weik.ioDocs
2026.2
Try Weik.io

Network

Weik.io 2026.2

The port and protocol of every connection of an installation and the firewall rules that follow from them. Product page · Video

Watch: What runs where, 3:42

The video shows where the hub and the agents run and the two outbound connections an agent makes on port 443.

On this page

Weik.io opens no inbound port at a site. An agent makes two outbound connections to the hub on port 443. Any other traffic from a site is your integrations’ traffic to your systems. The hub publishes only port 443, where it terminates TLS for its names and for the gateway hostnames.

What leaves a site#

From To Port and protocol Carries
The agent’s leaf node The hub’s link address, such as nats.acme.example 443, WebSocket over TLS (wss) The agent’s control traffic, events in both directions and the built integration versions the agent fetches
Each integration’s Java process and the agent The hub’s address, /otlp/v1/logs, /otlp/v1/metrics and /otlp/v1/traces 443, HTTPS Logs, metrics and traces over OpenTelemetry (OTLP). Each process uses its deployment’s credential.

A host that also runs a gateway uses the same two connections.

An integration’s own traffic, such as calls to an ERP or a bank’s SFTP server, leaves the site on that system’s own port.

What stays inside a site#

Between On
The Java processes and the local leaf node Port 4222 on the site’s own container network, never published
The agent and each process’s health and metrics endpoint One loopback port per process, from a configured range
The agent and a running integration, for weikio invoke Files in the deployment’s run folder instead of a network port. The run folder is home/agent/runs/<deployment ID> in the site’s folder on Linux and C:\ProgramData\Weikio\agent\runs\<deployment ID> on Windows.
An integration’s own HTTP listener Port 8080 on every interface, Camel’s default, unless the integration sets its own server settings. Your firewall at the site controls who reaches it.

A partner who calls a hub gateway can reach an API in front of an integration at a site. The hub gateway relays the call to the site’s gateway without opening a port at the site. See Gateways at sites for the relay.

Ports at the hub#

Listener Port Reached by
The backend, which serves the API and the admin UI and runs the OTLP ingest 443, through your load balancer The CLI, pipelines, browsers and every agent
APIM, the API gateway 443, one or more hostnames per environment Your API callers
The message server’s link listener 443, WebSocket The leaf node of every agent
The message server’s client port The hub’s own network only The backend and APIM. This port doesn’t accept an agent’s credential.
The log, metric and trace stores The hub’s own network only The backend only
/healthz and /readyz 443, on the hub’s address Your monitoring and weikio platform health
/metrics The hub’s own network, never through port 443 Your monitoring

On port 443, the hub passes each connection on by the name in its request. The hub’s terminator handles TLS for the hub’s own names. Every gateway hostname goes to APIM, which terminates TLS with that gateway’s certificate. The hub accepts TLS 1.2 and 1.3. On TLS 1.2 it accepts only the AEAD cipher suites, which are AES-GCM and ChaCha20. On a hub of several servers, the connections between the message servers use TLS too.

The terminator’s replies have the same headers as the hub’s other replies:

  • Referrer-Policy
  • X-Content-Type-Options
  • Permissions-Policy

The reply to a request for a name or path that nothing serves is an empty 404 with the headers above and Strict-Transport-Security.

The hub publishes port 443 and nothing else, and four DNS names point at it. Port 443 passes each connection on by the name it asks for. The CLI, pipelines, browsers and each agent's telemetry use acme.example, and each agent's leaf node links to nats.acme.example. The terminator ends TLS for these two names of the hub's own and passes them to the backend, with the API, the admin UI, the token issuer and the OTLP endpoint, and to the message server's link listener. Callers of production APIs use api.acme.example and callers of devtest APIs use api-test.acme.example. These go to the API gateway, which ends TLS itself with the certificate of each environment's gateway.

All four names use port 443. The terminator handles TLS for the hub's own two names, but APIM handles TLS for the gateway hostnames.

Weik.io obtains and renews every certificate:

  • For a name that points at the hub, Weik.io proves ownership to the public authority on port 443.
  • For a name behind a CDN’s proxy or on an internal network, Weik.io proves ownership through DNS.
  • For a name that no public authority signs, such as an .internal name, Weik.io issues a certificate from its own authority.

See Certificates for each source and when Weik.io uses it.

The hub’s four names#

An installation with two environments has four DNS names, which all point at the hub’s address.

Name Goes to Used by
acme.example The backend and the admin UI The CLI, pipelines, browsers and the telemetry of every agent
nats.acme.example The message server’s link listener The leaf node of every agent, as wss://nats.acme.example:443
api.acme.example APIM, the gateway of production Callers of production APIs
api-test.acme.example APIM, the gateway of devtest Callers of devtest APIs

The two API names are the hostnames of each environment’s gateway. When you add a gateway or a hostname, add its name to DNS too.

When the names are behind Cloudflare’s proxy, the CLI uploads large integration files in parts under the proxy’s request size limit, and it resumes an interrupted upload.

Firewall rules#

Direction Rule
Inbound to the hub Port 443 only, from wherever the CLI, pipelines, API callers and agents connect from
Inbound to a site Nothing
Outbound from a site Port 443 to the hub’s address. The integrations’ own traffic to your systems is separate.
Outbound from the hub The Maven repositories that Weik.io fetches libraries from, or one mirror on an air-gapped hub. If you set up a Dapr secrets sidecar or telemetry forwarding, the hub also reaches the sidecar and the systems that forwarding sends to.

The hub never connects to a Git repository. Pipelines push changes to Weik.io with the weikio CLI, so the hub needs no Git credentials and no network path to your Git host.

An agent beside the hub, in the hub’s own network, can link to the message server’s listener on port 7422 directly instead of through port 443. It’s enrolled with --via hub-network and needs no public name.

The hub’s allowed networks limit which addresses can reach the hub’s names. See Allowed networks and TLS for how they work.

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo