The OpenCodeGo Price Hike Betrayal: A Full Breakdown
OpenCodeGo broke its no-price-hike promise within 11 days, exposing its "supplier advantage" as a marketing tactic.
After DeepSeek announced an official API price hike, third-party provider OpenCodeGo quickly followed suit — despite its co-founder having publicly promised otherwise, citing supplier channels that could hold prices steady. Once the hike landed, OpenCodeGo blamed the supplier and claimed it had been deceived. The incident highlights a broader problem with AI intermediaries: many lack genuine pricing power and rely on hollow promises to drive short-term subscriptions. Users are advised to cancel auto-renewals immediately and consider switching to DeepSeek's official API or other reputable providers.
What Happened: From Public Promise to Instant Betrayal
Shortly after DeepSeekAd announced an official API price increase, third-party provider OpenCodeGo almost immediately followed suit — sparking serious backlash from its user base. What made matters worse: just days earlier, OpenCodeGo had publicly promised it would not raise prices, claiming that through its supplier channels it could maintain the original pricing levels.
The price increases were steep. In USD terms, a plan previously priced at $0.43 jumped to $0.66, while $0.87 became $1.98. The tiered subscription packages were also overhauled: what were once $60 plans (Flash, Pro, etc.) were slashed to $15 — but with drastically reduced request quotas, meaning the effective per-request cost now rivals DeepSeek's official API pricing.
The "Supplier" Marketing Spin Behind the Promise
OpenCodeGo's co-founder had explicitly stated on Twitter that their suppliers could replicate pre-hike DeepSeek pricing by running workloads on rented GPUs. That statement drove a wave of new subscriptions — many users signed up specifically because of the "no price hike" guarantee.
Just 11 days later, once DeepSeek's price increase took effect, OpenCodeGo immediately walked back its position, claiming that "the supplier deceived them" and "the supplier couldn't deliver anymore." This about-face is hard to take at face value. If the supplier genuinely had access to low-cost GPU resources, why did that capability evaporate the moment the official price change went live? A more plausible explanation: OpenCodeGo was using the window of DeepSeek's announced-but-not-yet-live price hike as a marketing opportunity, and the so-called "supplier advantage" was never more than a hook to attract subscribers.
How to Cancel and What to Use Instead
If you're already subscribed to OpenCodeGo, here's what you should do:
Cancel Your Auto-Renewal Immediately
Log into Alipay or whichever payment platform you used and disable the auto-renewal for OpenCodeGo to avoid being charged next month.
Making the Most of Your Current Billing Cycle
If you're on the introductory $5 first-month plan, it's reasonable to use out the rest of the current period. However, renewing at $10 or higher next month is not recommended.
Finding a Reliable Alternative
Consider switching to DeepSeek's official API directly, or look for other third-party providers with a genuine track record and transparent pricing. Official channels may cost slightly more, but they offer far better stability and accountability.
A Warning About Trust in Third-Party AI Services
This incident exposes a systemic problem with third-party AI service providers: when upstream pricing changes, intermediaries often have no real negotiating power or cost advantage. Claims of "supplier channels" and "special resources" are frequently just marketing language — and when the upstream price moves, those promises collapse instantly.
The deeper issue is one of integrity. OpenCodeGo actively recruited new subscribers with a "no price hike" promise while — presumably — aware that DeepSeek's price increase was imminent. That kind of conduct borders on false advertising. When evaluating third-party services, users need to look beyond price comparisons and assess the provider's track record for honesty and genuine technical capability.
For AI developers and power users, using official APIs directly may cost a bit more upfront, but the gains in stability, transparency, and service reliability are well worth it. Third-party services can serve as a useful supplement, but they shouldn't be your sole dependency. The OpenCodeGo episode is yet another reminder: over-reliance on any single third-party provider carries real risk. A diversified service strategy is the smarter long-term play.
Related articles
AI Comic Drama with WorkBuddy from Scratch: A Step-by-Step Skill Pack Installation Guide
Learn how to create AI comic dramas with WorkBuddy from scratch. This guide covers installation, Skill pack import and invocation, plus a script generation demo with manual revision tips to get you through the first step from script to storyboard.
WorkBuddy Agent Runs the Entire GEO Database Mining Pipeline with a Single Prompt
WorkBuddy agent automates GEO database mining: from data search and curation to batch correction, differential analysis, co-expression networks, feature gene screening, and immune infiltration—a single prompt generates a complete bioinformatics report, greatly lowering the barrier to bioinformatics analysis.
PC Memory Wasted? Hacker News Debates Centralized Data Centers
Hacker News users argue that personal computer memory is wasted and should be centralized in data centers, sparking debate on centralized vs. distributed computing resource allocation. This article analyzes the logic behind the claim, the costs of centralization, and new tensions in memory resource allocation in the AI era.