{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreictnuoozxkh4xwxu4g37jewyh3lw5yatdjpal37tpwzavlfbqswde",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mkupfic3wos2"
  },
  "path": "/t/cpu-basic-spaces-hitting-quota-limits-despite-unlimited-hosting-inconsistent-behavior-with-restart-and-factory-rebuild/175681#post_3",
  "publishedAt": "2026-05-02T12:09:59.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Thanks for your response.\n\nI’d like to clarify something regarding the CPU-Basic Spaces.\n\nAccording to the documentation, CPU-Basic Spaces are described as being freely available for hosting (often interpreted as “unlimited” in terms of usage, aside from sleeping behavior). However, the current behavior seems to contradict that expectation.\n\nIn my case:\n\n  * I cannot restart a sleeping Space due to a quota error\n  * “Factory Rebuild” also fails with a hardware quota limit\n  * The same issue occurs even on a fresh account with no active Spaces\n\n\n\nThis raises an important question:\n\n> Are CPU-Basic Spaces actually subject to a strict hardware quota limit?\n\nIf so:\n\n  * What are the exact limits (number of concurrent Spaces, CPU allocation, etc.)?\n  * Are sleeping Spaces still counted toward this quota?\n  * Why would a completely new account immediately hit this limit?\n\n\n\nAlso, the error messages are inconsistent:\n\n  * “null quota limit”\n  * “hardware quota limit across all your Spaces”\n\n\n\nThis makes it difficult to determine whether this is expected behavior or a bug.\n\nCould you clarify:\n\n  1. Whether CPU-Basic is truly “unlimited” in practice\n  2. What quotas are applied behind the scenes\n  3. Whether this behavior is intentional or a recent change\n\n\n\nThis clarification would help avoid confusion for developers relying on CPU-Basic Spaces.",
  "title": "CPU-Basic Spaces hitting quota limits despite “unlimited hosting” — inconsistent behavior with Restart and Factory Rebuild"
}