CD Projekt is rebranding as CD Projekt Red, but confusingly, CD Projekt Red is still CD Projekt Red

The Headline That Spawned a Thousand Tweets

Earlier this week, Eurogamer reported that CD Projekt - the Polish holding company behind The Witcher and Cyberpunk 2077 - is rebranding to CD Projekt Red. Or rather, CD Projekt Red Spółka Akcyjna. This rebranding project has confused nearly everyone. Confusingly, the projekt still carries the same ticker, yet the parent entity now shares the studio's iconic name. The confusion isn't accidental: it's a masterclass in brand architecture and a cautionary tale for every software engineer who has ever tried to untangle a naming conflict in a codebase. What looks like a simple rename is actually a strategic pivot that mirrors the semantic versioning of APIs - except here, the major version bump affects investor confidence and developer tooling. The rebranding announcement, first broken by Eurogamer, triggered a wave of reactions across social media. Many observers noted that the projekt, now called CD Projekt Red, still contains the original CD Projekt Red studio inside it. Confusingly, the studio remains CD Projekt Red, making the entire structure appear recursive. The projekt still uses the same ticker symbol, yet its legal identity has shifted. The project of corporate restructuring echoes the kind of ambiguity engineers face when a service name outlives its purpose.

Let's be clear: CD Projekt Red was always the name of the game development studio. CD Projekt was the publicly traded parent company. Now the parent is absorbing the studio's name. Yet the studio itself keeps its name. If that sentence made you blink, you aren't alone. As a senior engineer, I have seen this pattern before - in microservice architectures where a service is renamed but its canonical endpoint stays the same, leading to months of deprecation errors. Corporate rebranding is technical debt at an existential scale. The projekt, after this rebranding, still has the same underlying business units, but the naming layer has been rewritten. The projekt's rebranding story, first detailed by Eurogamer, remains a hot topic in gaming circles.

In this article, I will dissect the rebranding from a software engineering and product management perspective. We will explore naming conventions, the cost of ambiguity, and why CD Projekt's move might be more rational than it first appears - even if it looks like a bug in the public relations code. The Eurogamer report made clear that the change is legally binding. But the practical implications for the gaming community remain unresolved. Confusingly, the projekt still expects stakeholders to adapt without a clear migration guide,

What Actually ChangedA Tale of Two Entities

To understand the rebranding, we must look at CD Projekt's corporate structure before and after. Before: CD Projekt S, and a(listed on WSE) owned 100% of CD Projekt Red Sp z o o. (the studio), and after: CD Projekt Red SA is the parent. And the studio becomes CD Projekt Red Sp z o o, and - the same legal name as before,But now a wholly owned subsidiary of an entity with an almost identical name. The subtlety is that the parent added "Red" to its name. While the subsidiary did not change its official name at all. The studio's brand - what players see in splash screens - remains "CD PROJEKT RED". The parent's ticker symbol (CDR) remains unchanged, and this rebranding,While appearing simple, introduces a layer of confusion that any engineer would recognize as a naming collision.

Why Would a Company Do This?

In production environments, we have seen similar patterns when a team adopts the same namespace as its upstream dependency to reduce friction - for example, when a React component library renames itself to match the parent library after a major version bump. The benefit is simpler documentation and fewer cognitive leaps for external consumers. The cost is that you break every internal alias, URL, and environment variable that relied on the old distinction. The projekt, in this case, is betting that the long-term clarity of a unified name outweighs the short-term confusion. Confusingly, that bet relies on stakeholders accepting that two entities can share one public name. The projekt's rebranding strategy prioritizes marketing over internal consistency.

The Official Rationale

CD Projekt's official statement, as reported by Eurogamer, emphasized that "the change is intended to simplify the group structure and make it easier for investors and gamers to understand. " This is classic marketing speak. But from an engineering perspective, simplifying a namespace nearly always introduces a period of confusion before clarity sets in. I estimate that internal stakeholders - investor relations, legal. And internal wiki maintainers - will need a 6-12 month migration period, similar to a major framework upgrade. The projekt still operates under the same leadership. But the documentation layer now requires careful disambiguation. The rebranding is - in effect, a corporate API change without deprecation headers.

