Self-hosting overview

Origamy splits into two planes. The control plane (dashboard, configuration, the app at app.origamy.io) is always hosted by Origamy. The data plane — the event pipeline that ingests, transforms, stores, and routes your customer data — can run either in Origamy Cloud or in your own infrastructure. Self-hosting means your telemetry never leaves your network.

How it connects

The data plane opens one outbound TLS connection to Origamy (grpc.origamy.io:443). No inbound ports are required — your firewall only needs to allow egress on TCP 443. The dashboard reaches your data (live events, profiles, analytics) back through that same tunnel.

Your infrastructure
├── nats               (event bus)
├── clickhouse         (analytics store)
├── redis              (session cache)
├── postgres           (operational store)
├── ingestion-gateway  (receives events from your SDKs)
├── transformer-engine (JS transform pipeline)
├── identity-resolver  (user/device stitching)
├── segment-evaluator  (real-time segments)
├── bulker-worker      (warehouse sync)
├── workflow-engine    (messaging automation)
├── config-sync        (pulls config from Origamy)
└── portal-agent  ──── outbound TLS ──────▶ Origamy control plane
                                             (dashboard, config, queries)

The fast path: the Origamy CLI

The origamy CLI deploys the whole data plane in one command. It auto-detects your environment: a reachable Kubernetes cluster (kubectl) gets a Helm install into the origamy-dp namespace; otherwise it generates a Docker Compose project in ./origamy-dp-<id>/.

Download the binary for your platform from GitHub releases (macOS and Linux, amd64/arm64):

curl -fsSL -o origamy \
  https://github.com/QubelyLabs/origamy-cli/releases/latest/download/origamy_linux_amd64
chmod +x origamy && sudo mv origamy /usr/local/bin/

Get an enrollment token from the Connections page in your Origamy dashboard, then:
Terminal window
```
origamy deploy --token dpe_xxx
```

The CLI generates a keypair locally and enrolls with a certificate signing request — the private key never leaves your machine. Enrollment tokens are single-use and expire after 72 hours; get a fresh one from the Connections page if yours has lapsed.

Once the deploy finishes, the Connections page shows your data plane as connected, and the dashboard works exactly as it does for cloud workspaces.

To tear it down later: origamy uninstall.

Manual installs

If you want full control over the deployment, follow the platform guide:

Docker Compose — a single Linux host, ideal for evaluation and small production workloads.
Kubernetes (Helm) — the published chart runs the full pipeline, including its datastores, and scales the workers independently.

Where events go

With a self-hosted data plane, your SDKs send events to your gateway, not events.origamy.io. Each guide covers exposing the ingestion endpoint; once it’s public, paste its URL into your source’s Setup tab in the dashboard so the copy-paste SDK snippets use it automatically.