Company enquiries, engineering collaboration, press and general correspondence.
Direct contact
Talk to the people who build it.
FuryLogic is a small engineering company. There is no account to create, no form to fill in and no sales process. Email reaches the person responsible for the work.
Research correspondence, technical review and matters that need a direct answer.
No form, by design. This site is static and runs no application server, so there is nothing to submit to and nothing to secure. A direct email is the reliable channel — and it does not sit in a database we have to protect.
Elsewhere
Code and public record.
Public mirrors, releases and issue trackers.
Canonical repositories on FuryLogic infrastructure.
Researcher identity for the published papers.
Preprints deposited with resolvable DOIs.
Before you write
What reaches the right desk.
Engineering work
Systems where inference performance, memory behaviour, retrieval quality or storage consistency is the constraint. Include the hardware, the constraint and what you have already tried.
Research review
Reproductions, disagreements, missing baselines or constraints that change a published conclusion. Specific technical objections are the most useful kind of mail.
Security reports
Vulnerabilities in any FuryLogic project. Please include the version, affected component and a minimal reproduction. Do not open a public issue for an unpatched vulnerability.
Open-source
Patches, ports, packaging and bug reports. GitHub and the self-hosted Git instance are both monitored; a clear reproduction saves a round trip.
Start here
One email is enough.
Technical detail in the first message is appreciated: the constraint, the hardware, the version and the outcome you need. If it is a fit, we will say so. If it is not, we will say that too.