# Product status & release evidence

This page describes the product as documented on **November 2, 2026**, following the November 1 release. Availability can depend on your account, subscription, configured connection and service conditions. The interface shows the access available to you.

## Available in the released product

| Capability | What is available |
| --- | --- |
| Browser creation | Project conversation, explicit build requests/approvals, previews, checking and independent review |
| Continued development | Same-game follow-ups, editable waiting messages, unfinished-build recovery and project memory |
| Project records | Local journals, retained references, private restart exports and validated restore |
| Art and audio | Supported imports, free texture discovery, credits, WAV preparation and optional connected image generation |
| Development tools | Source editing for eligible Studio plans and separate hosted terminal workflows |
| Distribution | Playable/source downloads, deliberate public game publication and supported remix flows |
| Studio history | Saved-history usage summaries showing recorded coverage and available provider-reported costs |

The [creation guide](/docs/how-creation-works), [asset guide](/docs/assets-and-audio) and [publishing guide](/docs/publishing-and-export) explain how to use these capabilities and their boundaries.

## Access and setup still matter

Personal API requests need a valid connection and provider access. Native subscription routes require their own client setup and supported plan. Included AI is limited to the eligibility and allowance shown for an account; it is not a universal unlimited benefit.

Multiplayer source kits require backend configuration and validation. Self-publishing kits require your own store accounts, native build, signing and submission steps. Assisted publishing is in the access-request stage; an interest request is not an invitation or a store submission.

## Prototypes and development work

| Area | Current boundary |
| --- | --- |
| DEXPIT RWA pack-launch example | Live oracle reads; payments, asset acquisition, issuance and randomness are simulated |
| Signed desktop installers | Public trusted Windows/macOS release and complete installation acceptance remain pending |
| PixelLab and Meshy | Separate local workflows; no automatic hosted fallback |
| Larger asset storage | Preparatory storage work does not remove normal project/import limits |
| Broader store publishing | Requires invitations, operating readiness, individual agreements and store approval |

The playable DEXPIT game and its RWA launch prototype are different experiences. Follow their descriptions rather than treating prototype mechanics as deployed financial contracts.

## What release verification establishes

The November 1 rollout records passing automated application, backend and focused browser checks, followed by 29 live checks. The release includes the current artwork, follow-up queue and project-continuation work. Public changes are summarized in [Updates](/updates).

The checks cover specific source versions and observed flows. Many provider tests use simulated responses; passing those tests does not prove every live provider, new-customer payment, device or generated game. It also does not establish customer adoption, an external audit, or an uptime guarantee.

For a reproducible issue, include the page, device/browser, expected behavior and the visible support reference in your [support request](/help). Exclude keys, payment details and private source unless a suitable private transfer has been arranged.