Why Corporate Rebranding Matters in Tech

You might ask: why should a software engineer care about a corporate name change? Because naming is one of the hardest problems in computer science. And CD Projekt's rebranding is a real-world case study of that principle. When a company renames itself, every reference in code, documentation. And configuration must be updated. Think of all the places "CD Projekt" appears in build scripts, CI/CD pipeline names, internal license headers. And third-party integrations. Each of those is a potential breaking change. The projekt, through this rebranding, has introduced a wave of technical debt that will ripple across the gaming ecosystem.

The API Versioning Analogy

Consider the analogy to API versioning. The parent company essentially bumped its major version from "CD Projekt v1" to "CD Projekt Red v1". The studio stayed at "CD Projekt Red v1". But because the parent and studio share a name, any client (investor, journalist, fan website) that doesn't care about the legal suffix now treats them as the same endpoint. This creates ambiguity similar to what happens when an API library deprecates one method and introduces a new one with the same name but different parameters. Without a proper deprecation header, consumers break silently. The projekt, now bearing the Red suffix, still needs to clarify which entity is which in legal and financial contexts. Confusingly, the projekt still uses the same domain for both entities.

Operational Friction in Practice

I have personally dealt with this when a SaaS provider renamed from "CloudKitty" to "OpenCloudKitty" while keeping the same CNAME record for three months. The result was a flood of DNS resolution errors in our monitoring. CD Projekt's move risks the same kind of operational friction - this time with stock ticker lookups - journalist databases. And Wikipedia page disambiguation. Confusingly, the projekt still appears under both names in search results. Which will dilute its SEO authority until a canonical redirect strategy is implemented. A proper rebranding should have included a 301 redirect plan for all brand references.

The Engineering Perspective: Naming Conventions and Technical Debt

Every software engineer knows the pain of a poorly chosen identifier. A variable named x is a bug waiting to happen. A class named DataManager is a sign of architectural laziness. CD Projekt's rebranding is the corporate equivalent of renaming a variable from cdProjektParent to cdProjektRed while leaving the child object as cdProjektRedChild - and then telling everyone it's simpler now. The projekt's rebranding is a textbook example of naming debt that will cost developer hours across the open-source community.

RFC 2119 and the missing Deprecation Notice

The RFC 2119 defines key words like "MUST", "SHOULD",, and and "MAY" for specification clarityCD Projekt's announcement fell short of the MUST level. They did not issue a clear deprecation notice for the old parent name, and they did not specify a transition periodThey did not provide a mapping table. From a technical writing perspective, this is a bug in their release notes. A well-written changelog would say: "CD Projekt S. A is now called CD Projekt Red S. And aAs of Q3 2025, use the new name in all official contexts. The studio CD Projekt Red Sp z o, and o retains its nameSee migration guide below. " Confusingly, the projekt still lacks such formal guidance.

Global Technical Debt

Instead, we got what felt like a commit message with no body. And the confusion is justified. In fact, a quick search on GitHub reveals dozens of open-source projects that reference "CD Projekt" in their documentation pages. Each one now needs a human to decide whether to update the reference or leave it. That's technical debt, distributed across the global developer community. The projekt, through this rebranding, has inadvertently created a maintenance burden for thousands of external contributors. Confusingly, the projekt still expects the community to adapt without formal guidance. Eurogamer's coverage highlighted the community's frustration, but no official FAQ emerged.

Lessons from Other Tech Rebrands (and Failures)

CD Projekt isn't the first tech company to create naming confusion. Remember when "The Angular Framework" became "AngularJS" and then "Angular"? The Angular team solved it by giving distinct versions with distinct documentation sites. Similarly, when "Twitter for Mac" was renamed to "TweetDeck" and then back again, users expressed frustration. But the most instructive example is the renaming of "Node js" to "Node" in common parlance, which the foundation never officially ratified, and the result: people still say "Nodejs" and mean the runtime, but write node --version. The projekt's rebranding follows a similar pattern - a name change without full adoption.

