Switching from Incogniton
This page is for people who have already decided to leave. If you're still deciding, the Morfiade vs Incogniton comparison is more useful.
The main difference: which browser actually launches
Incogniton runs on its own browser build. Morfiade launches the same Google Chrome that's already installed on your computer, and doesn't substitute anything of its own.
Why this matters in practice: a custom build always lags behind the real Chrome — in version, in security patches, and in how it looks from the outside. The real Chrome is the best cover there is in this sense: you simply are Chrome, not a program imitating it. For the same reason we don't spoof the TLS fingerprint — ours is genuine.
The flip side is honest too: the browser also updates on its own, along with your Chrome, and if you're used to a program controlling the browser's version — that won't be the case here.
What you gain and what you lose
You gain:
- profiles with no count. Incogniton's plan is priced by the number of profiles and seats. With us, you have as many as you create;
- a one-time purchase as an option instead of a subscription;
- access without paying — profiles open even on an unpaid licence;
- the real Chrome, see above.
You lose:
- a permanent free plan — we only have a trial of 7 days and 100 profiles;
- team work with roles;
- proxies built into the service — you'll have to buy your own addresses separately;
- macOS and Linux — Morfiade is Windows 10 and 11 only.
If Incogniton's free plan was enough for you and you only need two or three profiles — honestly, there's no reason to pay us for that. Stay where you are.
How to move
1. Export your profiles and cookies from Incogniton. Both exports, not one: a profile without cookies arrives logged out.
2. Write down your proxies. If you used the service's built-in addresses, keep in mind: those stay with them. Your own addresses go into Morfiade's proxy library once.
3. Set up profiles in Morfiade, repeating the same names and categories — that makes it easier to check nothing was lost.
4. Load the cookies — the profile will open already logged in.
5. Check the proxies before you start working: not just whether it's alive, but which country it actually exits from. A mismatch with the browser's settings is more noticeable than the proxy itself.
⚠️ Passwords inside profiles don't carry over — you'll have to move them with Chrome's built-in export to a file. The reason is explained in the article on App-Bound Encryption.
About automation
If you had scripts on Selenium or Puppeteer — they won't be lost. We have a mode with a debug port: the profile hands out a ws:// address that you pass to Playwright or Puppeteer. Plus the local API and bridge for AI agents, which Incogniton doesn't have.
⚠️ One caveat worth knowing now: a profile with an open debug port can't sign in to a Google account. This is a limitation of the browser itself, not ours — details in the article on CDP. Profiles that need Google are automated a different way.
What doesn't change
No program of this class cancels the platforms' rules. And none of them fixes a bad proxy: a datacentre address collects captchas no matter the fingerprint — we've tested this live, and it's cured by residential proxies, not by settings.