We're using it in production, both their cloud-hosted offering and for our on-prem software products. Massive scale isn't really a requirement for us but the multi-model capabilities are a winner for our use cases - being able to mix graph and relational-style queries in the same query language.
A problem for us is the Enterprise licensing is implemented such that our on-prem customers would have to manually update a license string once a year, which is a PITA and why we have previously been using Community edition despite paying for Enterprise (mostly for the support contract).
As a maintainer of the C#/.NET driver, I'd say our project isn't so much dead as it is complete. We use it in our products and if it requires updates due to breaking changes, we will maintain it, but otherwise it does what we need it to.
Also worth noting that ArangoDB did have one of their own developers work on the project and made many contributions.
Thanks, we're not dealing with very large data sizes: maybe up to 100K documents, maybe using large binary attachments up to 100s MB per attachment. We use another DB product (ArangoDB) as our main application DB, so would be using something like CouchDB only for the offline-first and peer-to-peer replication capability - then referencing items in CouchDB from our main application DB, where we're more than happy about query language and other features. I had a somewhat wild idea that someone (maybe us...) could implement the couch DB replication protocol for ArangoDB using the ArangoDB FOXX framework. Not sure how feasible that might turn out to be though, wonder if anyone else thought of it...
A problem for us is the Enterprise licensing is implemented such that our on-prem customers would have to manually update a license string once a year, which is a PITA and why we have previously been using Community edition despite paying for Enterprise (mostly for the support contract).