惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News | PayPal Newsroom
P
Proofpoint News Feed
Cyberwarzone
Cyberwarzone
C
Cisco Blogs
SecWiki News
SecWiki News
Know Your Adversary
Know Your Adversary
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Vercel News
Vercel News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
罗磊的独立博客
NISL@THU
NISL@THU
WordPress大学
WordPress大学
Hacker News - Newest:
Hacker News - Newest: "LLM"
T
Threat Research - Cisco Blogs
AI
AI
Simon Willison's Weblog
Simon Willison's Weblog
Security Archives - TechRepublic
Security Archives - TechRepublic
有赞技术团队
有赞技术团队
L
LINUX DO - 热门话题
Hacker News: Ask HN
Hacker News: Ask HN
V
V2EX
G
GRAHAM CLULEY
TaoSecurity Blog
TaoSecurity Blog
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
F
Fortinet All Blogs
博客园 - 叶小钗
博客园 - 三生石上(FineUI控件)
云风的 BLOG
云风的 BLOG
Recorded Future
Recorded Future
Latest news
Latest news
The Hacker News
The Hacker News
aimingoo的专栏
aimingoo的专栏
T
Troy Hunt's Blog
S
Schneier on Security
I
Intezer
Google DeepMind News
Google DeepMind News
A
Arctic Wolf
Apple Machine Learning Research
Apple Machine Learning Research
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
T
Threatpost
爱范儿
爱范儿
The Register - Security
The Register - Security
S
SegmentFault 最新的问题
Blog — PlanetScale
Blog — PlanetScale
博客园 - 聂微东
宝玉的分享
宝玉的分享
Recent Commits to openclaw:main
Recent Commits to openclaw:main
美团技术团队
B
Blog RSS Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The Subscription You Did Not Ask For
Vivian Voss · 2026-05-01 · via DEV Community

A hand-drawn editorial illustration of a small modern design studio in landscape view. A young developer with long dark wavy hair and a pink cat-ear headset, sits at a wooden desk holding an open brown leather wallet, looking down into it with quiet sadness. Behind her, a Studio Display shows the readable email

In the Net, Episode 01

In 2012, Adobe shipped Creative Suite 6. A studio could buy the Master Collection once, for around two thousand five hundred euros per seat (US list price was 2,599 dollars), and run it for years. Thirteen years later, the same studio leases Adobe Creative Cloud All Apps for around 743 euros per seat per year (Adobe Germany list price, May 2026). The tools have not got dramatically better. The architecture under the licence rather has.

This is the first episode of In the Net: a series on the documented mechanics of vendor lock-in. The premise is simple. Every platform tells you how to come in. The architecture tells you whether you can leave. We will look at how each major platform's promise was built, what the lock-in mechanisms are, why the documented exit does not work as advertised, and what the realistic escape routes look like.

We start with Adobe because the pattern is at its clearest. The promise was good. The promise was kept for thirty years. The architecture under the subscription, however, is a separate story.

The Promise, Honestly

Adobe Creative Suite was, for three decades, the most defensibly chosen tool stack in design and publishing. Photoshop appeared in 1988. Illustrator in 1987. InDesign in 1999. Premiere in 1991. The applications were excellent, kept in active development, and produced the file formats that the entire commercial design industry settled on.

A studio buying CS6 in 2012 made a rational decision. Pay once, run forever. Major upgrade cycle every three years. Predictable cost, predictable workflow, the same key bindings their staff had learned over a decade. Nothing about that was a trap.

This matters. Lock-in stories are most useful when they begin with the promise that was real. Adobe's promise was real. The mechanism that came after did not undo the original promise. It changed the architecture under it.

The Day the Architecture Changed

In May 2013, Adobe announced that CS6 was the last perpetual-licence release of Creative Suite. Going forward, the only way to use Photoshop, Illustrator, InDesign and the rest would be Creative Cloud, a monthly subscription. The applications continued to ship. The licence did not.

The transition was managed elegantly. Existing CS6 owners could keep using their software. New customers and upgrades, however, were on the subscription path. Within two years, the perpetual market was effectively closed.

Three lock-in mechanisms were wired into the new architecture.

The First Hook: File-Format Binding

Adobe's file formats are proprietary and rich. PSD carries Smart Objects, Layer Effects, Adjustment Layers, and a depth of state that no open format mirrors completely. AI carries Illustrator's specific path semantics. INDD, more than the others, has effectively no portable equivalent: IDML exists as an interchange format, but loses live links, master-page state, and complex layout work.

The judgement is not that Adobe should publish their file formats. The judgement is that the file format is the lock. A studio that has spent a decade building PSDs is not just buying software; it is paying rent on its own back catalogue.

The Second Hook: Cloud-Library Binding

