Security at HIPS
HIPS runs every request in one of two pools. If you are unsure, choose the Certified pool.
Certified pool
Recommended if you are unsureThe safe route. Every facility is certified by HIPS's compliance team and stores none of your data, and HIPS guarantees that certification for every request here.
- Use it for
- Anything sensitive: personal data (PII), customer conversations, business data, source code
- Who runs the GPUs
- Facilities that HIPS's compliance team has certified
- Who can see your data while it is processed
- Nobody outside the certified facility
- Prices
- The normal prices
- Coding agents and tool calls
- Always here
Community pool
For work where you just need GPUs. Very reliable, because there are thousands of GPUs that can process your request.
- Use it for
- Work that holds nothing sensitive, such as a chat for fun with no personal data
- Who runs the GPUs
- Independent GPU owners, on their own machines
- Who can see your data while it is processed
- In theory the GPU's owner
- Prices
- A lower price
- Coding agents and tool calls
- Never here
In both pools: nothing stored, logged or trained on, and you can keep a request in one region, for example only the EU or only the US.
A request that names no pool, on a key that names none, runs under Auto, in either pool. To keep it in the Certified pool, name it (Set the pool).
Certifications
HIPS is PCI DSS Level 1, ISO/IEC 27001 and SOC 2 certified.
Find your work under its pool. Each one opens the guide on Choose a pool for your data with the reason and the code.
Certified pool
Recommended if you are unsureFor anything sensitive, at the normal prices.
- Not sure yetThe Certified pool. We always recommend it if you are unsure.
- A coding agentThe Certified pool, always, because of the risk of prompt injection.
- An app that sends tool callsThe Certified pool, always: every request that can act runs only there.
- Customer support chatThe Certified pool: customer conversations hold personal data (PII).
- Business documents or source codeThe Certified pool: any sensitive business data at all goes there.
- Documents with sensitive content (RAG)The Certified pool, so only its GPUs read the passages.
Community pool
For work that holds nothing sensitive, at a lower price.
- A chat for funThe Community pool, for a lower price: nothing in it is sensitive.
- Public content or test dataThe Community pool, for a lower price: nothing in it is sensitive.
- Image generationThe Community pool, for a lower price, when the prompts hold nothing sensitive.
- Text-to-speech or speech-to-textThe Community pool, for a lower price, when what you send is not sensitive.
- Classifiers and ONNX modelsThe Community pool, for a lower price, when the items hold nothing sensitive.
| Certified pool | Community pool | |
|---|---|---|
| Use it for | Anything sensitive: personal data (PII), customer conversations, business data and source code, coding agents, and whenever you are unsure | Work that holds nothing sensitive: a chat for fun with no personal data, or low-cost inference on data that is not sensitive |
| Prices | The normal prices | A lower price |
| Who runs the GPUs | Facilities that HIPS's compliance team has certified | Independent GPU owners, on their own machines |
| Before it carries a request | Certified by HIPS's compliance team: the facility has passed ISO/IEC 27001 and SOC 2 audits and meets HIPS's own zero-storage requirement | Enrolled and checked by HIPS; not a certified facility |
| Who can see your data while it is processed | Nobody outside the certified facility | In theory the GPU's owner, and HIPS cannot guarantee otherwise (What a Community pool provider can see) |
| Coding agents and tool calls | Always here | Never: HIPS does not offer coding-agent models here |
| One region | Keep a request to one region, for example only the EU or only the US | The same |
- Use it for
- Certified pool
- Anything sensitive: personal data (PII), customer conversations, business data and source code, coding agents, and whenever you are unsure
- Community pool
- Work that holds nothing sensitive: a chat for fun with no personal data, or low-cost inference on data that is not sensitive
- Prices
- Certified pool
- The normal prices
- Community pool
- A lower price
- Who runs the GPUs
- Certified pool
- Facilities that HIPS's compliance team has certified
- Community pool
- Independent GPU owners, on their own machines
- Before it carries a request
- Certified pool
- Certified by HIPS's compliance team: the facility has passed ISO/IEC 27001 and SOC 2 audits and meets HIPS's own zero-storage requirement
- Community pool
- Enrolled and checked by HIPS; not a certified facility
- Who can see your data while it is processed
- Certified pool
- Nobody outside the certified facility
- Community pool
- In theory the GPU's owner, and HIPS cannot guarantee otherwise (What a Community pool provider can see)
- Coding agents and tool calls
- Certified pool
- Always here
- Community pool
- Never: HIPS does not offer coding-agent models here
- One region
- Certified pool
- Keep a request to one region, for example only the EU or only the US
- Community pool
- The same
Set the Certified pool once on your client, and every request it sends runs there:
import osfrom openai import OpenAI client = OpenAI( api_key=os.environ["HIPS_API_KEY"], base_url="https://ai.hips.com/v1", # Sensitive data, or not sure: the Certified pool default_headers={"x-hips-pool": "certified"},)result = client.chat.completions.create( model=os.environ["HIPS_MODEL"], messages=[{"role": "user", "content": "Summarize this customer's last three orders."}],)print(result.choices[0].message.content)A request that names no pool, and whose key names none, runs under Auto: wherever HIPS has capacity for the model now, in the Certified or the Community pool (Pools). To be sure a request stays in the Certified pool, name it. Every way to set it is on Choose a pool for your data.
Because of the risk of prompt injection, every coding agent runs in the Certified pool, always. HIPS never sends a request that can act, a coding agent's or one with tool calls, to the Community pool, and does not offer coding-agent models there. Read Coding agents and prompt injection.
HIPS does not store, log or train on your prompts and answers, on any plan, in either pool. The one thing that may ever be held is a prompt cache: temporary, in GPU memory, never on disk. Read What HIPS stores.
A Community pool provider never learns who sent a request, and before a request reaches a GPU a provider owns, HIPS recognizes and redacts API keys, tokens, private keys and the values of environment variables in its text. There is encryption, there is attestation, and there are thousands of tests, all to make sure a provider cannot access your data and cannot inject anything. In the Community pool none of it can be guaranteed: the GPUs are out in the wild, as with anything on the internet. The Certified pool is the one HIPS can fully certify. Read What a Community pool provider can see.
- Choose a pool for your dataYour pool, the reason and the code, by kind of workOpen
- Coding agents and prompt injectionWhy every coding agent runs in the Certified poolOpen
- What a Community pool provider can seeWhat reaches a provider's GPU, and what never doesOpen
- What HIPS storesNothing you send, with one temporary exceptionOpen
- Knowledge and RAG dataWhere your documents live and what a model receivesOpen
- GuardrailsDetect prompt injection and mask sensitive informationOpen
Related sheets
- Sheet
- 03 of 21
- Updated
- 2026-11-18