Firm rents four Nvidia H200s to test '80x cheaper' DeepSeek claim — $13,200 monthly GPU rental doubles Claude bill while security flaws keep code offline

The DeepSeek logo against a hexagonal textured background
(Image credit: DeepSeek)

The Call Center Doctors, a call center consultancy that builds and runs call floors for other businesses, rented a server with four Nvidia H200 AI GPUs to serve DeepSeek V4.1 Flash to its Claude Code agents in place of Opus 5.5, according to its test write-up. The write-up is aimed at anyone who has heard that DeepSeek is “80x cheaper” than Claude. Using its real coding mix, the firm's server topped out at around 213 tokens written per second at an on-demand cost of $440.88 per day, versus $184–$223 per day for the same work via DeepSeek’s API. The call center went back to Opus 5.5 at a lower price than the box would cost at on-demand rates.

DeepSeek’s API is priced at $0.15 per 1 million new input tokens off-peak, $0.003 cached input tokens, and $0.60 per 1 million output tokens. Peak costs are double. By comparison, Anthropic’s Claude Opus 5.5 is listed at $4 input and $20 output per 1 million tokens, with cache reads at $0.20. The consultancy used it through subscriptions and not the API.

Latest Videos FromTom's Hardware
Shane Downing
Contributing Writer

Shane Downing is a Contributing Writer for Tom’s Hardware, covering consumer storage, PC hardware, and AI.

  • ndneubauer2
    DeepSeek is “80x cheaper” than Claude.

    Well, obviously you have to compare API costs with API costs, not the cost of renting hardware.

    What even is the point of this article?
    Reply
  • Moosegoose
    This is the dumbest article I have read in weeks.

    This isn’t even AI slop, it’s devoid of intelligence. I hope the author doesn’t think this makes him some sort of authority on LLMs.

    “The box’s performance was fine for one kind of work at a time in the test’s one-minute full-load runs. But the coding agents work mostly by resending the conversation, and 96% of what the agents provided the model was stale text, according to the consultancy’s logs. It takes about 1,000 old tokens for every new token written; the re-reads are cheap, but so numerous that the box was kept busy re-reading, leaving little of its time for writing new tokens.”

    Do…. you not know how caching works? Or are you a fourth grader, because that is about the critical thinking proficiency demonstrated here.

    Also the company that rented 4xH200s 24/7 to serve themselves Deepseek to their coding agents…? Equally devoid of any brain cells.

    Probably taking advice from Shane Downing.
    Reply
  • loveday.ben
    Is this a paid advertisement for Anthropic? I'm sure if I rented a server with gpu from Azure Foundry and deployed a Claude model I'd have a similar experience...
    Reply
  • jsidhenneld
    Admin said:
    A call center consultancy rented four Nvidia H200s to run DeepSeek V4.1 Flash for Claude Code and found DeepSeek's API cheaper.

    Firm rents four Nvidia H200s to test '80x cheaper' DeepSeek claim : Read more
    This most stup1d articles i read from this website, not even ai slop just pure stupidity

    API cost vs API cost, NOT RENT VS API COST !!!!🤦
    Reply
  • ryanga
    I am soooo relieved that these comments exist. I was shocked that the article didn't understand that getting sample drugs for free was not actually what drugs cost and why api costs are not the consumer costs if the companies are still running at a loss unless someone else builds and supports their infra
    Reply
  • machdisk
    So the firm were incompetent at setting up LLMs? 4xh200 and they only got 200 tok/s concurrent on dsv4.1 a 16B active in decode and 8B active in prefill model? How? Were they running llama.cpp in pipeline parallel or something? Thats a fraction of what they should have got
    Reply
  • impoor
    Well, this comment section just did the peer review that the article apparently didn’t.

    My original response to the author was literally: "Sounds like a skill issue."
    He challenged me to provide a case study, so I did. What followed was enough of a train wreck that I ended up documenting the entire exchange and auditing the original test.

    The problems are basically the same ones people here already spotted;

    -> API cost vs dedicated H200 rental is not the same comparison.

    -> The serving/harness configuration was never published well enough to reproduce.

    -> Their own workload was dominated by context/re-read traffic, making harness and context management central to the result.

    -> The DeepSeek builder agents were never enabled, so "cost per shipped DeepSeek change" was estimated, not measured.

    -> Four H200s producing these economics should trigger questions about the deployment before anyone declares the model defeated.

    Comment #7: yes. Exactly. How do you end up there with 4×H200?
    What surprised me most is that Tom’s Hardware apparently never stopped to seriously interrogate the methodology before turning the consultancy post into an article.

    I documented the entire exchange, the math, the missing methodology and my own local case study here:

    https://samsai.no/logg/deepseek-lost-part-1https://samsai.no/logg/deepseek-lost-part-2
    After asking me to "prove him wrong," the original author eventually abandoned the technical discussion and replied:

    "you are poor."
    Hence the username.

    - impoor
    Reply