Creative Cloud syncs fonts, brushes, asset libraries, colour palettes, and shared resources between the applications and across teams. Cancel the subscription, and the synchronised assets become unavailable. Some assets remain locally, others depend on the licence. The working environment is not portable.

This is a more recent hook than the file format. It came in over the years between 2014 and 2020, with Creative Cloud Libraries, Adobe Fonts (formerly Typekit), and the deeper integration between Photoshop and Lightroom Cloud. Each individual feature was a real productivity gain. The cumulative effect was that the user's working environment lived inside Adobe's account, not on their own machines.

The Third Hook: Cancellation Architecture

Adobe's Annual Plan, billed monthly, carries an Early Termination Fee equal to 50 percent of the remaining months on the contract. A user three months into a twelve-month plan who cancels owes nine months at half rate.

In June 2024, the US Department of Justice, on behalf of the Federal Trade Commission, filed suit against Adobe alleging that this fee was hidden behind layered cancellation flows and that the company had violated the Restore Online Shoppers' Confidence Act. The case (FTC v. Adobe) is, as of this writing in 2026 and to my knowledge, still in motion. Whatever the eventual outcome, the architecture itself is documented in the agreements.

A subscription that costs more to leave than to keep is not, by any honest reading, a subscription one can leave at will. The architecture says what the marketing copy does not.

The Standing: Market Power and How the User Is Treated

Two further dimensions matter, and neither is reducible to price. The first is market power. The second is how the user is treated in the contracts the user has signed.

Market position. Adobe holds, by industry-aggregator estimates, more than eighty percent of the creative-software market. Photoshop alone accounts for around forty-two percent of the graphic-design segment, InDesign for around twenty-six percent, Illustrator for around twelve percent (multiple market-research aggregators citing 2024 figures, e.g. ElectroIQ, Bayelsawatch). The consequence is that Adobe's three core file formats, PSD, AI and INDD, are the de-facto industry standard. A studio that has migrated to Affinity, Krita or any other alternative still receives PSDs from clients, suppliers and partners. The lock-in is not only at the studio level. It is at the level of the entire industry's file-exchange protocol. An agency that holds out alone has not actually escaped; it has only insulated its own machines, while still negotiating in someone else's format.

This is the difference between a Lock-in and a Quasi-Monopoly. The Lock-in keeps the individual customer. The Quasi-Monopoly keeps the customer's customers, and through them, the customer.

How the user is treated. In February 2024, Adobe quietly updated its Terms of Service to include language that, in many readings, granted Adobe broad rights to access user content, including to train generative AI models. The change went largely unnoticed for months. In June 2024, Adobe pushed a routine re-acceptance pop-up to Creative Cloud and Document Cloud users, and many users encountered the new language for the first time as a forced confirmation: accept, or lose access to your tools. The artist community responded with a sustained backlash. Adobe issued clarifications on its own blog (10 June 2024), and on 24 June 2024 published revised Terms that explicitly state Adobe does not train generative AI on customer content (with the exception of submissions to the Adobe Stock marketplace), and that the company never has.

The clarification is, as far as one can verify, accurate. The clarified Terms are clearer than the prior wording. The question that remains is what was being granted before the backlash, and why a company with this market position needed to be told by its own users that this is not the language a creative tool's licence ought to contain. The original wording was not a slip. It was the architecture of the contract a corporation believed it could propose to its captive user base. That belief, and not the words themselves, is the part of this story that does not get corrected.

These two dimensions, market position and contractual stance, change the reading of the price. The price is not only what the studio pays in money. The price is also what it accepts, by signing the contract, about the rights it retains over its own work, and about the position from which the contract is offered. A subscription is the lower-cost end of the price. The other end is harder to put a number on.

The Exit That Isn't

Adobe will tell you the exits exist. They are correct, technically. They are wrong, operationally.

Export your PSD to a portable format. Smart Objects flatten. Layer Effects sometimes lose their parameters. Adjustment Layers may bake into the underlying pixels. The file opens elsewhere; it is no longer the file you built. Anyone who has tried to recover an old PSD in another tool has met this in person.

Cancel your subscription. The Early Termination Fee triggers. The flow is layered. Customers report that the cancellation requires multiple confirmations, optional retention offers, and live-chat negotiation. The exit is documented. It is also a fence.

This is a Lock-in by design. Not in the sense that someone in a boardroom said "let us trap our users". In the sense that the architecture, taken as a whole, produces the outcome that users do not leave even when they would prefer to. That is what an architecture is: the outcome the structure makes likely, regardless of intent.

The Price

