Ship code
A merged pull request to the SDK, a new connector, a fixed example. Attribution stays with you. Maintainers review fast and tell you why.
AFFIXIO
Collaborate with AffixIO
Prove things that matter, together.
AffixIO is cryptographic proof infrastructure. We are looking for people, not just companies, who want to build on it, research it, teach it, and take it further. Pick the way that fits how you work.
Already know what you want to build? Tell us in one line. We reply within two business days.
Six ways in
Find the collaboration that fits you
Everyone arrives here for a different reason. Choose a track to see what the work looks like and how to take the first step. You can mix more than one.
Build on the open SDK
For engineers and open-source contributors. The AffixIO SDK, MCP connector, and documentation are open to read, extend, and improve. Start small, ship a pull request, go from there.
What you would do
- Improve the SDK on npm and GitHub
- Write connectors, examples, and client libraries
- Extend the MCP connector for new clients
- Sharpen the developer docs and error catalogue
How to start
- Run the sandbox. Hit the proof endpoints in the live sandbox.
- Read the quick start. Follow the quick start guide.
- Open an issue or PR. Pick something small and propose the change.
Research zero-knowledge and post-quantum cryptography
For cryptographers, academics, and standards people. Our technical work is documented in a public library of field reports, and we want production implementations tested, extended, and challenged.
What you would do
- Benchmark ZK circuits against a live implementation
- Probe ML-DSA and hybrid post-quantum migration paths
- Co-author or peer-review a field report
- Bring university groups and standards bodies into the loop
How to start
- Read a report. Start with the whitepaper library.
- Reproduce a result. Every report ships with reproduction steps.
- Send your findings. Tell us what held up and what did not.
Advocate in your community
For writers, speakers, and organisers. If you already explain hard technical ideas to other people, help more developers understand what verifiable proof changes and how to use it.
What you would do
- Write tutorials and explainers grounded in real code
- Give a talk or run a workshop at a meetup or conference
- Record a walkthrough of the sandbox or SDK
- Help newcomers land their first contribution
How to start
- Learn the basics. Read what AffixIO is.
- Pick a format. A post, a talk, a video, whatever you do well.
- Tell us the plan. We will share early access and review drafts.
Refer and resell
For consultants, agencies, and channel partners. If you advise organisations that need verifiable records, introduce them to AffixIO and earn commission through the regional vendor programmes.
What you would do
- Introduce clients who need tamper-evident audit trails
- Resell proof infrastructure under a regional programme
- Co-sell into ticketing, finance, healthcare, and public sector
- Earn commission on referred and closed work
How to start
- Read the programme. See the vendor programmes.
- Test the product. Walk a client through the sandbox.
- Register interest. We set up terms for your region.
Integrate proof into your platform
For product and platform teams. Any system that handles transactions, credentials, access, or entitlements can embed the AffixIO proof layer and give its own users something they can verify independently.
What you would do
- Embed signed allow or deny proofs at your boundary
- Add stateless QR verification that works offline
- Ship tamper-evident audit trails to your customers
- Scope a production integration in a structured pilot
How to start
- Map the fit. Read the stack placement guide.
- Prototype. Validate the flow in the sandbox.
- Scope a pilot. Move to partnerships and pilots.
Advise as a design partner
For operators, regulators, and domain experts. If you know where verifiable records break down in the real world, shape what we build next by acting as a design partner or advisor.
What you would do
- Pressure-test the roadmap against real constraints
- Bring sector knowledge in finance, health, or government
- Review compliance mapping for your jurisdiction
- Sit on early design reviews for new circuits and flows
How to start
- See the direction. Read a recent field report.
- Share your context. Tell us the problem you keep hitting.
- Join a review. We invite advisers into design sessions.
The work, honestly
What collaboration actually looks like
Not a logo wall or a Slack invite that goes quiet. Real contributions with a name attached, agreed before the work starts.
Publish findings
Reproduce a result, challenge a claim, or co-author a field report. Reproduction steps ship with every paper so the work is checkable.
Grow the room
Run a workshop, mentor a first-time contributor, bring a research group in. Advocacy that helps other people succeed, not vanity metrics.
What you build on
Real surfaces, open to work with
None of this is a waitlist. Every one of these is live and public today.
Live
Sandbox for proof endpoints, QR mint, and PQC attestation. Open it.
40+
Field reports with reproduction steps in the whitepaper library.
MCP
Hosted connector at affix-io.com/mcp for any Streamable HTTP client. Connect.
Before you write in
Questions people ask first
Who can collaborate with AffixIO?
Engineers, cryptographers, researchers, writers, community organisers, resellers, and platform teams. If you build software, study proofs, teach others, or bring AffixIO to a market, there is a track for you. Collaboration is open to individuals as well as organisations.
Do I need to be a cryptographer to contribute?
No. The open SDK, MCP connector, documentation, and worked examples are all places to contribute without a cryptography background. If you do work in zero-knowledge proofs or post-quantum cryptography, the research track goes deeper.
How is this different from a partnership or pilot?
Collaboration is the broader door. It covers individual contributors, researchers, advocates, and referrers as well as companies. Structured commercial work, such as an enterprise pilot or a channel programme, sits under partnerships and pilots and the vendor programmes, which this page links to.
Is the AffixIO SDK open?
Yes. The SDK is published on npm as @affix-io/sdk and mirrored on GitHub. You can read the code, open issues, and submit pull requests. A live sandbox lets you test proof endpoints before writing a line of integration code.
What do collaborators get in return?
Depending on the track: direct access to maintainers, early builds, attribution on merged work and published research, sandbox and API credits, and commission on referred deals through the vendor programmes. We agree what fair looks like before work starts.
How do I get in touch?
Use the contact form and pick Collaboration, or email partnership@affix-io.com with one line on what you want to build or prove. We reply to every genuine enquiry within two business days.
Start the conversation
One line is enough to begin
Tell us which track fits and what you have in mind. A pull request you want to open, a result you want to test, a talk you want to give, a client you want to introduce.
No pitch deck, no discovery call before there is anything to discover. We reply within two business days and scope a small first piece of work so both sides learn quickly.