Yes. Hollow Knight is an indie game made by Team Cherry. The studio explicitly describes itself as an indie developer in Adelaide, and the original game’s Steam listing credits Team Cherry as both developer and publisher. Its substantial world, later success and recognizable identity do not cancel that production background.
Begin with evidence stronger than the art style
Hollow Knight’s hand-drawn presentation is recognizable, but hand-drawn art is not the reason it qualifies as indie. The stronger evidence is the developer’s own description and the original release’s developer and publisher credits. Those identify the production behind the game.
This distinction matters even when the answer seems obvious. If indie meant a particular style, a visually similar corporate production would automatically qualify. Looking at the studio first gives a definition that works consistently across different art styles instead of relying on a familiar aesthetic association.
Identify Team Cherry’s role
Team Cherry’s official about page calls it an indie games developer based in Adelaide, South Australia. The Steam listing for Hollow Knight names Team Cherry as developer and publisher and records the PC release in February 2017. These are direct, checkable facts rather than conclusions drawn from a fan-made genre list.
They establish a straightforward independent-development example. They do not require the claim that nobody outside the core team contributed. Music, localization, technical help and other specialist work should be understood through the credits, without turning independent production into a demand for complete creative isolation.
For the documented reference, see Team Cherry’s first-party studio description.
A large world does not impose a different ownership category
A game’s map size, challenge or playtime does not reveal who owns the studio. A focused team can spend substantial time on one world, reuse systems thoughtfully and build depth through interconnected spaces. The outcome can feel expansive without requiring the organization of a major corporate franchise.
That is an explanation of how scale and independence can coexist, not a claim about an undisclosed production budget. Avoid inventing a precise cost or labour total to make the story sound more dramatic. The classification is already supported by the documented developer relationship.
Keep success separate from a change in ownership
A game does not automatically stop being indie when it reaches a large audience or becomes a recognizable brand. Sales and cultural visibility describe reception. A change in ownership would be a separate business event requiring its own evidence.
This is especially important when a celebrated independent game becomes a common reference point. Calling it too successful to be indie changes the definition after the fact. Use dated company information if you are discussing the present studio, and preserve the original production context when discussing the original release.
Check the exact release when discussing publishing
A PC release, console version, physical edition or regional distribution arrangement can involve different partners. A company appearing on one edition does not automatically rewrite the developer’s role across every release. Specify the product you are looking at.
For a purchase, verify platform support and the edition’s current listing. For a production-history question, distinguish development, porting, publishing and distribution. These responsibilities can be shared, and treating every credit as proof of an acquisition produces confusion where the actual roles are more informative.
Describe the game without promising a particular experience
Hollow Knight is a clear independent-development example, but that label alone does not tell a player whether they will enjoy it. Exploration, combat, navigation and difficulty are separate questions from how the studio is organized.
A useful recommendation would therefore pair the production description with an accurate account of the gameplay and the player’s preferences. You can recognize Team Cherry’s independent work without assuming every indie fan likes the same challenge, or that one successful game represents the entire range of independent development.
Frequently asked questions
Was Hollow Knight made by Team Cherry?
Yes. Team Cherry is credited as developer, and its official studio page identifies it as an indie developer. The original PC listing also credits Team Cherry as publisher.
Does being popular make it stop being indie?
No. Popularity is not an ownership change. A claim about a new corporate relationship needs separate evidence rather than an assumption based on sales or recognition.
Does indie mean the game must be short or easy?
No. Length and difficulty are design characteristics. Independent developers can make demanding, substantial games as well as short or relaxed experiences.