Deployment & security
Two ways to run Presponsieve
Let us host it for you, or run it on your own infrastructure. It is the same product with the same reports either way — the only difference is where it lives and who looks after it.
Not sure which fits? Tell us about your team and your security requirements and we will recommend one — see Pricing to get started, or go back to the Home page.
Common questions
Choosing
What is the difference between the two?
Only where it runs. Hosted, we run it for you and you sign in from your browser. Self-hosted, your own IT team runs it inside your company's systems. The features and the reports are the same.
Does any of our data reach you?
Hosted: your data is stored on our secure cloud service so we can run it for you — encrypted, kept separate from every other customer, and never sold or used to train AI. Self-hosted: no. Nothing you put through it ever reaches us.
Hosted by us: how we keep your data safe
Is our data encrypted?
Yes, always. It is encrypted on its way to us and while it is stored, using AES-256 — the same standard banks use. Each organisation has its own encryption key.
Can other customers see our data?
No. Every organisation's data is kept separate and locked with its own key. Inside your organisation, people see only what their role allows.
How do people sign in?
With your company login (single sign-on) or a verified email address. Two-step verification is required for every account, and sessions sign out automatically after a period of inactivity. Remove someone from your organisation and their access ends straight away.
Is our data used to train AI?
No. We do not use your conversations, profiles or reports to train AI models, and the AI providers we work with are not allowed to either.
Is the service protected from attacks?
Yes. It runs on Google Cloud behind a web application firewall that blocks common attacks and limits suspicious traffic. Sign-ins and key actions are recorded in an audit log.
Can we delete our data?
Yes. You can delete any profile at any time. If you leave, we can destroy your organisation's encryption key, which makes everything stored for you permanently unreadable.
Can you fill in our security questionnaire?
Yes — start it with us on the first call and we will walk your security team through how the service is protected.
Self-hosted
What does it need from our infrastructure?
A Kubernetes cluster, a Postgres database and somewhere to run the model. We go through sizing with you before anything is signed, because it depends on the model and on how many people are using it at once.
Can we run it air-gapped?
Yes. Mirror the container image into your own registry, install the chart and set the licence key. With the revocation check unreachable the licence simply runs to its expiry.
Where do we get the install instructions?
With your licence. The self-hosting guide — the Helm chart, the configuration reference and the deployment walkthrough — goes to customers while we finish the self-service install, so it is not published openly yet. Your key, the public key to verify it against and the credentials for the guide are waiting on your dashboard.
Self-hosted: details for your IT team
Only relevant if you run Presponsieve yourself.
- Where it runs
- A Kubernetes cluster you control, installed with our Helm chart. Any cloud, or your own hardware.
- Who operates it
- You do. We do not have access to your cluster, and there is no agent or tunnel that gives us any.
- Upgrades
- A new chart version you roll out when it suits you. Nothing updates itself underneath you.
- Egress
- Optional. A periodic licence check that sends one opaque licence id is the only call that ever leaves your network, and it can be blocked outright.
- Licensing
- A signed
LICENSE_KEYverified locally with Ed25519, so no network call is needed. Revocation is the optional check above; Renewal re-signs the same licence with a new expiry, with nothing to redeploy. - Seats
- A seat is one person on your team who can sign in to your deployment. The count is carried in the licence and enforced by the app you run.
- End of term
- The licence stops verifying at its expiry and the app stops unlocking the engine on its next check. Nothing is deleted; your data stays where it already is.
- Data protection
- We are not a processor of the content you put through a self-hosted deployment, so a DPA covering conversation data has nothing to cover.
Ask us directly — email sales@presponsieve.ai, or start a conversation from Pricing and we will get the right person on it.