This page documents the optional multi-tool intelligence stack that runs alongside the core Paperclip control plane. The intelligence stack is additive:
  • PostgreSQL remains the canonical control-plane database
  • ClickHouse remains the shared warehouse and telemetry store
  • vendor tools attach around those core stores
  • obs-proxy provides stable hostnames in front of the stack

​
What The Overlay Starts

The intelligence overlay adds these services:
  • Langfuse
  • Redash
  • Bytebase
  • ChartDB
  • Gigapipe
  • MindsDB
  • Telescope
  • MinIO for Langfuse object storage
  • obs-proxy for hostname-based ingress
  • cloudflared for the optional hosted tunnel path
It also bootstraps the supporting databases these tools need.

​
Runtime Topology

​
Primary Commands

Use the overlay wrapper rather than raw compose commands: 
./scripts/intelligence-stack.sh up
./scripts/intelligence-stack.sh down
./scripts/intelligence-stack.sh ps
The wrapper derives intelligence-postgres settings from DATABASE_URL when possible, prepares the local databases, starts obs-proxy, and only starts cloudflared when the tunnel is intentionally enabled.

​
Local Service URLs

SurfaceLocal URLHosted URL
Paperclip monitorhttp://obs.localhosthttps://obs.sydiolabs.com
Langfusehttp://langfuse.localhosthttps://langfuse.sydiolabs.com
Redashhttp://redash.localhosthttps://redash.sydiolabs.com
Bytebasehttp://bytebase.localhosthttps://bytebase.sydiolabs.com
MindsDBhttp://mindsdb.localhosthttps://mindsdb.sydiolabs.com
Telescopehttp://telescope.localhosthttps://telescope.sydiolabs.com
ChartDBhttp://chartdb.localhosthttps://chartdb.sydiolabs.com
Gigapipehttp://gigapipe.localhosthttps://gigapipe.sydiolabs.com
MinIO APIhttp://minio.localhosthttps://minio.sydiolabs.com
MinIO consolehttp://minio-console.localhosthttps://minio-console.sydiolabs.com

​
Hosted Ingress Notes

For hosted use:
  • obs.sydiolabs.com is the canonical monitor origin
  • each tool keeps its own protected hostname
  • Cloudflare Access sits in front of the tunnel
  • obs-proxy remains the only browser-facing local origin behind the tunnel
See Hosted Intelligence Monitor Ingress for the exact ingress contract.

​
Verification

Typical verification commands: 
./scripts/intelligence-stack.sh ps
curl -I http://127.0.0.1:3000
curl -sS http://127.0.0.1:5001/ping
curl -I http://127.0.0.1:8081/healthz
curl -I http://127.0.0.1:8082
curl -sS http://127.0.0.1:3102/ready
curl -I http://127.0.0.1:47334
curl -I http://127.0.0.1:9898

​
Operational Boundaries

  • The monitor summarizes system health but does not replace the vendor tools.
  • Tool metadata is external; Paperclip only owns its control-plane records and derived summaries.
  • Hosted ingress should never be debugged before local service health is confirmed.