Castle Story
Sauropod Studio · 2017 · $9.99 · Indie · deal grade B
Measured on 2026-09-24 10:44 UTC, 11 days ago. The whole catalog is re-measured daily; a game that just launched can move fast between passes.
- Estimated net residual revenue: $1.3k to $2.0k per month
- Opportunity: $3.1k per month at x1.90 dormancy
- Estimated lifetime owners: 510.0k
- 65% positive across 10654 reviews · 30.5 reviews/month
Why it's flagged
- Developer silent for 6.6 years
- Studio inactive: no public activity across 1 tracked titles
- Store page localized in only 2 language(s)
Analyst notes (AI-assisted)
Note written 2026-08-25; the live figures above take precedence over any numbers in it.
Castle Story is a cozy voxel-based tower defense and colony builder where players construct fortifications to survive enemy waves.
This indie title has shipped over half a million lifetime units and still generates solid four-figure monthly residuals despite dormancy since late 2024. The 65% positive score and engaged core community (60% still playing) suggest the game has genuine staying power as a value proposition at its current price point. For a small studio or publisher seeking low-risk catalog depth or a revival play with existing IP infrastructure, the brand recognition and workshop ecosystem (8400+ user creations) offer a soft landing; however, the lack of developer communication since mid-2024 and frustrated player sentiment around AI and pacing mechanics present a credibility rebuild challenge. Most realistic play: watch.
- Risk: Developer has entered ghost status; no public updates in 78+ months, no Discord communication since completion announcement, raising questions about post-acquisition support and IP stewardship.
- Risk: Player base is small and stable rather than growth-oriented; recent sentiment improvement is modest and review velocity is low, suggesting limited viral or comeback potential without substantial creative intervention.
- Risk: Recurring complaints center on AI difficulty, lack of game-speed controls, and optimization jank; these are structural design choices that would require development resources to address.
This case as Markdown · Estimates carry ±30-50% error per title.