metaphactory for any graph database (AMI, non-production license)

We use the solution to monitor vulnerabilities. I use metaphactory to create semantic data as part of our data architecture. We're building data products, lifting data to be used internally for better products. It's mainly used for managing metadata of existing data, including data models, lineage, ownership, and data contracts.

metaphactory is a central tool for implementing these data products. We're considering it for pharmaceutical modeling and connecting to graph databases. It's the only product our company uses with Graph DB.

The most valuable feature is graphical modeling, which allows domain experts who aren't software developers to create domain models. It provides good support. These valuable features enable domain experts to work with the tool and create their own models.

For improvements, I'd like to see more maturity in the product, especially regarding enterprise vendor lock-in. The whole area isn't mature enough yet. I think it will develop over time. More competitors are coming up now. I'd like to see better integration with specific vendors who specialize in managing data products. We need more standards beyond the W3C standards from the semantic web that have been around for twenty-five years.

I have been working with the product for two years. 

I've never had issues with the tool's stability. I would rate it as eight out of ten.

I rate metaphactory's scalability as eight out of ten. It's pretty scalable and can handle large amounts of data. We don't have a month of data but three months' worth. For our use case, it's sufficient, but there are other cases where they might need to process much more data. We currently have four customers using metaphactory, and they are enterprise businesses.

I haven't personally had experience with their technical support, but I haven't heard any complaints either.

Regarding the initial setup, I'd rate it a seven out of ten, where one is difficult and ten is easy. It's pretty easy to set up. I'm not directly responsible for the setup, but I think there might be some complexities with identity and access management, federated access integrations, and external use cases. However, I'm not a 100 percent sure about these issues.

The product is expensive. 

My advice for others considering metaphactory is to use it if they want an easy-to-use tool. While there might be other tools that are more feature-complete for advanced scenarios, metaphactory is a really good choice for standard scenarios. They have good support, graphical visualizations, and many capabilities. You don't need a trained specialist to use it, making it useful for domain experts.

I rate the overall solution a seven out of ten.