It's more of a database-building toolkit than a storage engine. What you get is a distributed KV store with a strict serializable consistency model (see
https://jepsen.io/consistency) and very interesting versionstamp functionality.
What you do not get is a "query language" or indexing.
Yes, there are companies that use FoundationDB as their primary data store. It makes a lot of sense to integrate it directly with the application rather than go through additional layers and a "query language". I am working on adapting my app to use it, and so far very happy with the results.