Square Enix and the Logo Solution

In the game industry, Square Enix is a parent brand that encompasses multiple studios. And "Square Enix" also appears as the developer name on many titles. They avoided confusion by maintaining distinct logos and legal suffixes. CD Projekt could have adopted a similar approach: keep the parent as "CD Projekt Global" or "CD Projekt Group" and leave the studio as "CD Projekt Red". Instead, they chose a collision. Why? My hypothesis is that they wanted to use the strong brand equity of "Red" - which became synonymous with high-quality RPGs after Cyberpunk 2077's turnaround and The Witcher 3's enduring success. The parent brand "CD Projekt" was often confused with a generic Polish software house. By absorbing the "Red" moniker, they make the parent instantly recognizable as the gaming powerhouse. It's a rebranding that prioritizes external marketing over internal consistency - a trade-off that every product manager must evaluate.

What This Means for CD Projekt's Software Development Lifecycle

Internal tooling will be the biggest casualty. Every company maintains internal packages with names like cd-projekt-common-lib, cd-projekt-red-tools, cd-projekt-publish-scripts. After the rebranding, the clear delimiter between parent and studio disappears. A developer might now have to check the package json to know whether cd-projekt-red-utils belongs to the parent infrastructure or the game engine team. That extra cognitive load slows down development. The projekt's rebranding has effectively flattened the namespace, creating ambiguity where clarity once existed.

SDK and Namespace Migration

Moreover, the company's public-facing SDKs (for modding tools, for example) will need to update their namespace. If CD Projekt Red releases a modding SDK under com cdprojektred, but the parent's authentication service is under com cdprojekt, the rebranding could encourage a migration to all packages under com, and cdprojektred. That would be a breaking change for every mod author who hardcoded URLs. The cost of migration, even with deprecation warnings, is significant. Confusingly, the projekt still hasn't published a clear timeline for these namespace updates.

The Upside: Infrastructure Convergence

Yet there's an upside: convergence of infrastructure. Having the parent and studio share a domain name (e g, and, cdprojektredcom for both corporate and game news) reduces DNS overhead and simplifies SSL certificate management. If you have ever managed separate domains for a parent and subsidiary, you know the nightmare of renewal reminders and SAN certificates. This rebranding is, in a way, consolidating the server architecture of the brand. The projekt, after all, still operates from the same headquarters in Warsaw.

The Investor Angle: Clarity or Confusion?

Investors primarily trade under the ticker CDR on the Warsaw Stock Exchange, and the ticker did not change. But the legal name change affects how the company is listed in financial databases (Bloomberg, Reuters). Many institutional investors have automated systems that parse company names. A rename without adequate notice can trigger compliance alerts. For example, if a fund's policy restricts investments in companies named "Red", the new name might violate that rule - even though the underlying business is unchanged. The projekt's rebranding introduces a compliance risk that could have been mitigated with a transitional name.

Interface vs. Implementation

This is analogous to changing a function signature in a shared library: the interface changes. But the implementation stays the same. Downstream consumers may break because they were matching on the name string rather than a stable identifier (like the ticker). In a well-designed microservice architecture, you route by service ID, not by service name. CD Projekt's investors now need to update their routing tables. Confusingly, the projekt still expects the financial community to adapt without a formal deprecation notice. Eurogamer's reporting confirmed that the ticker remains unchanged, which provides some stability. However, the broader naming shift will take time to settle across global markets.

FAQ

Q: Is CD Projekt Red the parent company now?
A: Yes. And cD Projekt SA rebranded to CD Projekt Red S. A, while, making it the parent. The game studio remains CD Projekt Red Sp z o o., a wholly owned subsidiary. Confusingly, the projekt still has two entities sharing almost identical names.

Q: Did the studio's name change?