Governance
Use GPT without sending customer data
Your support assistant runs on a US model, but names, emails and IBANs stay out. The answer comes back with the real values.
Comes back: The model's answer, with the real names back in place.
AI workflows for developers
Block a prompt injection, pull an order number from an email, strip the personal data, then hand the clean prompt to your model. One request, billed per character, EU-only.
Early access opens in batches. Every account starts with 1M characters free each month.
# Needs jq. Set MESSAGE to the text to send.
jq -n --arg input "$MESSAGE" '{
"input": $input,
"detect": ["pii.entities", "secrets.credentials"],
"transform": [
{ "op": "pii.tokenize", "when": ["detect.pii.entities:flagged"] },
{ "op": "secrets.redact", "when": ["detect.secrets.credentials:flagged"] }
],
"relay": { "provider": "openai", "model": "gpt-4.1-mini" }
}' | \
curl -X POST https://api.chersus.com/v1/run \
-H "Authorization: Bearer $CHERSUS_KEY" \
-H "X-LLM-Key: $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d @-| A big LLM | Your own small models | Chersus | |
|---|---|---|---|
| You pay | Tokens, for every job | GPUs, busy or idle | Characters in and out |
| Speed | A general model thinks it over | Fast, once warm | Super fast, always warm |
| Who sees your text | The model provider | You | Chersus, in the EU, keeping none of it |
| Who operates it | The provider's staff | Your people, on call | We do |
Governance
Your support assistant runs on a US model, but names, emails and IBANs stay out. The answer comes back with the real values.
Comes back: The model's answer, with the real names back in place.
Security
Web pages, emails and documents can hide instructions for your agent. They are blocked before the text reaches the prompt.
Comes back: A block, before the page reaches your agent's prompt.
Data
Log lines and tickets reach your warehouse or monitoring tool without names, emails or keys.
Comes back: The same log line, minus names, emails and keys.
Content
Tickets reach the right team by language and topic, without keyword rules, and without personal data in storage.
Comes back: The language and the topics, ready to send to the right team.
/v1/run, with the steps you want.Nothing leaves your browser.
A verdict and a score. Personal data, credentials, prompt injection, jailbreaks, hate, abuse and threats.
A value. Language, fields, title, description, topics and emoji.
Rewritten text. Redact or tokenize personal data, redact credentials.
The model call. Your model gets the clean prompt; your user gets the real names back.
European models, running on EU infrastructure in 26 cities. Chersus processes your text there and keeps none of it. With your own key, the provider you relay to is your processor, not ours.
Combine any operations. You pay for the text you send and the text you get back.
Every operation runs on a small model built for one job, not a general model that thinks it over. Try it on your own traffic in early access.
Only what you let through. A tokenize step swaps personal data for placeholders before the prompt leaves, and relay puts the real values back in the answer. Detection is statistical, so treat it as a strong filter, not a guarantee.
It depends on the operation: personal data in 27, language detection in 84, topics in 101. Each operation lists its own.
No. Take the clean text and the token map, call your model yourself, and put the values back. Relay does all of that in one request.
Chersus processes it in the EU and keeps no content after the request. The audit trace holds hashes only. With relay, the prompt also goes to the model you named.
Access opens in batches. Request yours, get your key, and start with 1M characters free every month.