PRISM
The sanitised LLM gateway.
PRISM sits between your agents and every language model — cloud or local. Every prompt is scanned for PII, developer secrets, and prompt injection before it leaves your perimeter, while responses are logged with live spend tracking.
Private Cluster Development ReleaseActive Evaluation
Automated NER redaction models and JIT proxy endpoints are undergoing private enterprise security audits. Gated access is provisioned on request.
Dual-Layer Redaction Pipeline
Raw agent prompts never reach public cloud APIs unmodified. PRISM strips confidential customer data and developer credentials before requests cross the cluster perimeter, replacing them with deterministic pseudonyms.
“Process refund for user John Doe (SSN: 482-19-4821, Card: 4111-2948-2941-8492). Connect to internal database via postgres://admin:secret99@192.0.2.100:5432”
“Process refund for user <TOKEN_USER_01> (SSN: <TOKEN_SSN_01>, Card: <TOKEN_CC_01>). Connect to internal database via <TOKEN_DB_URI_01>”
Customer & Personal Identifiers (PII)
Social Security Numbers, Credit Cards, Medical Record Numbers, Full Names, Home Addresses
Developer Secrets & Credentials
AWS Access Keys, GitHub PATs, JWT Tokens, SSH Keys, Database Passwords
Internal Network Infrastructure
Internal IP addresses (10.x, 192.168.x), Cluster Node Hostnames, VPC Subnets
Proprietary Trade Secrets
Proprietary Algorithm Weights, Customer Tenant IDs, Internal Financial Projections
Prompt Injection & Jailbreak Defense
Untrusted web scrapes and external payloads often contain adversarial prompts designed to hijack autonomous agents. PRISM scans prompts prior to model dispatch.
Flags phrases such as “Ignore previous instructions”, “System override”, and persona switching attacks before token ingestion.
Decodes and evaluates Base64, hex, and unicode obfuscated payloads concealed inside scraped web pages or PDF documents.
Flagged malicious requests are blocked immediately at the gateway layer (HTTP 403), consuming zero third-party model tokens.
Zero Stored Provider Keys
PRISM stores zero OpenAI, Anthropic, or Gemini API keys in its environment or on disk. When an LLM request arrives, PRISM requests a Just-In-Time lease from lvls. The key is delivered via ML-KEM-768 post-quantum transport, used in RAM for the single request, and purged immediately.
Real-Time Budget & Spend Enforcement
Preventing runaway autonomous loops. PRISM enforces hard monetary spend ceilings per task, per agent, and per day. Requests are blocked before overspend can occur.
Explore the full platform
Five integrated components. One unified system.