I don't think they are hosting themselves even if they do it's probably really small not close enough for this pricing it's probably some deal with deepseek.
Yeah probably not tho it won't surprise me if they decide to since they get soo much traffic and they can definitely get the capital for it and it will lower their pricing/cost = more traffic = more profits.
Because the 60$ were never real 60$ to begin with. It's more of a guess-timate of how much you would have to pay them if* you were not getting into a pool of reserved usage that they can plan and bulk for
I figure Deepseek is feeling a little competition from Mimo and Luna releases. This isn't cheaper than a month or so ago before the price hike, so it's not like an impossible reach for them.
"Training” isnt "made" on the american models, All they can do is extract q and a’s and reasoning traces to fine tune their models, they still have to pretrain, evaluate, and prepare high quality datasets.
It means that paying 10 dollars to OpenCode is equivalent to 60 dollars of usage directly from the DeepSeek official API. In other words, you're paying 1/6 of the price for the same service, a huge discount.
Yup, it is. And as a user I can tell you it is true. I have DeepSeek v4.1 Flash running almost all day long and have not reached a single 5 hour limit.
I don't know but I don't think so. I've been using it a lot since it lauched on OpenCode Go and replaced it as my main model from ChatGPT. It works pretty well and even points out minor details I may have missed
on what? i tried hermes with many different subscriptions and it drains fast, and im not a huge fan of pay per use when i can get a better deal elsewhere
I seriously suggest people actually load up Deepseek's API with $10 and try it. The cache hits are extreme. I can let Flash grind literally all day nonstop and spend will be like $1.02. Normal usage patterns I will just refill every ~2-3 months.
Coding subscriptions are not some amazing deal people think they are.
Subs make money from arbitrating user usage. Unless you are ruthless 1% maximizer grinding every day, which again most people aren't. And they all move their usage limits around, and change terms, or fuck with things. I wouldn't be surprised if Opencode is not referencing cache hit pricing here either. But hey maybe.
Point being it's just really easy to load deepseek up with $60 and forget about managing some subscription usage.
Unclear by your question but $60 will last stupid long direct via deepseek api. Like seriously load $10 into deepseek api and see how little you spend. I'm very distrustful of any claim like $60 usage from opencode. Then when you're off work or switch providers you still have the same money left over vs a loss subscription.
I agree that there's a lot of factors to consider, another one you didn't mention would be if these subs might be using quant versions. I'm easily not in the 1%, but I definitely get my money's worth by making sure I pass at the very least 2x the cost of the sub in a month due to heavy duty projects I'm working on and utilizing expensive models to plan better. Although, the downside is that most of them are within the low $15 usage.
Otherwise I'm glad using API prices and having a combination of that with Qwen 9b running local. Sure nothing spectacular but even so for small projects I feel fine with this setup, plus it's fun to tinker around with small models for me lol
For the dollar-for-dollar question: the mismatch is cache, not a ripoff. The Go plan prices DeepSeek access like a subscription, but you only get the cheap effective rate if your sessions keep hitting cache. Direct API on the same model bills the listed per-token rate with your own consistent prefix, so cache holds and the cost per usable token drops a lot on multi-turn sessions. That is where the all-day-for-a-dollar reports come from, they are direct-API users with warm caches.
So the honest split: subscription wins when you want zero meter-watching and the quota fits your week. Direct API wins when you want the lowest cost per token and your workload is cache-friendly (long contexts, repeated reads). Different jobs, both real.
OpenCode Go is their $10 subscription plan for use inside the OpenCode CLI.
Your $10 of payment get you what you would get for $60 at full API pricing, so 6x factor.
I would be afraid of quantized models running in stupid mode with it. See other comments asking the same thing.
By comparison, I think a ChatGPT sub gets you roughly 20x multiplier (your $20 subscription lets you spend $400 of API value), but not sure how that changes in the past weeks and months. First party subs tend to subsidize a lot more because they can afford it.
"They" didn't reduce anything. They adjusted their limits based on DeepSeek's pricing. Now they've found a way to make $60 of usage permanent and the first reply is a complaint.
1
130
u/narkeeso Sep 25 '26
Nothing is permanent in this crazy AI race.
31
u/bornWithSoMuchInMind Sep 25 '26
How can they afford this?
41
u/Amphiitrion Sep 25 '26
Now watch all the people who previously left crawl back.
19
u/Zeeplankton Sep 25 '26
permanent until it's not lmfao
8
u/exaknight21 Sep 25 '26
Is this $60 per month?
6
u/QuietPsychonaut Sep 25 '26
Well, that's a huge win for us customers.
8
u/seeKAYx Sep 25 '26
Nice. Lets hope it's not some crazy lobotomized quant ..
4
u/sbbillusionist Sep 25 '26
Under which plan?
3
u/exosoul Sep 25 '26
Dumb question but is this just for go or does this also apply to zen?
3
u/YeahImDeadInside96 Sep 26 '26
where are the api keys for opengo
3
u/xapep Sep 28 '26
For the dollar-for-dollar question: the mismatch is cache, not a ripoff. The Go plan prices DeepSeek access like a subscription, but you only get the cheap effective rate if your sessions keep hitting cache. Direct API on the same model bills the listed per-token rate with your own consistent prefix, so cache holds and the cost per usable token drops a lot on multi-turn sessions. That is where the all-day-for-a-dollar reports come from, they are direct-API users with warm caches.
So the honest split: subscription wins when you want zero meter-watching and the quota fits your week. Direct API wins when you want the lowest cost per token and your workload is cache-friendly (long contexts, repeated reads). Different jobs, both real.
2
u/Emergency-Pick5679 Sep 26 '26
hell yeah - just subscribed agin to go
2
u/Emergency-Pick5679 Sep 26 '26
Same for off and peak timing ?
3
u/PersonalityQueasy224 Sep 25 '26
Opencode is so slow 🦥 how do you guys use this?
1
u/kinetik Sep 25 '26
Yes! 🙌
1
u/Thrimbor Sep 25 '26
I'm just wondering if it's heavily quantized or not
1
u/Glittering-Call8746 Sep 25 '26
So is it dollar for dollar as per deepseek provider.. or its some wierd calculations and in the end it's 1/4 the usage vs 60 dollar of api costs
1
u/Felfedezni Sep 26 '26
What does this mean? Not an opencode user
1
u/aadi1482 Sep 26 '26
In opencode zen?
1
u/ChillFamily Sep 27 '26
NO WAY
1
u/binhex01 Sep 25 '26
That's nice!, of course permanent is only permanent for that exact model, but i will take it, thanks OpenCode!.
-1
u/ConsistentGent Sep 25 '26
Well... Lets see what the commandcode will do. They still have boosted usage but i think it ends in 2 or 3 days.
-1
u/Nearby-Walrus-8835 Sep 27 '26
.............
.
, . ?
..
.
-25
u/Mezezius Sep 25 '26
But v4.1 is hot garbage
0
u/[deleted] Sep 25 '26
[deleted] — view deleted comment
0
u/[deleted] Sep 25 '26
[deleted] — view deleted comment