Developer Portal

Build with the
PlumbrC API

Create an account, register your app, and get API keys to integrate log redaction into your workflow.

Quick Start
curl -X POST https://plumbr.ca/api/redact \
  -H "Authorization: Bearer plumbr_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"text": "password=secret123"}'
API Keys

Generate unique API keys for each of your applications.

5M+ Lines/sec

Native C engine with AVX2 SIMD. AMD Ryzen optimized.

Secure by Default

HTTPS only. Keys never logged. Ephemeral processing.

Usage Analytics

Track API calls, lines processed, and more.

3 Ways to Use

Native C binary, Python package, or REST API.

Open Source

Source Available. Free for open-source, non-commercial, and charities. Enterprise licenses available.

By creating an account, you agree to our Code of Conduct

Choose Your Integration

We believe in being honest about performance. Here's what to expect from each option.

RECOMMENDED

Native C Binary

Maximum performance
5M+ lines/sec

175 MB/s throughput

  • Pure C with zero overhead
  • AVX2 SIMD & SSE 4.2 optimized
  • Tuned for AMD Ryzen processors
  • Multi-threaded pipeline
echo "logs" | ./plumbr -j0

Python Package

Best of both worlds
2M lines/sec (bulk)

C engine via ctypes FFI, bulk API

  • pip install plumbrc
  • Same C engine under the hood
  • No network latency
  • Great for CI/CD pipelines
from plumbrc import Plumbr
r = Plumbr()
r.redact("AKIA...")

REST API

Easy integration
~0.1ms processing

Network latency is the bottleneck

  • Language-agnostic HTTP calls
  • Best for testing & prototyping
  • Use batch endpoint for throughput
  • Sub-ms server processing time
curl -X POST /api/redact \
  -d '{"text": "..."}'

A note on performance

The REST API processes each request in under 0.1ms on the server, but network round-trip latency (~100-800ms depending on location) dominates the total time. For production workloads, we strongly recommend the native C binary or the Python package — both run locally with zero network overhead. The C engine is specifically optimized for AMD Ryzen processors using AVX2 and SSE 4.2 SIMD instructions, but works on any x86-64 CPU. The REST API is ideal for testing, prototyping, and low-volume use cases where convenience matters more than throughput.