Roles and permissions
Users and custom roles grant access database by database, with system administration kept separate. The last administrator can never be removed by mistake.
Users and rolesGalactus DB runs production graphs for teams that answer to security reviews, uptime targets and finance. Access control, encryption, durable storage, replicas and monitoring are built into the server, and every one of them is documented.
Answers come back in well under a millisecond, over the network, through the same Bolt drivers your application uses. Reads never wait for writers.
Medians of three passes on Galactus DB 1.5.5, measured 9 October 2026: queries sent over Bolt by a Python client to a graph of 100,000 people and 200,000 relationships with an indexed ID, in a container with 8 CPUs and 8 GB of RAM. Full results
Users and custom roles grant access database by database, with system administration kept separate. The last administrator can never be removed by mistake.
Users and rolesTLS is built into the server. Drivers connect with bolt+s:// and browsers with wss://, on the same port, with no proxy to run.
Encrypted connectionsCommit logs and storage pages carry checksums, and recovery after a crash keeps every acknowledged transaction. With group commit, acknowledged writes survive a power cut and concurrent commits share each disk sync.
Durability and recoveryRead-only replicas follow their source transaction by transaction, on the same instance or, with Enterprise, on servers of their own. Delayed replicas keep history in reserve, and any replica takes over with one PROMOTE statement.
Replica databasesNative backup and restore with Commercial and Enterprise. Dumps run while writers carry on, of any size, and restore straight into storage pages.
Backup and restorePrometheus metrics and a health endpoint, statement and transaction time limits, and running queries you can list, profile and stop.
MonitoringChange streams with before-values, and subscriptions with label and property triggers, at-least-once delivery and dead letters, feed audit trails, caches and search indexes in commit order.
Change streamsCommercial runs any number of databases on one instance, each with its own grants, so tenants stay apart on the servers you already have.
DatabasesStorage pages stay on disk and the pages in use stay in memory, inside one memory budget you set. A large graph runs on a modest instance and opens without rebuilding anything.
StorageYes. Every release passes our full test suite on every storage engine, including runs with a 1 MiB page cache, and we kill the server mid-write at random to check that every acknowledged transaction survives. Every page carries a checksum, so a damaged page is caught, never served. Our own licensing, billing and Galactus Cloud control plane keep their records in Galactus DB.
Sub-millisecond for lookups and short traversals: a median of 0.48 ms for an index lookup and 0.54 ms for a two-hop traversal, measured over Bolt. Reads never wait for writers; each one reads the last committed snapshot.
Replicas follow their source within a few milliseconds with group durability. Failover is a PROMOTE statement you run, so you decide when a replica takes over. With Enterprise, replicas run on servers of their own.
No. Licence keys are signed and checked locally by the server, so nothing phones home and an outage elsewhere never stops your database. If a licence lapses, reads and backup exports keep working.
Everything in Commercial, plus replicas on other servers over encrypted Bolt and support from the Galactus team who build the database.
Community is free for any use and needs no account or licence key. One Compose file starts the database and Explorer.