▚ Open collective · Spin-qubit research ▞
An open community fuelling growth of semiconductor spin qubit platforms. We integrate, build and maintain useful pieces: simulators, datasets, drivers, algorithms — to co-design a scalable future for spin qubits.
Not one big thing. Many integrated ones.
We do this in our spare time, avoiding reinvented wheels, lowering the barriers to entry, and letting academic and industrial partners build on a standardized, compatible platform. Everyone is welcome, and not much is needed to join. In the era of AI, communities like this matter more than ever.
> Projects
The pieces we're building. Pick one, open an issue, dive in.
ReadSpyn
activeReadout simulator
Simulate spin-qubit readout traces for developing and benchmarking readout methods.
View repo →QDarts
activeCharge stability diagram simulator
Generate realistic charge stability diagrams for quantum dot arrays.
View repo →SpinSkills
activeReusable analysis skills
A growing library of small, composable skills for spin-qubit workflows.
View repo →ChargeTwin
activeWorld / surrogate noise simulator
Extremely fast world/surrogate simulator of charge-noise disorder and dynamics affecting quantum dot devices.
View repo →SpinStoq
activeStochastic noise trajectory generator
Fast generator of stochastic trajectories of spatiotemporal noise for spin-qubit simulations.
View repo →SpinDeck
activeOpen-source hardware map
A map of open-source hardware relevant to spin qubits — a value-chain matrix for the field.
View repo →SpinLib
cookingLiterature library & database
A structured library and database showing the connections and clustering of spin-qubit papers.
View repo →Tuning transformer
cookingAutomated device tuning
An ML approach to automating quantum-dot tuning.
View repo →SpinFEM
planningPoisson-equation device solver
Open-source finite-element simulator of the Poisson equation from device geometry.
Help shape it →> Manifesto
What we believe, and how we work.
- 01Standardize, don't fragment. Every isolated lab stack is a barrier to entry. Common formats and APIs beat one-off scripts.
- 02Open by default. Code, data, and decisions live in public. If it can't be shared, it doesn't belong here.
- 03Co-design, not gatekeep. Academic labs and hardware vendors build on the same platform — no permission required.
- 04Small pieces, loosely joined. No monolith. Modular tools others can pick up, swap, and build on.
- 05Reproducible over impressive. FAIR data, tests, documentation. A result you can rerun beats a demo you can't.
- 06Part-time is fine. Most of us do this on the side. Leave breadcrumbs so the next person can pick up where you left off.
- 07Built to outlast one grant. We're growing toward a self-sustaining foundation, not a one-off project.
> People 5
Who's keeping the lights on. Want to be listed? Get involved.
> How to get involved
Three ways in, whatever your time and background.
Clean & refactor
Highest-leverage, lowest-barrier work right now. Docstrings, tests, tidy-ups — no deep domain knowledge needed to make a repo more usable.
See bounty board →Build something new
Idea for a simulator, skill, or dataset? Open an issue describing what you want to try, find a collaborator, and go.
Propose an avenue →Lurk & learn
New to the field? SpinAcademy collects reviews, tutorials, and starter resources. No pressure to contribute immediately.
Browse SpinAcademy →