Edge Collector.
An on-prem appliance that runs Anoman's guardrails and reversible PII masking inside your own network. Prompt injection detection and PII anonymization happen on your infrastructure — only metadata telemetry, never raw prompt or response content, phones home to Anoman.
How it works
Guardrails run on your infrastructure, not ours
Your app → request sent to the Collector, inside your VPC
→ [COLLECTOR — on your infrastructure]
1. Prompt injection scan (on-device ML detector)
2. PII anonymize (NIK, NRIC, email, phone, credit card & more)
↳ blocked? Rejected locally — never forwarded, never billed.
→ thin forwarder sends the anonymized request to your LLM provider
→ provider response returns
→ [COLLECTOR] de-anonymize — real PII values restored
→ response returned to your app
↳ Raw prompts and PII never leave your network. Only metadata telemetry (counts, latency, guardrail triggers, license heartbeat) phones home to the Anoman control plane over mTLS.
Capabilities
What runs on your infrastructure
On-prem / in-VPC deployment
A distroless container appliance you run inside your own network or VPC — not a hosted proxy. It sits between your app and the LLM provider, on infrastructure you control.
Local guardrails
On-device prompt-injection detection and PII masking — including Indonesian NIK and Singapore NRIC — run locally on the appliance, before any request leaves your network.
Reversible PII anonymization on-prem
The same anonymize-then-de-anonymize round-trip as Anoman's cloud guardrails, but executed entirely on your infrastructure — the model sees synthetic values, your app gets the real ones back.
Metadata-only telemetry
Only operational metadata — request counts, latency, guardrail trigger counts, license heartbeats — is sent to the Anoman control plane. Raw prompt and response content never leaves your network.
Centrally governed
RS256-signed licensing and a signed policy-bundle sync keep the appliance governed from your Anoman control plane over mTLS — so signature and policy updates roll out without any customer content changing hands.
Distroless & lightweight
Built as a minimal distroless image with a thin, non-streaming LLM forwarder and SQLite-backed local audit log — designed to run alongside your app, not as a heavyweight platform.
Residency, two ways
Regional residency today. On-prem residency with Edge Collector.
These are two different, complementary guarantees — don't confuse them. Most customers only need the first.
Regional residency
Anoman's standard SaaS gateway runs in a Jakarta data center. Prompts, completions, traces, and usage data are stored and processed in-region, for UU PDP readiness. This is Anoman's default mode of operation — no extra setup required.
See regional data residency →On-prem residency
The Edge Collector goes a step further: your raw prompts and responses never leave your own network at all — guardrails and PII masking run on your infrastructure, and only metadata telemetry is sent to Anoman. Onboarded with our team as an Enterprise early-access capability.
Request early access →FAQ
Common questions
Where does my data go?
Your prompt is processed entirely inside your own network by the Edge Collector — injection scanning and PII anonymization happen on your infrastructure before the request is forwarded to your chosen LLM provider. Raw prompt and response content is never sent to Anoman's control plane.
What leaves my network?
Only metadata telemetry — things like request counts, latency, guardrail trigger counts, and licensing heartbeats over mTLS. No raw prompt text, no PII, and no completion content is ever transmitted to Anoman.
Which PII does it detect?
The same PII engine used in Anoman's cloud gateway: email, phone, credit card, IP address, URL, Indonesian NIK, and Singapore NRIC — with reversible anonymize-then-de-anonymize round-tripping, all running on-prem.
How is it kept up to date and governed?
Licensing is enforced with an RS256-signed license, and guardrail policy is synced from your Anoman control plane as a signed policy bundle over mTLS — so a signature or policy update rolls out to your appliance without you shipping data anywhere.
Is it self-serve?
Not yet. The Edge Collector is an early-access Enterprise capability, onboarded with our team rather than a self-serve download. Streaming responses are not supported in this phase — request/response calls only.
Keep your prompts on your own infrastructure.
The Edge Collector is an Enterprise early-access capability, onboarded with our team.