CTP247PRE-LAUNCH

Coming soon.

CTP247 is cyber threat protection that never clocks out — autonomous agents watching your attack surface, brand, and the dark web 24/7. Leave your email and we'll let you know when it's live.

One email at launch. No newsletters, no marketing dripfeed.

CTP247

Trust

Your data,
your perimeter.

CTP247 is a security tool deployed by security teams. We designed it the way we'd want one in our own environment — minimal blast radius, plain Postgres, zero telemetry, audit-everything.

Self-host by default

CTP247 ships as a Compose stack. Your VPC, your S3, your Postgres. We have no production access to your data and no telemetry calling home.

BYO LLM

Set ARGUS_LLM_PROVIDER to Ollama (fully local), Anthropic, or any OpenAI-compatible endpoint. Keys stay inside your deployment — env vars, or encrypted at rest in your own Postgres when entered via the admin panel.

Encryption where it counts

TLS terminates at your reverse proxy or ingress — you choose versions and ciphers. Postgres at rest under your managed encryption (RDS / Cloud SQL / disk). Connector keys entered in the admin panel are encrypted at rest.

RBAC + audit

Role-based access — admin / analyst / viewer — enforced per endpoint, with secure-cookie session auth and an append-only audit log. No 'one shared password' config. SAML/OIDC SSO is not in the box today; say so out loud because vendors usually don't.

Auditable agents

Every LLM call logs the prompt, the model, the cost, and the resulting tool calls. The audit log is append-only Postgres rows you own.

Retention you control

Per-table retention windows. Default 90d for raw intel, 365d for alerts, indefinite for cases. Configurable in admin settings.

Deployment topology

One container plane. Outbound is opt-in.

The default install runs entirely inside your VPC. Outbound connections are limited to the feeds you explicitly enable (abuse.ch, dshield, etc.) and the LLM provider you chose. No hidden phone-home, no analytics SDKs.

  • Single Docker Compose stack — api, worker, scheduler, postgres, redis, minio, tor; the dashboard runs alongside via start.sh
  • Helm chart for Kubernetes — full backend stack on any CSI-capable cluster
  • All inter-service traffic over the Docker network — no Internet hop required
  • Egress allowlist: the feed sources you enable + your LLM provider
$ ./start.sh
argus-postgres-1 Started
argus-redis-1 Started
argus-tor-1 Started
argus-meilisearch-1 Started
argus-minio-1 Started
argus-api-1 Started · http://localhost:8000
argus-worker-1 Started
argus-scheduler-1 Started
Health: healthy · 8/8
Egress: feeds + llm only

Sub-processors

Short list. Honest list.

Anyone CTP247 ships data to is on this page. If we add one, we update this page first.

ProviderPurposeRegionNotes
Anthropic / OpenAI-compatible LLM APIsLLM inference (chosen by you, optional — Ollama keeps it fully local)ConfigurableYou provide the API key; CTP247 routes prompts through your account. We never see the request payloads.
ResendTransactional email (demo requests, waitlist)EU / USOnly fired from this marketing site. Not used in your self-hosted deployment unless you wire it up.
VercelMarketing site hosting + CDN (ctp247.com)GlobalMarketing site only. Never touches your application traffic.

Security questions?

Architecture, data flows, retention, threat model — ask us directly and we'll answer in writing. The codebase is the documentation; we'll walk you through any part of it.

cto@gaigentic.ai