Grepture

Key features

• PII detection across 80+ built-in patterns The gateway scans prompts and responses for emails, phone numbers, IDs, and similar sensitive shapes, then redacts matches in milliseconds before the provider sees them.[1][2]

• Reversible redaction in local mode When the deployment keeps data on the user's machine, original values can be restored for authorized review instead of destroyed, which matters for audit and debugging workflows.[1]

• One integration for 20+ providers OpenAI, Anthropic, Google, Mistral, xAI, DeepSeek, and Ollama for local models all sit behind the same gateway, so adding a provider rarely means rewriting application code.[1]

• Drop-in proxy for OpenAI and Anthropic code Existing calls migrate by pointing the client at the gateway endpoint, keeping the request and response shapes teams already use.[1]

• TypeScript-first SDK with Zod validation Typed helpers wrap OpenAI and Anthropic clients, and input validation catches malformed calls before they cost tokens.[1][2]

• Prompt versioning with six evaluation templates Accuracy, relevance, toxicity, bias, PII leakage, and hallucination scores run against versioned prompts, giving teams a repeatable check before and after changes.[1]

• Single-file rules with stop-light checks All policy lives in one rules file, and built-in checks report red or green status with remediation commands when something is misconfigured.[1]

• Local SQLite or EU-hosted cloud operation Local mode stores traces on the user's machine, while cloud mode keeps encrypted redacted traces in the EU with a zero-data option for teams that want nothing retained.[1][2]

Who will love it

• Teams sending sensitive data through LLM APIs: PII detection plus redaction in the request path, reversible in local mode, directly addresses the leak class that blocks regulated and enterprise LLM adoption.[1][2]

• TypeScript shops centralizing provider traffic: the SDK, Zod validation, and drop-in proxy match a stack that already runs on TypeScript and Bun, keeping the gateway close to application code.[1][2]

• Privacy-constrained self-hosters: AGPL-3.0 licensing, local SQLite mode, EU trace storage, and a zero-data option let teams keep prompts inside their own boundary or a documented EU one.[1][2]

Who should avoid it

• Non-technical builders working alone: rules files, SDK wiring, CLI scaffolding, and Docker or Bun operation all assume engineering skills, and there is no click-only studio in this product.[1][2]

• Teams wanting a proven managed gateway with support terms: the managed tiers exist, but the project counts 10 repository stars, and support terms and SLAs are unpublished, so anyone buying operational certainty should wait for evidence.[1][2]

• Single-provider prototypes: when one application calls one model directly, a gateway adds configuration and moving parts without a payoff. Revisit Grepture when a second provider, a redaction requirement, or an evaluation need appears.[1][2]

Reported experience

Alternatives and compatibility