AI subscribers pay $200 but cost providers up to $3,500 a month, analysis finds

·1 views

A detailed analysis by SemiAnalysis found that heavy users of AI subscription plans such as ChatGPT Pro and Claude Max can consume tens of thousands of dollars worth of compute at API prices while paying only $200 per month. The real per-user loss after accounting for lower serving costs is estimated at around $3,500 monthly, roughly 17 times the subscription fee. The shortfall is covered by venture and institutional capital betting that today's usage habits will eventually translate into pricing power. Meanwhile, AI datacenter demand is redirecting DRAM production toward high-bandwidth memory, pushing consumer RAM prices two to three times higher and effectively spreading a hidden cost across all computer buyers. The dynamic mirrors past subsidy-driven growth plays like ride-hailing and cloud computing, but at a far larger multiple.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Dev Tutorial: Building an Orchestrator Agent for Multi-Agent AI LinkedIn Tool

A developer tutorial series on DEV Community details the construction of a multi-agent AI system designed to generate LinkedIn content for companies. Part 2 focuses on the Orchestrator Agent, which acts as a central coordinator — classifying topics, selecting content angles, and passing structured output to downstream agents. The project uses a modular file structure with separate Python files for each agent, alongside shared core utilities for LLM calls and data models. A key challenge encountered was inconsistent JSON output from local language models like Gemma2:2b, which sometimes returned malformed responses despite explicit formatting instructions. To address this, the author wrote a preprocessing function called strip_json_fences() that strips markdown fences, removes trailing commas, and normalises smart quotes before JSON parsing.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Cisco Ethical Hacker Curriculum Expanded Into Professional Penetration Testing Reference

A detailed, module-by-module reference guide has been developed based on the Cisco Networking Academy Ethical Hacker curriculum, extended to meet mid- and senior-level cybersecurity practitioner standards. The resource covers ten modules ranging from foundational ethical hacking concepts to post-exploitation techniques, cloud security, and professional reporting. It emphasizes that authorization is the single most critical distinction separating a criminal hacker from a legitimate security professional. Key concepts defined include ethical hacking, penetration testing, and vulnerability assessment, with the guide noting that pen testing is a formal, scoped subset of the broader ethical hacking discipline. The reference also addresses legal and procedural foundations, professional frameworks, and guidance on setting up isolated lab environments for safe practice.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Treating CI/CD Pipelines as First-Class Code Fixes Common DevOps Failures

A software developer outlines how poor CI/CD practices — such as hard-coded secrets, missing dependency caches, and monolithic pipeline scripts — led to slow feedback loops and unreliable deployments. The core fix proposed is treating pipelines as modular, version-controlled code with clearly defined inputs, outputs, and reusable jobs. Using GitHub Actions as the primary example, the article contrasts a flawed workflow with an improved version that pins action versions, caches dependencies, and protects secrets via environment-scoped variables. The improved pipeline separates build, test, and deploy into distinct jobs linked through artifacts, reducing redundant work and preventing accidental secret exposure in logs. The author notes these principles apply equally across GitHub Actions, GitLab CI, and Jenkins.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Weibo's Trending API Returns Only Phrases, Not Posts — Here's What You're Missing

Weibo's widely used hot-search endpoint returns only ranked phrases and heat scores, omitting post text, authors, timestamps, and comments, making it largely unsuitable for sentiment analysis or brand monitoring. A second endpoint, the hot timeline, returns full post objects including author details, repost and comment counts, and comment threads. In a comparative test, five trending posts expanded to 91 rows when comments were included, an 18x data multiplier from the same request budget. Most developers default to the hot-search board because it appears first in search results and returns clean JSON, creating a false impression of completeness. Analysts building social listening pipelines on Weibo are advised to use the hot timeline endpoint with comments enabled to capture meaningful content.

0 comments Read more at DEV Community