1. Weak privacy & attestation guarantees
“Apple’s attestation servers will only generate the FreshnessCode for a genuine device that checks in via APNs. A software‑only adversary cannot forge the MDA certificate chain (Assumption 3).” (btown)
“Macs do not have an accessible hardware TEE.” (ramoz)
These comments highlight skepticism that current macOS hardening (SIP, PT_DENY_ATTACH, Hardened Runtime) provides true confidential‑compute isolation.
2. Questionable economic math
“If you can pay off a mac mini in 2‑4 months, and make $1‑2k profit every month after that, why wouldn’t their business model just be buying mac minis?” (kennywinker)
“The numbers are obviously high, because if this takes off then the price for inference will also drop.” (znnajdla)
Users point out that the claimed earnings rely on unrealistic utilization and ignore real‑world costs such as power, cooling, and hardware wear.
3. Technical feasibility limits
“The hypervisor page‑table trick is thus claimed to protect GPU memory from RDMA.” (kennywinker)
“There is no actual way to verify the contents of the running binaries. The binary hash they include in their signatures is self‑reported, and can be modified.” (mirashii)
Discussion centres on gaps in remote attestation, the lack of a true TEE for third‑party code, and doubts about securing GPU memory and model binaries.
4. Marketplace bootstrap & demand uncertainty
“At the moment they don’t have enough sustained demand to justify the earning estimates.” (tgma)
“Give it some time and let’s see how it goes.” (splittydev) Commentators stress that without a steady stream of inference requests the model cannot attract enough providers, making early‑stage profitability doubtful.