Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
Sheet indexSecurity

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
03
  1. Docs/
  2. Security
llms.txt

Security at HIPS

On this sheet7 sections
  1. Which pool for your work
  2. The full comparison
  3. Set the pool in one line
  4. Coding agents always run in the Certified pool
  5. Zero storage, in both pools
  6. What protects you in the Community pool
  7. Read more

HIPS runs every request in one of two pools. If you are unsure, choose the Certified pool.

Certified pool

Recommended if you are unsure

The 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.

Which pool for your work

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 unsure

For 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.

The full comparison

Certified poolCommunity pool
Use it forAnything sensitive: personal data (PII), customer conversations, business data and source code, coding agents, and whenever you are unsureWork that holds nothing sensitive: a chat for fun with no personal data, or low-cost inference on data that is not sensitive
PricesThe normal pricesA lower price
Who runs the GPUsFacilities that HIPS's compliance team has certifiedIndependent GPU owners, on their own machines
Before it carries a requestCertified by HIPS's compliance team: the facility has passed ISO/IEC 27001 and SOC 2 audits and meets HIPS's own zero-storage requirementEnrolled and checked by HIPS; not a certified facility
Who can see your data while it is processedNobody outside the certified facilityIn theory the GPU's owner, and HIPS cannot guarantee otherwise (What a Community pool provider can see)
Coding agents and tool callsAlways hereNever: HIPS does not offer coding-agent models here
One regionKeep a request to one region, for example only the EU or only the USThe 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 pool in one line

Set the Certified pool once on your client, and every request it sends runs there:

00000000000000000000000000000000000000001import os2from openai import OpenAI3 4client = OpenAI(5    api_key=os.environ["HIPS_API_KEY"],6    base_url="https://ai.hips.com/v1",7    # Sensitive data, or not sure: the Certified pool8    default_headers={"x-hips-pool": "certified"},9)10result = client.chat.completions.create(11    model=os.environ["HIPS_MODEL"],12    messages=[{"role": "user", "content": "Summarize this customer's last three orders."}],13)14print(result.choices[0].message.content)
Reads from the environmentHIPS_API_KEYHIPS_MODEL

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.

Coding agents always run in the Certified pool

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.

Zero storage, in both pools

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.

What protects you in the Community pool

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.

Read more

  • PATH 01Choose a pool for your dataYour pool, the reason and the code, by kind of workOpen
  • PATH 02Coding agents and prompt injectionWhy every coding agent runs in the Certified poolOpen
  • PATH 03What a Community pool provider can seeWhat reaches a provider's GPU, and what never doesOpen
  • PATH 04What HIPS storesNothing you send, with one temporary exceptionOpen
  • PATH 05Knowledge and RAG dataWhere your documents live and what a model receivesOpen
  • PATH 06GuardrailsDetect prompt injection and mask sensitive informationOpen
  • Vulnerability Disclosure Policy

Related sheets

  • Data handling
  • Security and Data
Previous sheetQuickstart
Next sheetChoose a pool for your data
Sheet
03 of 21
Updated
2026-11-18
Sign in to the Console

On this sheet

  1. Which pool for your work
  2. The full comparison
  3. Set the pool in one line
  4. Coding agents always run in the Certified pool
  5. Zero storage, in both pools
  6. What protects you in the Community pool
  7. Read more

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