From the Galactus DB team
A place for ideas, practical guides and a look behind the scenes. Here’s what we’ve been building, testing and learning along the way.
RBAC: the right keys for the right people ↗
Your reporting dashboard needs to read the graph. Your application needs to update it. Neither needs to spend its afternoon creating administrators.
20/09/2026 · GuideParks, ponds and paths: giving your graph a sense of place ↗
A pin on a map tells you where something is. It is less helpful when the question is "Can we deliver there?", "Does this route cross the park?" or "Why have we put the meeting point in a pond?"
17/09/2026 · publishedA graph database that packs light ↗
Your application has enough to carry without its database arriving with a removal van. Galactus DB ships as a small, self-contained image, with Explorer in a separate package when you want a visual workbench.
17/09/2026 · publishedSaved, but how saved? Choosing a durability mode ↗
You press save. The database says "done". Can you put the kettle on, or is there still something waiting to reach disk?
17/09/2026 · publishedGalactus DB and Neo4j: a tale of two graph databases ↗
A graph database has a varied working day: find a person, follow a few connections, load a batch of records, then do it all again while everyone else is asking questions too. How do Galactus DB and Neo4j compare at those jobs? Here are the scores, with a little context to help you read them.