Deployment & security
The detail your IT team will ask for
Presponsieve Lite runs on infrastructure you control. This page is the technical half of that promise — where it runs, what licensing does, and exactly what leaves your network. If you are still deciding whether it is for you, the overview is the better place to start.
Running it
- Where it runs
- A Kubernetes cluster you control, installed with our Helm chart. Any cloud, or your own hardware.
- Footprint
- One deployment plus a Postgres database. Sizing depends on the model you run and how many people use it at once — we size it with you before you sign.
- 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.
How licensing works
- The key
- A signed
LICENSE_KEYcarrying your seat count, capabilities and expiry. Your deployment verifies it againstLICENSE_PUBLIC_KEYwith Ed25519, locally. - Offline
- Verification needs no network call, so an air-gapped cluster works.
- Revocation
- Your deployment periodically asks
licenses.presponsieve.ai/validatewhether one opaque licence id is still good. Nothing else is sent, and the check is optional — block it and the software keeps running until the licence expires. - Renewal
- We re-sign your existing licence with a new expiry. Same key id, same capabilities, nothing to redeploy and no downtime.
- Seats
- A seat is one person using the app in 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 and egress
- What we receive
- One opaque licence id, on the periodic revocation check. No conversation text, no profiles, no user data, no telemetry.
- Where conversations are processed
- Inside your cluster, by the model you run there. They never traverse our network.
- Egress
- Optional. The revocation check is the only call that ever leaves your network, and it can be blocked outright.
- Data protection
- Because we are not a processor of the content you put through it, a DPA covering conversation data has nothing to cover. We are happy to walk your privacy team through exactly that on a call.
Technical FAQ
Does any of our data reach you?
No. The engine runs entirely inside your cluster. The only thing that ever talks to us is a periodic licence check that sends one opaque licence id and gets back whether it has been revoked — no conversation text, no profiles, no user data.
What happens if our cluster is offline?
It keeps working. Licences are signed with Ed25519 and verified locally against a public key baked into your deployment, so no network call is needed to validate one. The revocation check is an optional extra on top.
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.
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.
How is the licence enforced?
The app verifies the signature on your key, reads the seat count and capabilities from it, and unlocks the engine accordingly. An expired or revoked licence stops the engine unlocking on its next check — it does not touch your data.
Where do we get the install instructions?
In the self-hosting guide, alongside the Helm chart and the configuration reference. Your key and the public key to verify it against are waiting on your dashboard.
Can we get a security review, pen-test report or questionnaire filled in?
Yes — start it with us on the first call. Because the software runs inside your perimeter and we hold none of your data, most questionnaires get shorter rather than longer.
Ask us directly — email sales@presponsieve.ai, or start a conversation from pricing and we will get the right person on it.