# What is Orbita browser? GoLogin's engine, explained > Orbita is the Chromium-based browser a GoLogin profile opens in. GoLogin says it tracks Chrome releases, and each profile is updated on its own. Source: https://mosaicbrowser.com/blog/orbita-browser ## What Orbita is, from GoLogin's own pages Orbita is the Chromium-based browser a GoLogin profile opens in. GoLogin says it tracks Chrome releases, and each profile is updated on its own. ![Orbita versus Google Chrome, each name in its own tile: Which Chrome does an engine say it is?](https://mosaicbrowser.com/covers/orbita-browser.webp) Orbita is GoLogin's own browser, the one a GoLogin profile runs in. [GoLogin's help article on Orbita](https://support.gologin.com/en/articles/14853789-orbita-browser) puts it simply: when you click Run on a profile, "a browser window opens. That browser is Orbita." It looks like Google Chrome and is, in GoLogin's words, "built on the same open-source foundation as Chrome", which is Chromium. The difference is in what it tells websites about the computer. We make a different anti-detect browser, so this is not an outside reviewer's view. Everything below about Orbita comes from GoLogin's own help pages, with no version numbers in it, because those change. The second half is a check you can run on Orbita, on our engine or on any other, to see which Chrome it claims to be. ## What GoLogin says Orbita changes GoLogin's article lists what Orbita answers with the profile's values instead of the computer's real ones: - the browser version and operating system reported to sites - screen size and resolution - graphics card details - the list of fonts available on the device - how the browser renders graphics and audio - timezone and language - IP exposure through WebRTC It adds "some more things under the hood", and says each profile keeps its own cookies, saved logins, history and session data. GoLogin also has an Android app that, by the same article, uses Orbita as its engine. The article says the changes are invisible to the person browsing. Bookmarks, extensions, shortcuts and developer tools work as they do in Chrome. None of that is unusual for the category. Any [anti-detect browser](https://mosaicbrowser.com/guides/what-is-an-anti-detect-browser) has to answer the same questions. Where products differ is in how and where the values are changed, and whether the answers agree with each other. Mosaic is a desktop app Email yourself the link and open it on your computer. [How it works: Its own Chromium](https://mosaicbrowser.com/features/engine) ## "Orbita tracks Chrome's version releases" That is the line in GoLogin's article that matters most for a reader checking things for themselves. It goes on: "a browser reporting an outdated version looks suspicious to websites", GoLogin updates Orbita regularly, and you can update individual profiles to the latest browser version from the profile menu. Its advice for older profiles is to check, from the three-dot menu, that they run the latest version. Read together, those sentences say that the browser version belongs to each profile as well as to the app. Two GoLogin profiles created a long time apart can run different Orbita versions, and so claim different Chrome majors, until each is updated. That is GoLogin's design described in its own words, and it explains why its help centre asks you to look. ## How to check which Chrome major any engine claims This works on Orbita, on our engine and on stock Chrome. Run it inside the profile you want to know about. 1. Read the major. `navigator.userAgent` carries it as `Chrome/.0.0.0`. The `Sec-CH-UA` request header and `navigator.userAgentData.brands` carry it as a brand list. 2. Read the full build. `navigator.userAgentData.getHighEntropyValues(['fullVersionList'])` returns the four-part version, for example `.0..`. 3. Look the build up in Google's own listings: the [Chromium Dash schedule](https://chromiumdash.appspot.com/schedule) for when each major reached stable, and the [Chrome Releases blog](https://chromereleases.googleblog.com/) for the exact builds Google shipped. 4. Compare. The major should be one real people are still running, and the full build should be one Google actually released for that platform. 5. Check the brand list against the User-Agent. A brand list naming `Chromium` beside a User-Agent claiming plain Chrome disagrees with itself. Steps 2 and 4 are the ones people skip, and both have caught our own engine. ## Three ways a version claim contradicts itself We have got each of these wrong at some point, so these come from our own work rather than anyone else's. **A full version with no build number.** For a while our engine reported `uaFullVersion` as the bare string `"153"`. No Chrome that has ever shipped does that, and a page reads it with one call. The fix was to send the engine's own four-part build, after which FingerprintJS's confidence figure matched the one it gives a stock Chrome on the same machine. **A build that was never released.** The four-part version we then reported, `153.0.8010.37`, was our own build's number, and it was never a stable Chrome Google shipped. We tried claiming the real stable build of that major, `153.0.8010.52`, to see whether IPHey's score moved. It did not. The `.37` was still a claim a released Chrome does not make, and step 3 finds that kind in a minute. Our build script can ask Google's version history for the current stable release on the platform, so the number we build is one Google shipped. **Features that belong to another browser.** An unbranded Chromium carries field trials Google Chrome does not run. Against Chrome 153 on our build Mac that was [twenty API differences](https://mosaicbrowser.com/blog/twenty-apis-chrome-lacks), each of them visible to a page listing properties. A version string can be right while the feature set says something else. ## Where Mosaic stands on this Our engine is Tesseract Chrome: stock Chromium source with our patches applied, tracking a current stable Chrome major. When a profile's claimed major matches the engine's, it reports the engine's own build number, because that is the browser actually answering. The values a profile claims are changed in the engine's C++ rather than by a page script, and [C++, not JavaScript](https://mosaicbrowser.com/blog/cpp-not-javascript) explains why that matters for consistency. Mosaic also imports GoLogin profile exports, mapping names, notes, proxies, start pages, cookies where present and the fingerprint fields GoLogin recorded. Whichever browser you use, the five steps above take a few minutes and tell you what each profile claims. ## Questions ### Is Orbita the same as Google Chrome? No. GoLogin's help centre describes Orbita as built on the same open-source foundation as Chrome, with the look and menus of Chrome, but answering a site's questions about the device with the profile's values instead of the computer's. ### How do I open Orbita? GoLogin's help centre describes Orbita as the browser window that opens when you press Run on a GoLogin profile. The values it reports to sites come from that profile's settings. ### How do I see which Chrome version my browser claims? Read navigator.userAgent and the Sec-CH-UA brands for the major, and call navigator.userAgentData.getHighEntropyValues with fullVersionList for the full build. Then look that build up in Google's own release listings. ### Why does an outdated browser version matter? Google Chrome updates itself by default, so a browser claiming a major that is long out of date stands out. A version also has to agree with the features the browser has, and an old claim beside a newer feature set is a contradiction. ## Related [What is an anti-detect browser?](https://mosaicbrowser.com/guides/what-is-an-anti-detect-browser): An anti-detect browser gives each profile its own fingerprint, proxy and cookies, so sites see separate visitors. What it changes, how, and its limits. [The best anti-detect browsers, compared on the same criteria](https://mosaicbrowser.com/compare/best-anti-detect-browsers): Seven anti-detect browsers on one table: free plan, entry price, what they bill by, teams, mobile and automation, from each vendor's own page in November 2026. [Twenty APIs Chrome doesn't have: Chromium's field trials](https://mosaicbrowser.com/blog/twenty-apis-chrome-lacks): Unbranded Chromium runs its field-trial testing config at every launch. Against Chrome 153 that was 20 API differences, and one switch moved them all. [Why we change fingerprints in C++, not JavaScript](https://mosaicbrowser.com/blog/cpp-not-javascript): A JavaScript spoof is one realm deep. An iframe read the real source of 33 of our patched functions; the same values changed in C++ agree everywhere. [Grandfathered plans and why review prices disagree](https://mosaicbrowser.com/blog/grandfathered-pricing): On an old GoLogin pricing plan, your renewal price comes from your own subscription, not the public page. Reviews often quote plans a new account can't buy. [How far behind Chrome stable is your anti-detect browser?](https://mosaicbrowser.com/blog/anti-detect-chromium-version-lag): Real Chrome updates itself, so an engine a few majors old claims a browser almost nobody runs. Our move from 153 to 154 took a 93-minute rebuild. [Is Camoufox still maintained? Reading the repository](https://mosaicbrowser.com/blog/is-camoufox-maintained): Is Camoufox still maintained? Its repository answers better than forums do: compare the latest release's date and Firefox base with today's Firefox. [Junglefox and Chroma, Kameleo's two engines](https://mosaicbrowser.com/blog/kameleo-junglefox): Junglefox is Kameleo's Firefox-based engine, beside Chroma, its Chromium one. A Firefox profile needs an engine that really is Firefox, and keeping one is work. ## Mosaic, on your own computer The browser this blog is about: its own Chromium, fingerprints from real machines and a proxy exit per profile. Free holds 3 profiles. Pro is $49 a month for any number. Mosaic is a desktop app Email yourself the link and open it on your computer.