{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigc2v4arykwyretxn2jl2kxydxy62fr6r4bew62r4apqqiwjhb5cu",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mmv52kqgtcj2"
  },
  "path": "/t/nutriken-clinical-bioinformatics-platform-for-latin-america-request-for-infrastructure-support/176254#post_2",
  "publishedAt": "2026-05-28T02:07:59.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "Spaces Overview — Hardware resources",
    "Using GPU Spaces",
    "Example staff comment: use the “Apply for a community grant” button in Space Settings",
    "Docker Spaces",
    "Manage your Space with huggingface_hub",
    "Spaces Overview — Secrets and environment variables",
    "Spaces Persistent Storage",
    "Spaces ZeroGPU docs",
    "Hugging Face Brand Assets"
  ],
  "textContent": "For the details, I think it would be safest to ask Hugging Face directly (`website@huggingface.co`), but **for the infrastructure part, I think applying for a Spaces Community Grant is probably the right path** :\n\n* * *\n\nA few practical suggestions, since this request seems to involve two slightly different things:\n\n  1. **temporary infrastructure support for the Space** , and\n  2. **official sponsorship / endorsement / logo usage**.\n\n\n\nThose should probably be handled separately.\n\n## 1. For the infrastructure request: use the Space’s Community Grant / hardware request flow\n\nFor the temporary CPU/GPU/tier upgrade, the most relevant path seems to be the **Community GPU Grant / hardware upgrade request** available from the Space settings.\n\nHugging Face’s Spaces docs mention that Spaces start on free CPU hardware by default, and that upgraded hardware can be requested from the **Settings** tab of the Space. The same docs also say that if a project needs help covering hardware upgrade costs, the owner can apply for a **community GPU grant** from the Space’s Settings tab:\n\n  * Spaces Overview — Hardware resources\n  * Using GPU Spaces\n\n\n\nThere is also a useful prior HF staff comment here:\n\n  * Example staff comment: use the “Apply for a community grant” button in Space Settings\n\n\n\nIn that thread, HF staff explained that using the button is important because it sends a notification to the internal review channel where staff members can see the request. So I would not rely only on a forum post for this part.\n\nThe route I would try is:\n\n\n    Your Space\n    → Settings\n    → Hardware\n    → select/request the needed hardware\n    → Apply for a community grant\n\n\nIf the UI has changed slightly, the same general idea should still apply: submit the request from the Space’s own hardware/settings page rather than only posting in the forum.\n\n## 2. Be specific about what resource is actually needed\n\nSince NutriKen is described as a **Docker SDK Space** , I would recommend being very explicit about the bottleneck.\n\nFrom your description, the request says “CPU/GPU/tiers”, but those are different problems:\n\n  * if the issue is many clinicians opening the app at once, the bottleneck may be **CPU/RAM/replicas** , not GPU;\n  * if the issue is slow model inference, then a **GPU tier** may be needed;\n  * if the issue is cold starts during the workshop, then an **upgraded always-on Space / sleep-time setting** may help;\n  * if the issue is traffic distribution, then **replicas** may be relevant, but replicas are tied to upgraded hardware;\n  * if the issue is local cache or generated reports, then **persistent storage** or external storage design may matter.\n\n\n\nRelevant docs:\n\n  * Docker Spaces\n  * Using GPU Spaces\n  * Manage your Space with huggingface_hub\n  * Spaces Overview — Secrets and environment variables\n  * Spaces Persistent Storage\n\n\n\nA good grant request would probably include something like:\n\n\n    Requested support:\n    - Temporary hardware upgrade for the Space during the APENUT workshop\n    - Dates: <start date> to <end date>\n    - Expected total participants: <number>\n    - Expected concurrent users: <number>\n    - Current bottleneck observed: <CPU/RAM/GPU/cold-start/API latency/etc.>\n    - Requested tier: <CPU Upgrade / T4 / L4 / A10G / etc.>\n    - Why this tier: <short technical reason>\n    - Whether GPU is required: <yes/no + reason>\n    - Whether patient-identifiable data is processed or stored: <yes/no + explanation>\n    - Post-event plan: downgrade the Space after the 3-day workshop\n\n\nThat kind of detail should make the request much easier to review than a general “please upgrade the Space” request.\n\n## 3. ZeroGPU may not be the right assumption here\n\nOne possible source of confusion: **ZeroGPU** and **regular Spaces hardware grants** are related but not identical paths.\n\nZeroGPU is a shared GPU infrastructure for Spaces. The current ZeroGPU docs describe it as being used for Gradio SDK Spaces, with dynamic GPU allocation:\n\n  * Spaces ZeroGPU docs\n\n\n\nSince NutriKen appears to be a Docker/FastAPI-style Space, I would not assume ZeroGPU is the correct target unless Hugging Face staff says so. For a Docker Space, a normal hardware upgrade request — for example CPU Upgrade, T4, L4, A10G, etc. — may be more appropriate.\n\nSo in the grant application, I would phrase the request as:\n\n> We are requesting the most appropriate temporary Spaces hardware support for a 3-day clinical education workshop. If GPU is not necessary for this Docker/FastAPI workload, a temporary CPU/RAM upgrade would also be acceptable.\n\nThis gives the HF team room to assign the appropriate resource instead of forcing the request into the wrong category.\n\n## 4. The endorsement / logo part should be treated separately\n\nFor the “official endorsement badge/logo” or “Infrastructure Sponsor” wording, I would be more cautious.\n\nUsing Hugging Face as a hosting platform is one thing. Saying that Hugging Face is an **official infrastructure sponsor** , or displaying an endorsement-style badge/logo, is a stronger claim. I would wait for explicit confirmation from Hugging Face before using language that implies sponsorship or endorsement.\n\nFor basic brand material, Hugging Face has a brand page:\n\n  * Hugging Face Brand Assets\n\n\n\nBut for anything like:\n\n\n    Official Hugging Face Infrastructure Sponsor\n\n\nor:\n\n\n    Supported by Hugging Face\n\n\nor:\n\n\n    Hugging Face-endorsed clinical platform\n\n\nI would not use that wording unless HF explicitly approves it.\n\nA safer wording while waiting would be something like:\n\n\n    Hosted on Hugging Face Spaces\n\n\nor:\n\n\n    Deployed on Hugging Face Spaces\n\n\nThose describe the infrastructure factually without implying official endorsement.\n\n## 5. For a medical / clinical decision-support project, include the safety boundary clearly\n\nBecause this is a clinical bioinformatics / clinical decision-support platform, I would also include a clear safety note in the grant request and in the Space README.\n\nSomething like:\n\n\n    NutriKen is intended for clinical education and decision support. It does not replace professional medical judgment, individualized patient evaluation, local clinical guidelines, or review by a qualified healthcare professional. The evidence shown by the system should be verified by the clinician before any intervention.\n\n\nThis is especially important because the forum post uses phrases like “clinical-grade reports.” That may be understandable from the project perspective, but for infrastructure review it is safer to clearly state the boundary between:\n\n  * educational / decision-support use,\n  * clinical workflow support,\n  * and actual regulated clinical deployment.\n\n\n\nIf the Space processes real patient data, I would also clarify:\n\n\n    The workshop demo will not store patient-identifiable information.\n\n\nor, if it does handle sensitive data:\n\n\n    The project handles <type of data>, stored in <location>, with <privacy/security controls>.\n\n\nFor a public Hugging Face Space, I would be especially careful not to process protected health information unless the privacy/security model has been reviewed.\n\n## 6. Suggested short application text\n\nYou could adapt something like this for the Community Grant request:\n\n\n    Hello Hugging Face team,\n\n    I am requesting a temporary Spaces hardware grant for NutriKen:\n\n    https://huggingface.co/spaces/Kenryu007/Nutriken\n\n    NutriKen is an open clinical bioinformatics / nutrition decision-support platform in Spanish, built for healthcare professionals in Latin America. It integrates public evidence sources such as MSKCC, NCBI Gene, Ensembl, KEGG and PubMed, and generates structured Spanish-language educational reports for clinician review.\n\n    The project is built as a Docker SDK Space using a FastAPI backend and a lightweight web frontend:\n\n    https://github.com/abrangel/Nutriken\n\n    I have been invited by the Peruvian Academy of Nutrition (APENUT) to use NutriKen as live training infrastructure during a 3-day international workshop for hundreds of clinicians.\n\n    Requested support:\n    - Temporary hardware upgrade for the workshop period: <dates>\n    - Expected total participants: <number>\n    - Expected concurrent users: <number>\n    - Current bottleneck: <CPU/RAM/GPU/cold start/API latency/etc.>\n    - Requested tier: <CPU Upgrade / T4 / L4 / A10G / other>\n    - Duration: <number of days>\n    - Post-event plan: downgrade the Space after the workshop\n\n    If GPU is not the right fit for this Docker/FastAPI workload, a temporary CPU/RAM upgrade would also be very helpful.\n\n    Safety note:\n    NutriKen is intended for clinical education and decision support. It does not replace professional medical judgment, individualized patient evaluation, or review by a qualified healthcare professional. The evidence shown by the system should be verified by clinicians before any intervention.\n\n    Thank you for considering this request.\n\n\n## 7. My overall recommendation\n\nSo my recommendation would be:\n\n  * keep the forum post as a public project-introduction thread;\n  * submit the actual infrastructure request through the Space’s **Apply for a community grant** flow;\n  * specify whether the bottleneck is CPU, RAM, GPU, cold start, or concurrent traffic;\n  * request a clearly time-bounded upgrade for the 3-day APENUT workshop;\n  * avoid implying official HF sponsorship or endorsement unless Hugging Face explicitly approves that wording;\n  * use factual wording like “hosted on Hugging Face Spaces” unless/until HF confirms sponsorship language.\n\n\n\nThe project seems well aligned with the spirit of community infrastructure support: open tooling, Spanish-language clinical education, Latin American access, and a time-limited workshop need. The strongest version of the request would be a concrete, reviewable hardware grant application rather than only a general forum appeal.",
  "title": "NutriKen – Clinical Bioinformatics Platform for Latin America (Request for Infrastructure Support)"
}