
The maintainer has not written a description at the source.
Repo LadybugDB/explorer, read from GitHub 3 d ago. LadybugDB has not joined Take My Repo.
LadybugDB/explorer is a public repo on GitHub by LadybugDB. It declares the MIT license on GitHub. It is written mainly in TypeScript, has 33 stars and last changed on 2026-08-08. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-19.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
Browser-based user interface for the Ladybug graph database.
Ladybug Explorer is a web application that is launched from a deployed Docker image. Please refer to the Docker documentation for details on how to install and use Docker.
Below we show two different ways to launch Ladybug Explorer. Each of these options make Ladybug Explorer accessible on http://localhost:8000. If the launching is successful, you should see the logs similar to the following in your shell:
Access mode: READ_WRITE
Version of Ladybug: v0.12.2
Deployed server started on port: 8000
To access an existing Ladybug database, you can mount its path to the /database directory as follows:
docker run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
--rm ghcr.io/ladybugdb/explorer:latest
By mounting local database files to Docker via -v {path to the directory containing the database file} and -e LBUG_FILE={database file name}, the changes done in the UI will persist to the local database files after the UI is shutdown. If the directory is mounted but the LBUG_FILE environment variable is not set, Ladybug Explorer will look for a file named database.lbdb in the mounted directory or create a new database file named database.lbdb in the mounted directory if it does not exist.
The --rm flag tells docker that the container should automatically be removed after we close docker.
You can also launch Ladybug Explorer without specifying an existing database. Ladybug Explorer comes with
bundled datasets that you can use to explore the basic functionalities of Ladybug.
This is simply done by removing the -v flag in the example above. If no database path is specified
with -v, the server will be started with an empty database.
docker run -p 8000:8000 --rm ghcr.io/ladybugdb/explorer:latest
Click on the Datasets tab on the top right corner and then: (i) you can select one of the bundled dataset
of your choice from the drow-down menu; (ii) load it into Ladybug by clicking the "Load Dataset" button; and (iii)
finally use Ladybug Explorer to explore it.
By default, Ladybug Explorer is launched in read-write mode, which means that you can modify the database. If you want to launch Ladybug Explorer in read-only mode, you can do so by setting the MODE environment variable to READ_ONLY as follows.
docker run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
-e MODE=READ_ONLY \
--rm ghcr.io/ladybugdb/explorer:latest
In read-only mode, you can still issue read queries and visualize the results, but you cannot run write queries or modify the schema.
By default, Ladybug Explorer is launched with a maximum buffer pool size of 80% of the available memory. If you want to launch Ladybug Explorer with a different buffer pool size, you can do so by setting the LBUG_BUFFER_POOL_SIZE environment variable to the desired value in bytes as follows.
For example, to launch Ladybug Explorer with a buffer pool size of 1GB, you can run the following command.
docker run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
-e LBUG_BUFFER_POOL_SIZE=1073741824 \
--rm ghcr.io/ladybugdb/explorer:latest
By default, Ladybug Explorer is launched in disk-based mode. If you want to launch Ladybug Explorer in in-memory mode, you can do so by setting the LBUG_IN_MEMORY environment variable to true as follows.
docker run -p 8000:8000 \
-e LBUG_IN_MEMORY=true \
--rm ghcr.io/ladybugdb/explorer:latest
In in-memory mode, the database is stored in memory and all changes are lost when the server is shut down even if a database directory is mounted. Also, read-only access mode is not supported in in-memory mode.
In WebAssembly mode, Ladybug Explorer is launched with @ladybugdb/wasm-core, which runs all the queries directly in browser. If you want to launch Ladybug Explorer in WebAssembly mode, you can do so by setting the LBUG_WASM environment variable to true as follows.
docker run -p 8000:8000 \
-e LBUG_WASM=true \
--rm ghcr.io/ladybugdb/explorer:latest
In WebAssembly mode, the database is stored in the current browser session and all changes are lost when the browser tab is closed or when the tab is refreshed. All other configuration parameters are ignored in WebAssembly mode.
If you want to launch Ladybug Explorer with the latest development build of Ladybug, you can do so by using the dev tag instead of latest.
docker run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
--rm ghcr.io/ladybugdb/explorer:dev
The dev tag is updated daily, approximately two hours after the latest dev build of Ladybug is released.
When a new version of Ladybug Explorer is released after the initial launch, re-launching the container WILL NOT automatically update the local image to the latest version. To update the local image to the latest version, you can run the following command.
docker pull ghcr.io/ladybugdb/explorer:latest
After pulling the latest image, you can re-launch the container with the same command as before.
If you are using Podman instead of Docker, you can launch Ladybug Explorer by replacing docker with podman in the commands above. However, note that by default Podman maps the default user account to the root user in the container. This may cause permission issues when mounting local database files to the container. To avoid this, you can use the --userns=keep-id flag to keep the user ID of the current user inside the container, or enable :U option for each volume to change the owner and group of the source volume to the current user.
For example:
podman run -p 8000:8000 \
-v {path to the directory containing the database file}:/database:U \
-e LBUG_FILE={database file name} \
--rm ghcr.io/ladybugdb/explorer:latest
or,
podman run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
--userns=keep-id \
--rm ghcr.io/ladybugdb/explorer:latest
Please refer to the official Podman docs for mounting external volumes and user namespace mode for more information.
The DB menu in the sidebar lets you switch the active database without restarting the server. Three modes are supported:
SSH mode uses sshfs to mount the remote directory on the machine running Ladybug Explorer and opens the database from the mount point directly. Changes are written through to the remote machine in real time.
Requirements on the machine running Ladybug Explorer:
Linux
| Dependency | Required when | How to install |
|---|---|---|
sshfs |
Always for SSH mode | sudo apt install sshfs or sudo dnf install fuse-sshfs |
/dev/fuse |
Always for SSH mode | Kernel FUSE module — present by default on most distributions |
sshpass |
Password auth only | sudo apt install sshpass or sudo dnf install sshpass |
macOS
macOS does not include FUSE support by default. Install macFUSE first, then allow its kernel extension in System Settings → Privacy & Security (a reboot may be required). On Apple Silicon, disabling SIP may additionally be needed — see the macFUSE FAQ.
brew install --cask macfuse
brew install gromgit/fuse/sshfs-mac # sshfs
brew install hudochenkov/sshpass/sshpass # only needed for password auth
Private key authentication does not require sshpass on any platform.
Requirements on the remote machine:
Only an SSH daemon (sshd) is needed. No additional software is required.
When running via Docker, grant the container access to FUSE:
docker run -p 8000:8000 \
--cap-add SYS_ADMIN \
--device /dev/fuse \
--rm lbugdb/explorer:latest
sshfs and (if using password auth) sshpass must also be present inside the container image.
For more information regarding launching and using Ladybug Explorer, please refer to the documentation.
npm i
The @ladybugdb/core dependency installs the native module for your platform
through its npm install script and optional platform packages.
The generated TypeScript parser is checked into src/utils/CypherParser, so
you do not need to regenerate it for normal development. Regenerate it only
when Ladybug's Cypher grammar changes.
To update the grammar:
@ladybugdb/core version in package.json../ladybug. The generator currently
reads ladybug/scripts/antlr4/keywordhandler.py,
ladybug/src/antlr4/Cypher.g4, and ladybug/src/antlr4/keywords.txt.npm run generate-grammar
src/utils/CypherParser.
The temporary ladybug checkout is only an input to generation and should
not be committed.npm run fetch-datasets
env LBUG_DIR={directory containing ladybug database} LBUG_FILE={database file name} npm run serve
npm run eslint
Include -fix for automatic correction of fixable styles.
npm run eslint-fix
npm run build
env LBUG_DIR={directory containing ladybug database} LBUG_FILE={database file name} npm run serve-prod
docker build -t ghcr.io/ladybugdb/explorer:latest .
docker run -p 8000:8000 \
-v {path to the directory containing the database file}:/database \
-e LBUG_FILE={database file name} \
--rm ghcr.io/ladybugdb/explorer:latest
A GitHub actions pipeline has been configured to automatically build and deploy
the Docker image to GitHub Container Registry upon pushing to the master branch. The pipeline will build images
for both amd64 and arm64 platforms.
We welcome contributions to Ladybug Explorer. By contributing to Ladybug Explorer, you agree that your contributions will be licensed under the MIT License.
LadybugDB/explorer is a public repo on GitHub by LadybugDB. Its maker has not written a description.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-08-08. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Go language binding for the Ladybug Graph Database

sigmajs + react-force-graph-2d based visualizer for LadybugDB
Vocabulary and ontology management for RDF datasets: Ladybug-backed schema registry with a Cypher surface, SHACL/ShEx validation
Take My Repo has not tested this on your machine. Requirements come from the project's own documentation.