Deploy
On-prem overview
When to run TheSpider on your own infrastructure
The public onboarding is Cloud. There is a separate on-prem edition if you need to run the server yourself: data residency, a private network, or no internet egress.
This page is for the decision, not the install. Images, licenses, and operator docs go to authorized customers privately.
Cloud vs on-prem
| TheSpider Cloud | On-prem | |
|---|---|---|
| Who runs the server | TheSpider | You (or a partner) |
| Tenancy | Multi-tenant, org isolation | Single-tenant |
| App | Hosted | Docker Compose or Kubernetes |
| Database and artifacts | We run them | Your Postgres and filesystem or S3 |
| Where models run | Your agent hosts | Your agent hosts |
| Model providers | Your local CLIs | Cloud, private, or local endpoints |
| Network | Agent talks to thespider.xyz | Private network or air-gap |
| Entitlements | Organization plan | Signed license |
| Price | Free / Pro $49/mo / Business $149/mo | Business yearly: $1,490/year |
What does not change
thespider-agentstill runs models on the machine with the checkout.- TheSpider still does not upload the source tree.
- Campaigns, findings, triage, retests, and the PR gate work the same.
How people usually deploy it
- Docker Compose on one host with disks you manage.
- Kubernetes when that is already how you run things.
- Air-gapped with internal models and optional outbound integrations left off.
Same numbers as Cloud Business: 50 seats, 50 projects, 50,000 slice claims, AI dedupe (your key), OIDC SSO.
Pay the yearly Business price, then a license JWT is minted for the instance. Public Cloud users should follow the Cloud quickstart. Do not clone this repository as an on-prem substitute.
Data-flow details that apply to both editions: Data handling.