No institution does this alone
Cross-institutional problems share a shape. The evidence sits in several places, nobody is allowed to pool it, and every organisation in the room answers to a different regulator. The usual answer is a data sharing agreement that takes two years, or a pilot that never leaves the lab.
Goose FL exists to make the other answer practical: the model travels, the data never does. We are looking for project partners who bring a real problem and a real decision to make. Not resellers, not referral partners, not marketing partners. A project, with a named problem, a defined role, and a result we can both point at.
Two places we work
Finance
Fraud, AML and inclusion decisions that decide who gets access to a bank account. KYComm is the shared compliance infrastructure for this work: each institution screens against the shared model, the records stay where they are, and there is no central vault to breach. The question a supervisor asks is not whether the model performs in a demonstration, but whether exclusion can be measured and shown.
Healthcare
Clinical evidence that has to hold across hospitals, when the record that matters most may not leave the building. Oncology HealthFL trains detection across sites on the hospital's own infrastructure, through the FHIR and OMOP interfaces already in place. The clinical proof point for the pattern is established: a tumour detection model trained across 71 hospitals improved detection by a third with zero patient records shared (Sheller et al., 2020).
Who we want
Eight kinds of partner. Most arrive through one focus area and one category, and some span several. We would rather hear the problem than file you first.
- ResearchUniversities and institutes that want a protocol worth publishing, on data that cannot be copied.
- Corporate and institutionalBanks, insurers, health systems, pharma, logistics and energy operators holding a live decision and records they cannot pool.
- Funds and portfolio companiesInvestors who want the AI claims in a portfolio tested, and companies that need a deployment their board can govern.
- PhilanthropicFoundations funding public-interest infrastructure, from programme design through independent evaluation.
- Public agencyRegulators, development banks and public agencies with a supervisory question and no safe way to test an answer.
- ConsortiumIndustry bodies and multi-country programmes that need one method across members who will not share data.
- TechnologyCloud and colocation providers, data centres, PET providers, and operators whose measurement data cannot leave the site, including carbon capture and industrial monitoring.
- RegionalPlace-based development and innovation bodies building capability in a region, with the institutions already in it.
Integration is the work
The cryptography is usually the easy part. Deployments stall on identity, consent and change control, months before anyone has to trust a proof. So the integration map comes first.
Where the data stays
Your environment, your region, or an enclave you control. This gets decided first because it decides everything else.
Where the model runs
Federated orchestration across sites, a trusted execution environment, or a clean room. The smallest pattern that answers the question, not the most advanced one.
Who is allowed to ask
Your identity provider, your consent records, your approval chain. A privacy pattern that routes around them is a second system nobody governs.
What comes out
Aggregates, parameters or evidence, landing in the warehouse or registry you already report from, so the result can be audited by someone who was not in the room.
Patterns we work with
- Federated learning
- Secure aggregation
- Private set intersection
- Differential privacy
- Synthetic data
- Trusted execution environments
- Clean rooms
Every engagement opens with a two-week integration map: systems, identities, data classes, and the decision the output has to support. If the pattern does not survive that map, we say so before anyone signs.
Who is already in
National agencies, research institutes, accelerator networks and privacy engineers. Each one is in a project, not a directory.
Marks are used with each organisation's permission. A mark without permission comes off the grid rather than going on greyed out.
In their words
A partner on what changed once the records stopped moving, and what it cost to get there.
Tell us the problem
Two or three sentences is enough. We answer every enquiry within five working days, and we will tell you if it is not a fit.