For a studio of ten seats on Creative Cloud All Apps, the recurring cost is in the order of seven thousand four hundred euros a year, every year, with no terminating event. Compare to the perpetual model: ten CS6 Master Collection licences in 2012 would have cost around twenty-five thousand euros and remained usable for the years the team chose to run them. The subscription model has been more profitable for Adobe and more expensive for studios across any horizon longer than a few years.

For a studio that wants to leave, the cost is migration. Months of file conversion, weeks of retraining, and a tail of legacy work that will, rather inevitably, not transfer cleanly. This is not a fee Adobe charges; it is a cost the architecture imposes.

The Escape Route

The alternatives are real and professional, but the landscape has shifted in 2024 and 2025. Two of the strongest names have changed owners. The migration paths are still good. They simply require attention.

Affinity, by Serif (now Canva). In March 2024, Canva acquired Serif for approximately three hundred million pounds (around three hundred and fifty million euros at the time, as reported by Canva's own newsroom). In October 2025, the three Affinity applications (Photo, Designer, Publisher) were consolidated into a single application called Affinity by Canva, version 3.0. The new model is free with a Canva account. AI features are locked behind a Canva Pro subscription, around one hundred and ten euros a year. The original Pledge given at acquisition included a commitment to perpetual licences; that commitment was, by the publisher's own communication at the version 3.0 launch, replaced when the new model launched. Affinity remains a strong one-to-one replacement for the Adobe core, with direct PSD and AI import. It is also itself an example of the pattern this series tracks.

Pixelmator Pro, by Pixelmator (now Apple). Apple announced its acquisition of the Pixelmator team in November 2024 and completed it in February 2025 (MacRumors, TechCrunch). The standalone perpetual licence is still listed on the Mac App Store at around fifty euros (US list 49.99 dollars). Newer features, such as the Warp tool added with the iPad release in January 2026, are exclusive to Apple Creator Studio: a subscription bundle priced at 12.99 dollars per month or 129 dollars per year (US list, around twelve euros a month or one hundred and twenty euros a year), which ships Pixelmator Pro alongside Final Cut Pro, Logic Pro, and the iWork suite. The standalone path remains, but the rate of new feature development sits inside the bundle.

DaVinci Resolve, by Blackmagic Design. Free for video editing, with a Studio version available as a one-time purchase. The free version includes colour grading that has, afaik, been used on theatrical productions; Blackmagic Design lists notable feature-film credits on its own product pages. The most stable of the alternatives in this list, with a perpetual non-subscription model that has held since 2009.

Krita. Free and open source, professional digital painting application maintained by the KDE community. Strong brush engine, deep tablet support, scriptable. Stable.

GIMP and Inkscape. Free, photo and vector. Robust and feature-complete for most workflows. The user experience is, honestly, dated, and migration cost from Adobe is real work because the muscle memory does not transfer cleanly. They are the right choice for budget-constrained teams or FOSS-aligned organisations who can absorb the UX cost.

Capture One. A direct Lightroom alternative. Individual perpetual licences are still offered (US list 299 dollars, around two hundred and seventy-five euros). Multi-user studios, however, were moved to subscription-only in 2024 (PetaPixel reported a 344 percent multi-user pricing change). This is the same pattern as Adobe: perpetual quietly retained for individuals, removed for the larger commercial users.

The maths still works. Adobe Photoshop and Lightroom Photo plan in Germany is around 17.99 euros per month (annual commitment, billed monthly) or about 142 euros per year prepaid; Photoshop Single App and Creative Cloud All Apps cost more (Adobe Germany list, May 2026, with VAT). Affinity is free with an account. Pixelmator Pro standalone is around fifty euros, perpetual. DaVinci Resolve is free. The break-even against any Adobe subscription happens within months, not years.

The harder question is which of the alternatives stays an alternative. Two of the largest names have changed owners in eighteen months, and the change has, in both cases, moved the architecture in directions worth watching. This is not an argument against the alternatives. It is an argument for the only sustainable strategy in this landscape: attention.

What to Take Home

If your tools come with a recurring bill, your back catalogue lives in someone else's licence. If your tools come from a vendor that holds eighty percent of the market, the industry's standard formats are theirs as well, and your migration is incomplete even when your studio has finished it. If your tools come with Terms of Service that granted broad rights over your content until your community noticed, the architecture of the contract is a separate question from the price tag.

The pattern repeats. The market holds the lock-in. The contract holds the user. Even the alternatives need watching, because two of the largest names have changed owners in eighteen months. The subscription you did not ask for is the architecture you signed up for: the rent has gone up, the formats have stayed standard, and the wording in the agreement has, for at least one entire spring, said something the publisher later had to take back.

The tools have not got better. The rent has, the standing has not, and attention is the only price that scales.

Read the full article on vivianvoss.net →


By Vivian Voss, System Architect & Software Developer. Follow me on LinkedIn for daily technical writing.