ianknowles/galactus-db-explorer repository overview

⁠Galactus DB Explorer

Galactus DB Explorer is a browser-based workbench for Galactus DB. Write Cypher queries, explore connected data, and inspect results as graphs, tables, or JSON.

Explorer connects to a separate database server over Bolt. It does not embed the database engine or open database files.

• Image: ianknowles/galactus-db-explorer:latest
• Platforms: Linux AMD64 (x86-64) and ARM64 (aarch64)
• Web interface: Port 7474
• Database image: ianknowles/galactus-db⁠

Use Linux containers on Docker Desktop for Windows or macOS. The latest tag tracks the published preview; pin image digests for repeatable deployments.

⁠What you can do

• Write Cypher in the query editor, with local query history and saved snippets.
• Switch between Graph, Table, and JSON result views.
• Explore graphs with 2D/3D layouts, pan, zoom, property inspection, and neighbour expansion.
• Edit node properties and inspect the database schema.
• Save connections in your browser and switch between database instances.
• Choose label colours, caption properties, and a light or dark theme.
• Download and restore native .gdb backups when the database licence permits it.

Available database operations depend on the server version, user permissions, and edition.

⁠Quick start with Docker Compose

Save the following as compose.yaml to run Explorer and a database together:

services:
  db:
    image: ianknowles/galactus-db:latest
    cpus: 2
    environment:
      GDB_BIND: "0.0.0.0:7687"
      GDB_DATA: "/data/gdb"
      GDB_INITIAL_USER: "gdb"
      GDB_INITIAL_PASSWORD: "${GDB_INITIAL_PASSWORD:?Set GDB_INITIAL_PASSWORD in .env}"
      GDB_INITIAL_DATABASE: "galactus"
      GDB_LICENSE_MODE: "developer"
      GDB_DURABILITY: "buffered"
    ports:
      - "127.0.0.1:7687:7687"
    volumes:
      - graph-data:/data
    healthcheck:
      test: ["CMD", "/usr/local/bin/gdb-server", "--healthcheck"]
      interval: 10s
      timeout: 5s
      retries: 5
    restart: unless-stopped

  explorer:
    image: ianknowles/galactus-db-explorer:latest
    environment:
      GDB_EXPLORER_LISTEN: "0.0.0.0:7474"
      GDB_EXPLORER_DEFAULT_ENDPOINT: "bolt://db:7687"
      GDB_EXPLORER_DEFAULT_USER: "gdb"
    ports:
      - "127.0.0.1:7474:7474"
    depends_on:
      db:
        condition: service_healthy
    restart: unless-stopped

volumes:
  graph-data:

Create a .env file beside it. Choose your own database password of at least 12 characters, and keep the file private and out of source control:

GDB_INITIAL_PASSWORD=replace-with-your-own-long-password

Start the services:

docker compose up -d
docker compose ps

Open http://127.0.0.1:7474⁠ and connect with:

Run a first query in the editor:

RETURN 'Hello from Galactus DB Explorer' AS message;

Explorer connects from its container to the database. The db hostname works inside the Compose network; applications on your host use bolt://127.0.0.1:7687 instead.

⁠Connect to an existing database

To run only Explorer, replace YOUR_DATABASE_HOST below with a database hostname or IP address reachable from the Explorer container:

docker run -d --name galactus-db-explorer -p 127.0.0.1:7474:7474 -e GDB_EXPLORER_DEFAULT_ENDPOINT=bolt://YOUR_DATABASE_HOST:7687 -e GDB_EXPLORER_DEFAULT_USER=gdb ianknowles/galactus-db-explorer:latest

For a database in another container, attach Explorer to the same Docker network with --network NETWORK_NAME and use the database's network name as the host. localhost inside Explorer's container refers to Explorer's container itself.

Open http://127.0.0.1:7474⁠ and enter the database credentials. You can change the endpoint and username in the login form.

⁠Configuration

The endpoint and username settings only prefill the login form. They do not create accounts or change the database password.

Keep the listener bound to 0.0.0.0 inside the container and control access through the published host address and port. The examples bind the web interface to loopback. For remote access, use private networking and an HTTPS reverse proxy; Explorer and the database do not provide native TLS.

⁠Saved connections and data

Explorer needs no database volume. The Compose volume belongs to the database service; Explorer accesses that service over Bolt.

Saved connections, query history, snippets, and visual preferences are local to your browser. Active database credentials are held in the Explorer process's in-memory session and discarded on logout, connection switch, restart, or expiry.

Save password on this device is off by default. Enabling it stores the password unencrypted in that browser's local storage. Use this option only on a trusted device and browser profile.

⁠Queries, results, and backups

The editor can run semicolon-delimited statements sequentially. Each statement is a separate auto-commit operation. Execution stops at the first error; previous successful statements remain committed. Result views show the final statement's result.

Query responses are capped at 1,000 rows. Neighbour expansion loads up to 50 one-hop neighbours at a time, with a 200-relationship expansion ceiling.

Native .gdb backup and restore require Commercial entitlement on the database. A restore replaces the selected database after confirmation. Explorer's upload limit is 512 MiB; the database's incoming-message limit also applies and can impose a lower limit.

⁠Licensing

Galactus DB Explorer is proprietary software, subject to the applicable licence grant and terms. Explorer requires no separate licence key and uses your database credentials to connect.

A fresh database starts in free Developer mode. Database edition restrictions are enforced by the server, and Explorer displays any licence errors it returns. Run CALL gdb.license(); to inspect the server's edition and licence status.

⁠Operations and troubleshooting

View Explorer logs:

docker compose logs -f explorer

If a connection fails, check that the database is running, its endpoint is reachable from the Explorer container, and the database credentials are correct. Use the database service name for connections within a shared Docker network.

To update a Compose installation, set the desired image tags or digests and run:

docker compose pull
docker compose up -d

Updating Explorer restarts its in-memory sessions, so users must sign in again. If updating the database as well, first verify backups and storage compatibility. docker compose down retains the database volume; adding -v deletes it.

The Explorer image runs as UID/GID 10001:10001, with its web assets embedded in the executable. It contains no shell or package manager.