Sub-processors
Effective 30 October 2026
Valitura uses the companies below to provide Akesis. Each processes customer data only to provide its part of the Service, under a written agreement with data-protection terms at least as protective as our Data Processing Agreement.
| Company | What it does for Akesis | Customer data it processes | Where |
|---|---|---|---|
| Neon, Inc. | Database: stores all customer data | All data held in Akesis | United States (AWS us-east-2) |
| Hostinger International Limited | Application hosting: runs the Service | All data, in transit while requests are served; request logs with IP addresses | United States |
| Amazon Web Services, Inc. | Amazon Bedrock, for AI risk narratives, only when AI features are on for your organisation | Facts Akesis already holds about a finding (advisory text, package, versions, status); never source code | Your organisation's region: the United States, or the EU for EU organisations |
All stored data is in the United States today. EU data storage is coming soon; contact us if you need it.
Not our sub-processors
- Services you connect, such as GitHub, GitLab, Bitbucket, Snyk, Jira, Slack, Sentry, your monitoring tools, your identity provider, your AI assistants and the endpoints you send webhooks to, are your own providers. Akesis exchanges data with them at your direction, under your agreements with them.
- Public data sources Akesis queries for vulnerability information receive only public identifiers (such as CVE IDs and package names), never customer or personal data: FIRST (EPSS), CISA (KEV), NVD, OSV, the npm, PyPI, Go and crates.io registries, Sigstore, Red Hat, Microsoft, Palo Alto Networks and Cisco.
Changes
We give at least 30 days' notice before adding or replacing a sub-processor, by updating this page and emailing each customer organisation's admins. You may object within that period on reasonable data-protection grounds, as set out in the Data Processing Agreement.
| Date | Change |
|---|---|
| 30 October 2026 | First published |