Repositories with a clear license story: OSI-style open source and source-available models with use restrictions.
We distinguish between licenses that match the common Open Source Definition (OSI) and models where code is public but use is restricted.
Licences such as Apache-2.0 or MIT are what many people mean by true open source: public source, reuse and modification within the licence terms, and alignment with the OSI definition. Our HelixTest and SecureCollab projects use Apache-2.0.
The Business Source License is not “open source” in the OSI sense: code is visible and often free for defined uses (e.g. non-commercial research), while commercial use is restricted or only unlocked after a set period. We publish Ferrum Lab Kit under BUSL-1.1 – transparent and inspectable, but strategically different from Apache-2.0.
Commercial products (e.g. Ferrum, BioResearch Assistant) may use BUSL or other models; the LICENSE file in each repository and the product page are authoritative.
Rust conformance and integration tests for GA4GH-style platforms: API contracts (WES, TES, DRS, TRS, Beacon v2), workflow execution, cross-service E2E, Passports, and Crypt4GH-oriented checks. Results are a technical signal – not official GA4GH certification.
GitHub →Multi-party clinical data analysis using homomorphic encryption: statistics across encrypted datasets from several institutions without raw data leaving each site. Proof-of-concept – not a substitute for a security audit or compliance assessment.
GitHub →On-ramp to Ferrum: deployment and integration layer for labs, ELIXIR node candidates, and GDI-style participants – selective GA4GH services against your storage, scheduler, and identity stack. Complements the main Ferrum repo; JSON conformance reports are open, licensed PDF output see repository.
GitHub →Additional repositories will follow. GitHub remains the central index of our public work.