We collaborate
rarely and well.
Arqora's work is mostly internal and mostly private. But occasionally, the right people or organizations appear — ones where the overlap is real and the collaboration would produce something neither side could do alone.
This is not a partnerships page. It's a filter.
Most organizations use a page like this to signal openness. Arqora uses it to signal the opposite — not hostility, but specificity. We're not looking for partners in the general sense. We're looking for people or groups who have a specific, legitimate overlap with what we actually do.
If you found this page by accident or out of curiosity, that's fine. If you have a real proposal, read the rest carefully before reaching out. The quality of the initial contact tells us almost everything we need to know.
Independent engineers
Individuals who build seriously. Not hobbyists looking for a portfolio piece — engineers who have shipped real systems and think carefully about the work they take on.
Research groups
Academic or independent research groups working on problems that intersect with software architecture, systems design, distributed infrastructure, or security.
Small technical orgs
Private organizations or small teams with focused mandates. Not large agencies or consultancies — groups that operate with discipline and own what they build.
Experiment partners
Groups willing to run a specific investigation with us — providing infrastructure access, domain expertise, or a real problem that maps to an active Arqora experiment.
Security researchers
Individuals doing serious work in vulnerability research, threat modelling, or infrastructure hardening. We engage with them on mutual terms — never adversarially.
What Arqora brings
What Arqora needs from you
Read this page carefully.
Understand what Arqora does, how it operates, and what kinds of collaboration it's actually open to. If something here doesn't match your context, a proposal probably won't go far.
Send a specific proposal.
Not an introduction. Not a CV. A specific description of what you're working on, what overlap you see with Arqora's work, and what collaboration would concretely mean. Three paragraphs is enough. Ten is too many.
Expect a considered response.
We read every proposal. We don't respond to ones that clearly didn't engage with what Arqora actually does. If there's genuine overlap, we'll respond with questions or a call. If not, we'll say so.
A short scoped engagement first.
New collaborations start with a defined, limited-scope engagement — not an open-ended partnership. This protects both parties and surfaces incompatibilities early, before either side has over-invested.
Ongoing only if it earns it.
An ongoing collaboration is earned through the quality of the initial engagement. We don't commit to long-term relationships by default. If the work is good and the fit is right, it continues naturally.
Arqora keeps a small number of active collaborations at any time — deliberately. A collaboration that doesn't get attention isn't a collaboration, it's a name on a list.
If you're not accepted, it doesn't mean your work isn't good. It means the overlap wasn't right, or the timing wasn't right. Both are valid reasons.