The source research uses dated evidence, not a current price list. “Free,” “private,” “owned,” and “exportable” answer different questions; none should stand in for the others. Labels are defined on index > How to read claims.
Choose the bill before the build
| Expense or route | Source-grounded statement | What still needs checking |
|---|---|---|
| ChatGPT-connected Build | D: the July 16, 2026 article describes Free/Plus/Pro accounts powering live edits without Websim credits | The connected account and active plan limits; no unlimited usage or separate fresh allowance is established |
| Websim model route | D: the guide describes model/credit-based generation | Current signed-in prices, available models, entitlements, and displayed operation cost |
| Visitors’ runtime AI | D: the October 28, 2025 AI article uses broad free-access language but explicitly quotes 100 credits per image-to-image use | Current payer, credit bucket, limits, and operation-specific exceptions; the dated figure is not a current quote |
| Credits and rewards | D: January discontinued free daily credits, sponsorship/creator program, and video rewards; the August update announced video rewards again | Current eligibility and rules; the August statement does not restore other discontinued programs or guarantee income |
Evidence: Build, AI abilities, January credit update, August update, guide, and plan screen.
O: the original research found the plan page redirected to login. Guide examples of standard 100-credit runs and premium tiers are not sufficient evidence for today’s catalog. No dollar prices, daily allowances, current model roster, or current runtime payer are invented here.
R: inspect the active route and the specific operation’s current UI. ChatGPT build usage is not evidence that runtime AI, image operations, storage, or visitors are funded through the same account. Reuse assets, tweak parameters, and edit narrowly before considering larger generation or refactoring; never put an AI request in a render loop.
Project privacy is not asset privacy
D: the guide distinguishes Unlisted, accessible to anyone with the link, from Private, described there as creator-only. It also says approved uploads enter the global Asset Browser. These are separate visibility boundaries.
R: check current entitlements, actual visitor access, and any newer exceptions. Do not upload confidential documents, secrets, or sensitive images on the assumption that a private project protects every uploaded asset. A link that works for the creator does not establish the intended audience’s access.
The quickstart poster compresses this warning; this explanation preserves the distinction rather than reading the poster as a complete access policy.
Ownership and permitted use
D: terms section 2, cited by the source with an August 29, 2024 date, retains ownership of content/output while granting a broad perpetual, irrevocable, sublicensable platform license including improvement/training. Private visibility is not a documented no-training promise in this evidence.
R: verify code and media rights before external reuse or sale. Remixability is not public-domain status, and content ownership does not settle copyright certainty or third-party asset rights. The terms also restrict automated extraction and reverse engineering; a community endpoint list is not permission for bulk scraping or a supported export contract. Confirm automation/export support with Websim.
This is an explanation of the supplied evidence, not a fresh legal or account-entitlement determination. The source also cites privacy information when discussing critical use.
Stay or migrate
| Intended use | Source recommendation | Reason |
|---|---|---|
| Games, interactive art, AI experiments, community prototypes | Strong fit | Rapid iteration, hosted capabilities, and community feedback match the stated purpose |
| Larger component-based app with persistent roles | Possible, conditional on the exact requirements | Verify the particular framework and permission model rather than relying on the general announcement |
| Sensitive production, paid critical workflow, required availability | Do not assume readiness | Establish trusted execution, security, backup/restore, observability, quotas, support, and contractual guarantees |
| Self-hosting or avoiding lock-in | Treat as a real migration | Confirm supported source/data export and rights; replace managed AI/auth/data/multiplayer, migrate data, and re-exercise behavior |
D: View Source is documented; a historical 2024 report describes frontend downloads. ?: complete backend export, current export format, Git sync, custom domains, and operational equivalence are not established. Downloading HTML/CSS/JS does not download the hosted services those files depend on.
Ownership, copyright certainty, asset rights, backend portability, and permission for automated extraction remain distinct. A successful demo does not substitute for critical operational guarantees.
Source basis: CHEATSHEET.md costs, safety and stay-or-migrate sections; PLAN.md billing and sections 1, 3 and 5; PRD.md non-goals and evidence/risk boundaries. See evidence-and-limits for chronology and state-and-trust for enforcement and recovery.