Companies / Riftmap / Subprocessors
Riftmap parses infrastructure dependencies from a GitLab or GitHub org to show which repositories are affected by changes to shared base images, Terraform modules, or Helm charts. It serves engineering organizations whose cross-repo dependencies span Docker, Terraform, Kubernetes, Helm, Ansible, Python, Go, and npm.
Summarized from its homepage on 14 Nov 2026.
Subprocessors of Riftmap
Riftmap declares 7 subprocessors.
| Subprocessor | Purpose |
|---|---|
| Structured log aggregation | |
| Marketing-site hosting (Cloudflare Pages), DNS, TLS termination, bot management, and reverse-proxy execution for analytics ingestion. | |
| Product and marketing analytics (riftmap.dev and app.riftmap.dev) — page views and named product events on both, plus autocaptured interactions and optional session replay on the marketing site only. In the app, after sign-in, events are associated with your account (user ID, email, name). Client-side capture is consent-gated (no data before consent); a small set of server-side conversion events (subscription_started, OAuth signup_completed) is sent under legitimate interest. | |
| Application and database hosting | |
| Transactional email delivery | |
| Error monitoring and crash reporting | |
| Payment processing and subscription management |
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See Riftmap's full stack
Every vendor with its source and date, and an alert when Riftmap adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call