This page lists what users and admins need to run PADAS in production or staging environments.
PADAS runs as a standalone service. External systems such as Kafka, Splunk, syslog devices, and object storage are optional and only required when you enable matching connectors.
Operating system
| Item | Requirement |
|---|
| Primary target | Linux x86_64 |
| Service manager | systemd recommended |
| Container option | TBD (not documented in this site yet) |
Host capacity (recommended)
| Component | Recommended baseline |
|---|
| CPU | 4+ cores |
| Memory | 8 GB minimum, 16 GB preferred |
| Disk | SSD; size based on logs + retention + WAL usage |
Optional integrations (via connectors)
Connectors are how PADAS talks to the outside world. Each is optional — pick the ones your deployment needs. Source connectors push events into streams; sink connectors drain them out.
| Connector | Direction | When to use |
|---|
| PADAS TCP | source / sink | Engine-to-engine streaming over the native PADAS wire format. No external dependencies. |
| HTTP | source / sink | Push or pull over HTTP APIs. |
| File | source / sink | NDJSON or text files. The simplest local-development connector — no extra infrastructure. |
| Syslog | source / sink | RFC 3164 / 5424 over UDP/TCP. Requires reachable network interfaces. |
| Splunk HEC | source / sink | HTTP Event Collector compatibility — needs a reachable Splunk instance (or HEC mock for tests). |
| Kafka | source / sink | Use when you already operate Kafka. Requires reachable broker(s); KRaft-mode Kafka does not need a separate ZooKeeper. Not required for PADAS to run. |
| Object storage (S3 API) | sink | S3-compatible storage with Parquet or JSON Lines for archive flows. |
Network and access
| Item | Requirement |
|---|
| Inbound access | Engine HTTPS API on 8999 (paths under https://<CORE_IP>:8999/api/v1/… unless changed); health (/health or equivalent) reachable from operators and gateways |
| Outbound access | Reachable endpoints for enabled connectors (Kafka, Splunk, S3, etc.) |
| Service account | Non-root runtime user with write access to data and log directories |
Where to next