Start with a defined problem.
COSRYX builds verifiable mission intelligence for space: every command, decision and health record a spacecraft or rover produces becomes evidence a third party can check later.
We work with universities, laboratories, mission teams and institutions on written scopes: who owns the data, who decides, what may be claimed, and how success is measured.
Small, written, and checkable.
COSRYX software is built and internally tested. The next steps, an external audit, radiation testing and work with real telemetry, all need people outside DCS Labs. That is where partners come in.
Every collaboration begins with a written scope and a research status. Results from a partnership carry the same labels as everything else on this site: simulated, ground-demonstrated or tested, never more than the evidence supports.
We do not list partners, show logos or describe a relationship in public unless the partner has approved it in writing.
Six ways to work together.
Research collaboration
Joint questions, publications, datasets, experiments and validation with universities and laboratories.
Mission study
Bounded analysis of communications, autonomy, planning, planetary conditions or operational intelligence for a named mission concept.
Technology evaluation
A controlled assessment of COSRYX-LENS, COSRYX-WATCH, COSRYX-MCC, COSRYX-EDGE, DSRP or the R-Series receipt layer against your requirements.
Pilot programme
A defined scope, approved data, success criteria, human oversight and an explicit research status from the first day.
Academic network
Student research, internships, seminars, datasets and collaborative technical writing.
Government and institutional
Secure, governed discussions for public research, mission support and strategic capability studies.
Know where your cryptography lives before you migrate it.
A post-quantum readiness assessment using the PQ-Agility platform, the most mature pilot we offer today.
- Cryptographic inventory (CBOM): where each algorithm, key and certificate is used.
- Policy evaluation: which uses meet your chosen post-quantum policy, and which do not.
- Deprecation calendar: when each classical algorithm should be retired.
- Migration roadmap: an ordered plan, starting with the systems that matter most.
Aligned with the published timelines of US CNSA 2.0, the European Union and India's National Quantum Mission. PQ-Agility: 109 tests in that population, including X-Wing (IETF draft; implemented and tested with the draft vectors, not yet deployed) and CBOM 11 of 11.
A written assessment, not a certificate
An inventory, a policy evaluation, a deprecation calendar and an ordered migration plan, each finding labelled with how it was checked. PQ leg of COSRYX receipts: ML-DSA-65 (FIPS 204) via the R-Series engine; software key custody; not flight-qualified.
From first email to a written result.
A defined problem
You write to research@cosryx.com with the question, the system and the decision the answer would inform.
A written scope
Data ownership, confidentiality, named technical and decision owners, and what each side may say in public.
Success and stop criteria
How results are measured, what counts as failure, and when either side may end the work.
The work, receipted
Runs are recorded as signed receipts, so either party can check the record later without trusting the other.
A labelled report
Results, uncertainty and limits, with every count tied to its population, and simulation kept separate from real data.
Scope, evidence and responsibility first.
Every collaboration should define who owns the data, who makes decisions, which claims are permitted, how results are measured and what remains outside scope.
- Written scope and research status before any work starts.
- Data and confidentiality terms agreed in writing.
- Named technical and decision owners on both sides.
- Success, safety and termination criteria set in advance.
- Publication and public-claim approval by both parties.
- Human accountability for any high-impact decision, whatever the software recommends.
A conversation is not a partnership.
Yes Say only what is approved
- Name a partner only with their written approval.
- Describe joint results with the agreed status label.
- Correct a public statement quickly if a partner asks.
Never Borrow credibility
- Show a logo, name or quote without written approval.
- Describe an enquiry, meeting or quote request as a partnership or contract.
- Name suppliers, launch providers or audit firms we have only approached.
- Imply endorsement by any agency or government.
Each product, with its honest label.
PQ-Agility · DSRP · AI Sovereignty Oracle
Post-quantum policy, delay-tolerant relay and model provenance. 249 foundation tests.
S1–S7LENS · WATCH · WEATHER · MCC · EDGE · NEXUS · SWARM TRUST
Mission applications evaluated in simulation. 258 tests across the seven.
N13 · S8 · S9SPACETRACE · SSA Accountability · MFG Provenance
Provenance and accountability products shown on the ground. 96 tests across the three.
COSRYX-WATCH here is the COSRYX conjunction and anomaly alert product. Product test counts are one population (692 product tests in total) and are never mixed with integrated tests or security-gate checks.
Write to us. The form is not connected yet.
Send a partnership proposal
Use the COSRYX enquiry form with "Partnership or collaboration" already selected. Describe the objectives and proposed scope at a public level.
research@cosryx.com
Put the collaboration type in the subject line. In the message: the problem, the system or data involved, the decision the result would inform, and any deadline.
Email research@cosryx.comSecrets or controlled data
No keys, passwords, credentials, export-controlled material or personal data in a first message. We will agree how to handle data in the written scope.
Before you propose.
Does COSRYX have partners today?
We do not name any. A partner appears on this site only after written approval, and an enquiry or quote request is never presented as a partnership.
Can we test COSRYX on our own spacecraft or telemetry?
That is the kind of work gates G4 and G5 (hardware-in-the-loop and LEO shadow) need. It would start as a scoped pilot with ground data first. Nothing is flight-qualified.
Is the PQ pilot a certification?
No. It is an assessment with an inventory, a policy evaluation and a migration plan. It is not a certification and PQ-Agility has not been externally audited.
Who owns the results?
That is agreed in the written scope before work starts, together with who may publish what.
When will the form work?
When a production endpoint is connected. Until then, email research@cosryx.com; the page will change when the form starts working.
Bring a problem. Leave with a written scope.
One email is enough to start: what you want to learn, and why it matters.