Hey Michael
Happened to chance upon your message while searching for something related to Flur.ee. Wanted to say that I have had the chance to evaluate it very recently for a project. I'd like to keep my recommendation brief without boring you with details you might not need: Flur.ee may be the best fit yet for linked data application development, or what I call LDApps, [1] due to native support for JSON(-LD), i.e. no more object-triple marshalling/mapping.
However, Flur.ee currently markets itself as a JSON-LD database, not as a triplestore (TS). Therefore, certain features that you might expect from a TS, like a file loader, SPARQL endpoint or an admin panel, [2] are not available at this time (but you can send RDF data and SPARQL queries through their API, aside from their own FlureeQL). It has a unique backend-less authorization mechanism, so theoretically, you don't need an "RDF back-end". Its blockchain-based storage also provides a neat record-keeping feature -- history "time travel".
TL;DR: If all you need is a CRUD app backed by a knowledge graph, Flur.ee provides the least development resistance for application developers, but may not be the best graph database or triplestore for data professionals (yet).
[1] "el-dapps"; one can also call them KGApps but that's a mouthful unless you say "kay-gapps"
[2] there is no GUI management from v3 onwards as they focus on their cloud/hosted offering