Tranzify Watch/Documentation
Documentation · v0.2.0

Deploy the platform.
Connect your infrastructure.

A practical guide to installing, securing and operating Tranzify Watch in your own environment.

01

System overview

Tranzify Watch is a self-hosted platform for telemetry collection, event exploration, threat detection and incident response.

Current release

Version 0.2.0 provides Linux agents for amd64 and arm64. Amazon S3 and HTTP API sources operate without an agent.

Core APIManagement, authentication, policies and workflows
PostgreSQLUsers, settings and operational state
ClickHouseEvents, analytics and high-volume search
Linux AgentPolicy-driven telemetry collection
02

System requirements

The installer exits before making changes when the host does not meet the minimum requirements.

ResourceMinimumRecommended
Operating systemUbuntu 22.04 LTSUbuntu 24.04 LTS
CPU2 vCPU4+ vCPU
Memory8 GB16+ GB
Disk40 GB SSDBased on volume and retention
NetworkTCP 80/443Domain and trusted TLS
Capacity planning

A 365-day retention policy does not imply a fixed disk size. Estimate events per second, average event size and keep at least 30% free space.

03

One-command installation

The installer validates compatibility, verifies the signed release and deploys isolated system components.

$ curl -fsS https://packages.tranzify.watch/install.sh | sudo bash
  1. 1
    Validate the host

    Check OS, architecture, CPU, memory, disk, ports and package access.

  2. 2
    Verify the release

    Validate SHA-256, the KMS manifest signature and installer compatibility.

  3. 3
    Prepare services

    Create the system account, directories, PostgreSQL, ClickHouse, backend and frontend.

  4. 4
    Complete setup

    Use a one-time token to create the first administrator in the setup wizard.

Verify the release without installing

$ curl -fsS https://packages.tranzify.watch/install.sh | bash -s -- --verify-only --version 0.2.0
04

Network and TLS

Use a public domain, a direct IP address or a closed network. The connection mode can be changed later in platform settings.

Public

Domain + Let’s Encrypt

Automatic trusted certificate issuance and renewal. DNS and inbound TCP 80/443 are required.

Private

IP / VPN + Internal CA

For VPC, PrivateLink, VPN and isolated networks. Trust the internal CA on every agent.

Isolated

HTTP without TLS

Only for physically trusted test segments. Never use it across untrusted networks.

05

Connect a Linux agent

The agent enrolls once. A short-lived token is stored only as a hash and becomes invalid after successful use.

No remote execution

The core may deliver a signed configuration or disable an agent. It cannot execute arbitrary commands on the monitored host.

What a policy controls

  • heartbeat, resource and inventory intervals;
  • update, antivirus, firewall and listener checks;
  • journald units and custom log file paths;
  • queue size, batching and offline behavior;
  • a dedicated dataset for every event stream.
06

Agentless data sources

Scheduled sources keep an independent cursor and do not reread successfully processed data.

Amazon S3

Use an IAM role or access key, bucket and prefix, glob patterns, nested objects and explicit error handling.

production/audit/*.log
HTTP API

Configure GET or POST, headers, body, expected status code and response-content checks.

200 + body contains "ok"
07

Parsers and detection rules

A text line first matches a safe RE2 expression. Named groups become normalized fields before a versioned detection rule evaluates them.

192.0.2.10 - admin [27/Jul/2026:08:12:45 +0000] "GET /health HTTP/1.1" 200 42
                    ↓ RE2 named groups
source.ip · user.name · http.method · url.path · http.status_code

Raw preserves the original event for investigation. Normalized contains the stable output of a specific parser revision used by filters, dashboards and rules.

08

Incident response

Promote an alert to an incident with owners, statuses, comments, attachments, evidence, resolution notes and a complete activity timeline.

The workflow helps produce operational evidence, but does not by itself constitute ISO 27001 or PCI DSS certification.

09

Security model

  • Least privilegeRoles separate visibility, alert handling and administration.
  • Signed configurationThe agent applies only a valid Ed25519 policy and does so atomically.
  • Protected secretsSource credentials are encrypted and never returned by the API after saving.
  • Immutable auditSign-ins, reads, changes, errors and access denials enter the activity log.
  • No arbitrary codeCustom parsers and rules use a constrained DSL without code execution.
10

Updates and rollback

Every release is immutable. The client verifies the manifest signature before download and every artifact hash before installation.

$ sudo tranzify-watch update --version 0.2.0
Before updating

Back up PostgreSQL, ClickHouse and configuration. Test production upgrades on a representative non-production instance first.

Next step

Connect the first server

After installation, open Agents and create a one-time enrollment token.

Return to quick start