About the project

A model hub run like an infrastructure project, not a content farm

ModelFoundry is a small collective of engineers and researchers who got tired of downloading checkpoints whose provenance nobody could state. The project maintains a catalogue of open-weight models, the tooling to verify them, an evaluation harness that ships beside every release, and a compact runtime for serving them.

We are not a research lab and we do not compete with the labs. We care about the layer between a checkpoint and the machine it runs on: hashing, licensing, quantization quality, latency and the boring question of who is allowed to pull what.

15checkpoints published
68contributors
4gate checks per upload
0 trackersin our own runtime
Funding comes from hosted inference and support contracts. There is no advertising, no data sale and no paid placement in the catalog.
Principles

Four rules we do not negotiate

Publish the evidence, not the claim

A model card without a runnable harness is marketing. If we cannot reproduce a number, we delete the number.

Say what a build is not good at

Long-context decay, quantization trade-offs, refusal behaviour, language parity. Limitations belong in the card, not in a footnote.

Access should be revocable

Keys instead of public links. It is less convenient and it is the only design that survives a takedown.

Measure the boring things

Time to first token, cache hit rate, digest mismatches, failed verification runs. These are the numbers that decide whether anyone can actually run this.

Maintainers

Who answers when something breaks

Six people carry the pager rotation; sixty-two more contribute models, tasks and fixes.

ME
Mara Ellis
Inference engineering

Schedulers, quantization promotion gates and the p99 work. Writes about latency more than is healthy.

DK
Deniz Kaya
Model research

Pre-training recipes and distillation for the small families. Maintains the bilingual sampling mix.

IV
Ilya Voronov
Evaluation

Owns the harness, the judge models and the rule that a suite version changes whenever a prompt changes.

SV
Sanne de Vries
Platform

Mirror operations, storage and the boring work of making a static site survive a traffic spike.

PR
Priya Raman
Release engineering

The verification pipeline, signed manifests and the gate that a build must pass before it gets a page.

TB
Tomas Berger
Documentation

Keeps the docs, the examples and the license texts honest with what the tools actually do.

How decisions get made

Two maintainers, one disagreement rule

Anything touching weights, licenses or the verification pipeline needs two maintainers. Anything touching documentation needs one. A change that cannot be explained in a single paragraph in the changelog does not ship.

  • Release lines, not calendar dates, define what is current
  • Withdrawn builds stay in the changelog with a reason attached
  • Breaking changes require a migration note in the same entry
Get in touch

Three doors, no ticket funnel

ChannelUse it for
Community chatModel requests, eval questions, "is this normal?"
Issue trackerBugs with a reproduction, conversion and verification PRs
Security contactResponsible disclosure, see the policy

The mirror itself is static, so there is no support form. Anything you type into a page on this domain stays in your browser.