Everything, in its place.
Name your profiles, add tags and notes, and find exactly the workspace you need. Duplicate settings to get a new profile ready faster.
Bring order to your browser profiles. Keep workspaces separate, launch them in a click, and keep your data on your own machine.
From focused daily work to repeatable browser testing, every profile has a home of its own.
Name your profiles, add tags and notes, and find exactly the workspace you need. Duplicate settings to get a new profile ready faster.
The manager runs on your machine. Profile settings and browser data stay in your configured data directory. No account is needed.
Loopback access by defaultSet a startup page, locale, window size, and credential-free HTTP or SOCKS5 proxy for each profile. Choose a windowed or headless launch.
Your installed browser, your settingsBuild with Maven, manage profiles over a JSON API, and connect your automation tools to a running profile’s local Chrome DevTools endpoint.
Read the API guide# Your workspace, from the terminal
curl http://127.0.0.1:8080/api/profiles
# A standard Java application
mvn verify
java -jar target/NabilBrowserManager-1.0.0.jarBring a Java 17+ JDK, Maven, and a local Chrome or Chromium installation. Everything else is in the source package.
Read the setup guideExtract the source package and run mvn verify in the Maven project.
Run the JAR, then open http://127.0.0.1:8080/app/.
Add a name and your settings. Your browser opens with its own persistent data directory.
NabilBrowserManager is a Java application that organizes and launches your installed Chrome or Chromium. It does not include or modify a browser engine, and it does not promise fingerprint spoofing or detection avoidance.
Profile metadata and each browser’s data directory live in the manager’s local data folder. You can choose another location with NABIL_DATA_DIR. The website demo stores only example profile settings in this browser.
You can create, edit, search, tag, duplicate, import, and export demo profile settings. Launching browsers and using CDP require the Java manager running locally. Demo mode is always clearly labeled.
Yes. The website is plain HTML, CSS, and JavaScript, ready for a static host. Connecting the domain requires your hosting and DNS configuration. Browser management runs through the Java application; static hosting alone cannot launch browsers on your machine.
No. Export and import move profile settings only. Cookies, history, passwords, and other browser data are not included. Duplicating a profile also copies settings only.
The project takes product inspiration from the public CloakBrowser Manager repository. This is an independent Java implementation with a different browser integration. It does not bundle the separately licensed CloakBrowser binary.