From Oneira to Growit O1: the name migration

Is Oneira the same product as Growit O1?

Oneira is the earlier name attached to the pocket-companion concept and source assets that now support the Growit O1 presentation. Growit O1 is the current public product name on growit.lol, and https://growit.lol/o1 is the current canonical product URL.

That relationship explains why an older asset, path, screenshot, or social reference can still say Oneira. It does not mean two separately purchasable Growit products exist. It also does not make every old promise, price, specification, or availability statement current. The name history and the claim history have to be handled separately.

For a first mention in reporting, use Growit O1 (formerly presented as Oneira). After that, use Growit O1 or O1. Do not combine the names into an unverified company, model, or legal-manufacturer name.

What changed in the public identity

The current site publishes the product under Growit branding, uses the O1 model name, points search engines to the Growit O1 canonical URL, and provides Growit O1 buyer guides, policies, drop information, support, and media materials. The structured product identity keeps “Oneira” only as an alternate name so search engines and readers can connect older mentions with the current product record.

Current public name

Growit O1

Current model name

O1

Earlier public name

Oneira

Canonical product path

/o1

Public rename date

TBD

Manufacturer of record

TBD

A clean identity record matters because product search depends on consistent names, URLs, descriptions, and entity relationships. It also protects readers from mistaking a legacy campaign or mirror page for the current offer.

The migration does not validate every legacy claim

A rename can preserve product history without inheriting stale commercial details. A price attached to an earlier event, preorder, or legacy-brand page is not the current Growit O1 price unless the current product page and live checkout confirm it. The same rule applies to quantities, shipping dates, returns, warranty language, finishes, accessories, and provider integrations.

Product-stage language also remains important. The current record supports local expressive reactions, a prototype-stage local AI direction, optional connected betas, and an Eye World browser preview. It does not support calling every pictured feature a finished production capability. The specs and status ledgeris the controlling record for those distinctions.

Why legacy Oneira references can still appear

The current experience grew from earlier creative and technical source material. As a result, old filenames, asset directories, captured page fragments, image metadata, or third-party mentions can retain the Oneira name. Renaming every historical byte would erase useful provenance and can break links; leaving it unexplained creates a different kind of confusion. This page is the bridge between those two states.

Treat a legacy reference as historical context, not as an active offer. Check its canonical URL and visible review date. If it points somewhere other than the current O1 product and documentation cluster, return to the current O1 pagebefore quoting a specification or purchase term.

The repository also contains JML Tech Studios attribution in legacy source notices and a separate Oneira presentation. That establishes a history of attribution; it does not, on its own, establish the current manufacturer of record or a second active Growit O1 offer. The founder and product-history page records what the current public sources can and cannot say about those relationships.

How reporters, reviewers, and creators should cite it

Use the current evidence cluster

The identity record answers what to call the product. It does not replace feature, privacy, purchase, or comparison evidence. Use the status ledger for capabilities, the connection guide for setup and data boundaries, the buying guide for purchase mechanics, and the build logfor conflicts and unresolved questions.