Partners
Building on the index without rebuilding it
Vendors, integrators, managed service providers: three ways to bring in an archive depth nobody can rebuild.
Three routes
Plug it in, resell it, embed it
The same index, three different contracts. What changes is not the data but who talks to the end client.
The Aleph index
Continuous collection since 2012, timestamped
01
Plug it in
Connectors and standard output: the index lands in a platform that already exists.
02
Resell it
White-label deliverable and per-client isolation, to carry it under your own name.
03
Embed it
An anteriority variable that feeds a score you already compute.
In all three cases, the collection, the timestamping and the legal framework stay ours. What changes is who talks to the end client — and that is exactly what the contract sets out.
The three routes are not exclusive: an integrator who resells can also plug the index into its own platform.
Who this is for
Three profiles, three expectations
Vendors & platforms
OpenCTI, MISP and Sekoia connectors, STIX 2.1 output, API access. Documentation, not a pitch.
MSSPs & integrators
White-label deliverable and per-client isolation, to carry the service under your own name.
Scoring & models
An anteriority variable feeding a score you already compute, with no exclusivity.
What is settled
What a partnership agreement sets out
- 01The redistribution scope: who your end client may pass on what they receive, and in what form.
- 02Source attribution and preservation of timestamps, without which a dated element loses what makes it valuable.
- 03The legal framework of the collection, which stays ours and which you can put forward to your own client.
- 04Service levels and commercial terms, discussed according to volume and the form of integration.
Talk integration
Tell us what you produce for your clients today: we will tell you which of the three routes plugs in fastest.