Seems like you could do the same with rqlite [1], since SQLite supports JSON.
[1]: https://rqlite.io
[1]: https://rqlite.io
Before we jump into what is encrypted, and what is not, what are the threat vectors we are actually concerned about?
With rqlite all traffic between the nodes can be encrypted, as can be the HTTP API. Yes, the data at rest is not, but there are many ways to protect that[1]. One way would be to use an encrypted file system, perhaps.
Encrypted data-at-rest is a valid request, but what use cases would it address?
I never liked the idea of having any database storing my data in a way which can be seen in plain sight regardless of permissions and so forth. Servers get broken into very often and protecting the data within the files is important to me.
I've created another tool called qenc that may help the at rest problem if someone has a problem with it. qenc.org
With a CursusDB node on signal or automatic backup the system will encrypt and compress block by block. Using ChaCha and DEFLATE just to put that out there, it's pretty cool stuff!