Character sheets look simple until a game starts calculating abilities, equipment, health, spells, levels, and rules. Evrone developer Anton Bogdanov met that problem while learning Dungeons & Dragons. He wanted a faster tool, so he started Charkeeper in 2025.
Why another character manager?
Anton wanted:
- A responsive, lightweight interface.
- Freedom from rigid character limits.
- One application for different RPG systems.
Charkeeper also gives Game Masters access to sheets, inventories, health, and statistics. A GM can prepare an item and assign it directly instead of exchanging screenshots or files.
One codebase, several platforms
Charkeeper runs as:
Evrone’s developer chose Tauri instead of rebuilding the frontend for mobile. The same SPA powers the web and Telegram versions, while Tauri packages it for native platforms.
The stack
- Backend: Ruby on Rails + RSpec
- Frontend: SolidJS
- Cross-platform: Tauri
- Telegram: Telegram Mini Apps SDK
Rails handles business logic, while SolidJS keeps the client compact.
A model built for new RPG systems
Different games use different names for similar mechanics. Charkeeper uses shared structures for common entities and extra parameters for special rules. This lets Anton add systems without rebuilding the character workflow.
The roadmap includes DC20, Vagabond, Nimble RPG, better imports, integrations, and a universal homebrew builder.
Evrone supports Charkeeper as an engineering experiment shaped by its community. The project shows how one developer’s hobby can evolve when architecture, open source, and player feedback work together.
The project’s source code is hosted on GitHub, specifically in the kortirso/charkeeper repository.
🧩 Building an RPG Character Platform Without Five Separate Codebases.
Top comments (0)