YOUR BROWSER. YOUR WORKSPACE.

A separate space
for every session.

Bring order to your browser profiles. Keep workspaces separate, launch them in a click, and keep your data on your own machine.

Java 17+ & Maven Self-hosted Your Chrome / Chromium
NabilBrowserManagerPRODUCT PREVIEW
YOUR WORKSPACE

Browser profiles

+ New profile
D
Design workspaceen-US · 1440 × 900
WorkLaunch
Q
QA playgrounden-GB · 1366 × 768
TestingLaunch
R
Research desken-US · 1440 × 900
PersonalLaunch
Separate browser data. One organized workspace.
Stored locallyBuilt to stay in your hands.
A little more focus.
A lot less tab chaos.
Independent sessions
Persistent local profiles
Open Java source
MADE FOR YOUR WORKFLOW

Many profiles.
One clear view.

From focused daily work to repeatable browser testing, every profile has a home of its own.

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.

Client workQuality assuranceResearch
W
Work workspaceIts own cookies, history, and local storage
P
Personal workspaceA separate browser data directory

Local is the default.

The manager runs on your machine. Profile settings and browser data stay in your configured data directory. No account is needed.

Loopback access by default

A setup for each session.

Set 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 settings

Friendly to developers.

Build 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.jar
GET UP AND RUNNING

Your next workspace
starts here.

Bring a Java 17+ JDK, Maven, and a local Chrome or Chromium installation. Everything else is in the source package.

Read the setup guide
01

Build the manager

Extract the source package and run mvn verify in the Maven project.

02

Start your local workspace

Run the JAR, then open http://127.0.0.1:8080/app/.

03

Create a profile and launch

Add a name and your settings. Your browser opens with its own persistent data directory.

A FEW GOOD QUESTIONS

Know your workspace.

Is NabilBrowser a new browser engine?

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.

Where is my data stored?

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.

What does the online demo do?

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.

Can I host the website on NabilBrowser.com?

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.

Does export include my signed-in sessions?

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.

How is this related to CloakBrowser Manager?

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.

MAKE ROOM FOR FOCUSED WORK

Your profiles. Your machine.
Your way of working.

Explore the demo