Vaibie
Vibe code playable browser games and 3D worlds with AI, rendered live with three.js.
For browser-game prototyping, Vaibie removes the boring middle: no backend, no asset pipeline, no hosting. Per-project SQLite and a public play URL mean you can share something playable the same afternoon you thought of it. The REST API's build modes — outline, standard, deep, ultra — let you decide how much AI scaffolding to buy (100 credits for an outline, 300 for the three-pass ultra build), and 1-credit BYO-LLM pushes from Claude Code or Codex are the cheapest path in. The catch is scope: this is a rapid-iteration playground, not a production pipeline, and heavy prompts at 2× token markup burn credits fast.
Verified 9d ago · liveness 66/100 · cite: rightaichoice.com/tools/vaibie
- Indie developers prototyping a browser game in an afternoon
- Educators who need an interactive demo students can play via a link
- Hobbyists experimenting with AI-generated 3D worlds and physics sandboxes
- Designers iterating on game mechanics through conversation, not code
- Professional studios needing source control, asset pipelines, and a full engine
- Teams shipping native desktop or mobile builds
- Complex multi-file projects with custom build toolchains
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Vaibie if you need a full engine with source control, asset pipelines and native builds — it is a browser-based rapid-prototyping studio, not a production game pipeline.
API /prompt calls bill LLM tokens at 2× markup, so long generation chats cost roughly double the raw model rate
Vaibie runs on pay-as-you-go credits (1 credit = $0.01) with no subscription required, which fits hobbyists and indie devs who iterate in bursts. A prototype session — a project spin-up plus a handful of pushes — lands in the low single-digit dollars. Compare against engine-based pipelines your team pays for monthly, or general app builders with tiered subscriptions; Vaibie is cheaper for occasional prototyping and more expensive per hour for heavy frontier-model loops because prompt tokens
In short
Vaibie — Vibe code playable browser games and 3D worlds with AI, rendered live with three.js. Best for Indie developers prototyping a browser game in an afternoon, Educators who need an interactive demo students can play via a link, Hobbyists experimenting with AI-generated 3D worlds and physics sandboxes. Free to use.
What's new in Vaibie
Checked 9 days agoAcross the latest 1 update: 1 changelog entry.
Viability Score
How well maintained and how widely used is Vaibie? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Turn natural-language prompts into playable browser games
- Render 3D worlds live with three.js in the page
- Build 2D arcade games and interactive web apps in vanilla JS
- Switch between Claude, GPT-5, Gemini 3 Pro, Grok, and DeepSeek per prompt
- Conversational refactors with full game context
- 1-click auto-debug on console errors
- Per-project SQLite database queried via window.vaibie.db
- Leaderboards and high-score tables persisted server-side
- Multiplayer-ready shared state via the per-game database
- Public play URLs and embed snippets for every project
- Fork and remix community games from the gallery
- REST API for external coding agents like Claude Code and Codex
- Build modes: outline, standard, deep, ultra
- Chat studio with iframe sandbox and live preview
- Human-first editor for manual polish after API scaffolding
About Vaibie
Vaibie turns a written prompt into a playable browser game or interactive 3D scene, rendered live with three.js inside the page. Type something like "a 3D pinball table where the ball is a tiny moon," and the AI writes the HTML/CSS/JS, drops it into an iframe sandbox with a live preview, and lets you play it immediately. No build step, no install, no engine to learn. The intended audience is broad: indie and hobbyist game makers who want a prototype before lunch, designers who think in mechanics rather than code, and educators who need something clickable to hand to a class. Frontier models — Claude, GPT-5, Gemini 3 Pro, Grok, and DeepSeek — are switchable per prompt, which lets you reroll a stubborn generation on a different model instead of rewriting the brief. What separates Vaibie from a generic AI coding assistant is the batteries-included layer. Every project ships with its own SQLite database reachable through window.vaibie.db, so leaderboards, player profiles, saved runs, and world state persist server-side without you standing up a backend. Shared state across players is available through that same per-game DB, and the chat handles conversational refactors like "make the boss faster" alongside 1-click auto-debug on console errors. Each project also gets a public play URL and an embed snippet, and you can fork games from the gallery to remix them. A second workflow skips the studio entirely: drive a Vaibie project from Claude Code, Codex, or your own scripts through the REST API — 10 credits to create a project, 1 credit per BYO-LLM code push — then return to the web editor for polish. The API also supports build modes: outline (1 call, 100 credits), standard (1 call), deep (2 calls, 100 credits), and ultra (3 calls, 300 credits). Vaibie is part of the Alexiuz ecosystem and signs in with a single Alexiuz account. It is early-access software, now at v0.7.70 according to the site footer (a June 2026 changelog entry noted v0.7.29). Credit consumption scales with usage and model choice, with 1 credit equal to $0.01 and top-ups handled at alexiuz.com/credits.
Behind the Verdict
Vaibie occupies a narrow but useful niche: it is not a general app builder like Lovable or v0, and it is not a full game engine like Unity or Godot. It is a prompt-to-playable-loop studio for browser games and three.js scenes. Strengths. The batteries-included layer is the real differentiator. Every project gets its own SQLite DB, reachable from your game with window.vaibie.db, so leaderboards, saved runs, player profiles, and shared world state persist server-side without you writing a backend. Multiplayer-ready shared state rides on that same DB, which is the part most AI code generators make you build yourself. Model switching per prompt (Claude, GPT-5, Gemini 3 Pro, Grok, DeepSeek) is genuinely useful when a generation stalls — reroll on a different model instead of rewording the brief. The API-first path is well designed: write locally in Claude Code or Codex, push with PUT /projects/{slug}/code for 1 credit, then polish in the studio. Build modes with a plan you can edit before the build call (outline → deep with a custom "plan" string) is a thoughtful touch for anyone who wants control over what the model commits to. Weaknesses. It is browser-first, no offline or native deployment is mentioned, and it is early-access software (v0.7.70 per the footer). Credits are the cost model: 1 credit = $0.01, POST /projects is 10 credits, each BYO-LLM push is 1 credit, and API /prompt calls bill LLM tokens at 2× markup, same as the studio. A long iteration session with a frontier model adds up. Free-tier rate limits are 30 req/min, 500 req/hour, 5000 req/day per key, with unauthenticated reads at 15 req/min — fine for experimentation, tight for anything automated at volume. Where it fits. Indie devs and hobbyists who want a playable prototype in one sitting. Educators who need a link students can open. Designers iterating on mechanics through conversation. Anyone who wants leaderboards and persistence without touching infrastructure. Where it doesn't. Professional studios needing source control, asset pipelines, and a full engine. Teams shipping native desktop or mobile builds. Complex multi-file projects with custom toolchains. Cost-sensitive heavy users running long generative loops.
Researching Vaibie? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Vaibie actually fits — and what changes day-one when you adopt it.
Open the studio, type a prompt for a 3D pinball table, switch to a different frontier model when the first generation stalls, then ask the chat to add a high-score table.
Outcome: A playable browser game with a working leaderboard and a public play URL, all from prompts and without touching a backend.
Write the game HTML/CSS/JS locally, mint a vbk_live_ API key, POST /projects to spin up the project (10 credits), then PUT /projects/{slug}/code to push (1 credit per push), iterating locally and pushing when ready.
Outcome: Code stays under the developer's own tooling, while Vaibie hosts the game, wires the SQLite DB, and exposes a play URL for sharing.
Describe an interactive physics playground with voxel landscapes in the studio, check the live preview, and share the public play link or embed snippet with students.
Outcome: Students open a link and interact with the demo immediately; no install, no accounts for players, and per-project DB persistence if the demo saves state.
Use Cases
- Create a 3D procedurally generated planet explorer
- Build a 2D arcade shooter with leaderboards in minutes
- Prototype an idle clicker game with persistent state
- Design a physics playground with voxel landscapes
- Develop a multiplayer co-op game using shared database
- Generate an interactive data dashboard as a web app
- Scaffold a game locally in Claude Code or Codex and push it via REST API
Models Under the Hood
as of 2026-10-08
Limitations
- Version v0.7.71 per the site footer; the June 2026 changelog note recorded v0.7.29.
- Runs entirely in the browser with three.js and vanilla JS — no native or offline deployment is mentioned.
- Models are presented as a selectable fleet (Claude, GPT-5, Gemini 3 Pro, Grok, DeepSeek) accessed per prompt in the studio or via a REST API for external coding agents.
as of 2026-10-01
Verification history
We have re-verified Vaibie 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Vaibie tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Hobbyists and students who want to try prompt-to-playable browser games without spending anything
What this tier adds
Free entry point: Alexiuz sign-in, chat studio with live three.js preview, model switching, public play URLs and gallery forking.
Pay-as-you-go credits
Per-credit
Ideal for
Indie developers and coding-agent users who push code via the REST API and only pay when they generate
What this tier adds
Credit billing on top of the free studio: 10 credits per project spin-up, 1 credit per BYO-LLM push, and 2× markup on API prompt tokens.
Where the pricing makes sense
The company stage and team size where Vaibie's pricing actually pencils out — and where peers do it cheaper.
Vaibie runs on pay-as-you-go credits (1 credit = $0.01) with no subscription required, which fits hobbyists and indie devs who iterate in bursts. A prototype session — a project spin-up plus a handful of pushes — lands in the low single-digit dollars. Compare against engine-based pipelines your team pays for monthly, or general app builders with tiered subscriptions; Vaibie is cheaper for occasional prototyping and more expensive per hour for heavy frontier-model loops because prompt tokens
Setup time & first value
How long it actually takes to get something useful out of Vaibie — broken out by persona, not the marketing-page minute.
Hobbyist in the studio: about a minute to sign in with an Alexiuz account and start prompting; a playable result within a few minutes per generation. Developer pushing code via the API: a few minutes to mint an API key from the account page and run the create-project + push-code curl calls. Educator: same as hobbyist — sign in, prompt, share the play link the same session.
Switching to or from Vaibie
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-coding browser games with raw three.js: prompt the scene in Vaibie's studio, then polish the generated html/css/js in the human-first editor without rebuilding the sandbox or hosting layer.
- →From a generic AI app builder: move the game-shaped parts over — Vaibie already wires per-game SQLite, leaderboards and shared state, so you stop hand-rolling persistence per project.
- →From local-only prototypes in Claude Code or Codex: keep writing locally, then POST /projects and PUT /projects/{slug}/code to push each revision for 1 credit and get a public play URL.
- ↗To a production engine (Unity, Godot): download the project via GET /projects/{slug}/export (.vaibie) and rebuild the gameplay in the engine's own scene/asset pipeline.
- ↗To a self-hosted three.js build: pull the current html/css/js with GET /projects/{slug}/code and point it at your own database instead of window.vaibie.db.
- ↗To a general-purpose app builder: export the code and re-implement the persistence layer, since Vaibie's per-game SQLite and leaderboards don't carry over.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Vaibie”, and we withheld 6: 6 could not be judged, because “Vaibie” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Vaibie.
Official links
Tools that pair well with Vaibie
Common stack mates teams adopt alongside Vaibie, with the specific reason each pairing earns its keep.
Opus
Opus converts text prompts into playable 2D and 3D game worlds, with AI co-pilots and multi-platform export.
Godot Mcp Pro
MCP server with 187 tools that lets Claude or Cursor drive the Godot 4 editor live over WebSocket.
Glade Mcp
Project-aware AI assistant for Unity and Godot that reads your scripts, scenes, and hierarchy, then acts in the editor
Featured Head-to-Head Comparisons
Vaibie vs Cognition Ai
Vaibie wins for rapid game prototyping and creative coding with multiple AI models; Cognition's Devin is unmatched for enterprise production automation with financial guarantees. Choose Vaibie for fun, shareable browser games; choose Cognition for mission-critical engineering at scale.
Vaibie vs The New Black
Vaibie and The New Black serve entirely different industries — game prototyping vs fashion design. Choose Vaibie if you want to turn prompts into playable browser games using multiple AI models and quick iteration. Choose The New Black if you need AI-generated apparel designs with production-ready exports. Neither replaces the other; your decision hinges entirely on your domain.
Vaibie vs Bito
Vaibie and Bito serve entirely different needs. Vaibie is a game prototyping playground for indie devs and educators, turning prompts into playable 3D worlds. Bito is an enterprise context layer for AI coding agents, solving cross-repo complexity in large engineering teams. Choose Vaibie for creative speed and Bito for architectural depth.
Alternatives to Vaibie
View all
Opus
Opus converts text prompts into playable 2D and 3D game worlds, with AI co-pilots and multi-platform export.
Godot Mcp Pro
MCP server with 187 tools that lets Claude or Cursor drive the Godot 4 editor live over WebSocket.
Frequently Asked Questions
Used Vaibie? Help shape our editorial sentiment research.