Detect and redact sensitive data across documents, images, and audio.
The open-source multimodal redaction API: an LLM-powered engine and HTTP service that finds PII and applies your redaction policies, wrapped in a multi-tenant, self-hostable Rust server.
A document flows through two phases: detection analyzes it for sensitive entities and stores a reviewable report; redaction applies the pipeline's policies (with optional reviewer edits) to produce a redacted file. Detection runs asynchronously off a transactional work queue; redaction is synchronous and repeatable. Everything is scoped to isolated workspaces with per-workspace credential encryption.
Warning
Active development. API not stable. Public APIs, configuration shapes, on-disk formats, and wire protocols may change without notice between releases. Pin a specific commit if you depend on this in production.
- Multimodal redaction: detect and remove sensitive data across PDFs, office documents, images, and audio.
- AI-powered detection: LLM- and pattern-driven PII/entity recognition, governed by configurable redaction policies.
- Reviewer edits: suppress a false positive, retag a detection, or add one the analysis missed, then re-redact, as many times as needed.
- Workspace isolation: multi-tenant workspaces with HKDF-derived, per-workspace credential encryption.
- Live status: server-sent event streams for detection progress and notifications, fed by NATS pub/sub.
- Interactive docs: auto-generated OpenAPI served through a Scalar UI.
- Rust + Cargo: 1.99+, Edition 2024
- PostgreSQL 18+, NATS 2.10+ (JetStream), and an S3-compatible blob store (RustFS by default). The dev compose file provides all three.
The fastest way to get started is with Nvisy Cloud. To run a server locally:
make install-all # Install tools and make scripts executable
make generate-all # Generate .env, auth keys, and apply migrations
docker compose -f docker/docker-compose.dev.yml up -d # Start Postgres, NATS, RustFS
make run # Run the serverThe API then serves interactive OpenAPI docs (Scalar UI) at the running server's
docs path. For self-hosted deployments, see docker/ for compose
files and infrastructure requirements, and .env.example for
configuration.
Run make help to list the available commands.
docs/ covers the architecture, one document per concern.
| Document | Subject |
|---|---|
| Architecture | The crates, the detect/redact pipeline, and how they fit together. |
| Intelligence | Detection capabilities and the in-process redaction engine. |
| Providers | Inference and object-store provider design. |
| Security | The encryption, authentication, and isolation model. |
API documentation lives at docs.nvisy.com.
- Changelog: CHANGELOG.md for release notes and version history
- Contributing: CONTRIBUTING.md
- License: Apache 2.0, see LICENSE.txt
- Documentation: docs.nvisy.com
- Email: [email protected]