GitHub ne apne Copilot AI service ke liye ek bada change announce kiya hai. June 1 se company usage-based billing model par shift ho rahi hai. Matlab ab users actual AI usage ke hisaab se pay karenge, na ki fixed monthly requests ke hisaab se.
Yeh change isliye aa raha hai kyunki current system mein ek quick chat question aur multi-hour autonomous coding session ka cost same tha. GitHub ka kehna hai ki yeh step Copilot ko financially sustainable rakhne ke liye zaroori hai, kyunki AI computing resources ki demand bahut badh gayi hai.
Kya Badal Raha Hai GitHub Copilot Mein?
Filhaal GitHub Copilot subscribers ko monthly "requests" aur "premium requests" ka allocation milta hai. Jab bhi woh Copilot se AI model ki madad maangte hain, yeh requests use hoti hain. Lekin GitHub ke mutabiq, yeh broad categories alag-alag AI tasks ke backend computing costs ko cover nahi karti.
GitHub Blog ke mutabiq, "Today, a quick chat question and a multi-hour autonomous coding session can cost the user the same amount." Isliye company ab usage-based billing model par shift ho rahi hai, jahan users actual AI usage ke hisaab se pay karenge.
Kyun Aa Raha Hai Yeh Change?
GitHub ka kehna hai ki yeh change "better align pricing with actual usage" ke liye hai. Company chahti hai ki users sirf utna pay karein jitna woh actually use karte hain. Saath hi, surging demand for limited AI computing resources ke chalte, Copilot ko financially sustainable rakhna bhi zaroori hai.
Microsoft-owned GitHub ne yeh announcement kiya hai. Yeh change June 1 se apply hoga. Ab users ko apne actual AI usage ke hisaab se billing milegi.
Hamaari Baat: Copilot Users Ke Liye Kya Matlab Hai?
Seedha baat karein toh yeh change un users ke liye faydemand ho sakta hai jo kam AI requests karte hain. Lekin heavy users ke liye cost badh sakti hai. GitHub ka logic sahi hai — ek quick question aur multi-hour coding session ka cost same nahi hona chahiye. Lekin users ko ab apne usage patterns ko samajhna hoga aur accordingly plan karna hoga. Yeh ek positive step hai pricing transparency ke liye, lekin implementation dekhna hoga ki users ke liye kitna smooth hai.
Sources & References
- GitHub Blog — GitHub
