Games and entertainment decision
Raconi Games
A competent developer can produce a narrow, self-hosted playable web version using existing engines (Godot/GDevelop), but reproducing a full commercial product experience (hosting, storefront, community, polish) is larger and not fully covered by the replacement.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off160 h to build
$0/mo4 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Raconi Games alternatives, with the arithmetic →
What a replacement has to do
- Player launches a web-hosted game build, plays levels, scores progress; developer provides builds and collects basic analytics.
What it still won’t have
- Proprietary assets, branding and storefront polish
- Any hosted dashboard or infrastructure provided by the original vendor
- User accounts, leaderboards, and community features if not implemented
- Integrated monetization/analytics tailored by the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Raconi Games does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal web-playable 2D game using Godot (latest stable). Stack: Godot for development, export to HTML5 (WebAssembly/WebGL), host static build on Netlify or S3+CloudFront, use Google Analytics (or Plausible) for play metrics. In scope: player controls, one playable level, score persistence (localStorage), build/export script, CI deploy to hosting, analytics events for session start/score, basic payment link page. Out of scope: multiplayer, dedicated backend user accounts, in-app purchases. Include error handling for asset load failures, automated export and deploy steps, and unit/scene tests where supported by the engine.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productLovable App — product page
- open sourceGodot Engine repository
- open sourceGDevelop repository
Integrity checks
What held up, and what did not.
