Abdohoo.App Developer tools
Devdesk · Desktop database clients
One window each for ScyllaDB and Cassandra, for MongoDB, and for Redis and the servers that speak its protocol. Schema, a real workbench, typed editing, live metrics, backups and an advisor — built with Electron, React and TypeScript, and shipped for Windows, macOS and Linux.
The tools
They share a shell and a set of habits, but not a generic grid. Each one speaks its own database's vocabulary — CQL and ring ownership, mongosh and field shape, SCAN and key types — because a client that pretends every database is a table helps with none of them.
ScyllaDB · Apache Cassandra
A CQL workbench that lints before the server refuses, typed row forms for every CQL type, exact ring ownership computed from vnode tokens, and a keyspace ERD that draws the relationships a wide-column model actually has.
MongoDB 4.4+ · Atlas
Real JavaScript against a db handle with mongosh conventions honoured, documents flattened into typed columns by dotted path, field shape sampled with $sample, and an index advisor that reads $indexStats.
Redis · Valkey · KeyDB · Dragonfly
A SCAN-based key tree that never runs KEYS *, a dedicated editor for every core and module type, a linter that knows which commands hurt, keyspace analysis by namespace, and an advisor that hands you the command that fixes each finding.
Trial and licence
Each client runs fully featured for fourteen days from first launch. After that it keeps reading — browsing, queries, metrics, analysis and export — and only writing needs a licence key.
Someone diagnosing a production incident is never locked out of looking at their own data by a lapsed key. That is a deliberate choice, not an oversight.
A key is an Ed25519-signed statement verified locally against a public key compiled into the binary. Nothing contacts a server, which matters because database tooling is routinely run on machines with no route to the internet. Perpetual keys carry a maintenance window, so a key keeps working forever on the versions it covers and never silently unlocks a release nobody paid for.
Pricing is not set yet — ask and we will tell you the moment it is.
Why they're quiet
Database tooling gets run on jump boxes, in locked-down networks and against data that must not leave the building. Every choice below follows from that.
Connection secrets go to the OS keychain — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux — not to a config file in your home directory. Passwords go straight to the server: never logged, never echoed back, and masked in every statement preview.
There is no analytics call, no crash reporter phoning home and no sign-in. The app behaves the same on an air-gapped jump box as it does on your laptop, and the offline licence check is part of why — it is arithmetic, not a request.
Destructive actions take typed confirmation, and every write shows the exact command before it runs. A connection can be marked read-only, and that switch is enforced in the main process at the same place the licence gate lives — so a caller that respects one cannot slip past the other.
Every client tunnels through an SSH bastion, and does it without breaking what sits on top: ScyllaDesk forwards CQL, the REST API and the metrics port together; MongoDesk sets SNI to the real host so certificate checks still pass through the tunnel.
The shell is the same each time; what changes is the vocabulary it speaks. If there's a database you use daily and nobody has written a decent desktop client for, tell us which one.