Overview

Product video
Low-code, FAIR Data Platform * Knowledge Graph Management * Rapid Application Development * End-user Oriented Interaction * Use with Amazon Neptune or any SPARQL 1.1 graph database * License for development, sandbox and staging use *
metaphactory is a low-code, FAIR Data Knowledge Graph platform designed to ease onboarding into the world of Enterprise Knowledge Graphs. metaphactory runs on top of Amazon Neptune or any SPARQL 1.1 graph database and offers capabilities and features to support the entire lifecycle of dealing with Knowledge Graphs. With metaphactory, authoring, curating, editing, exploring, integrating, searching, and visualizing your Knowledge Graph become easy, fast and intuitive.
metaphactory's generic approach based on open standards offers great flexibility in different usage scenarios and across various industries, such as Engineering & Manufacturing, Pharma & Life Sciences, Finance & Insurance, Business, and Cultural Heritage & Humanities. Visit metaphactory.com/solutions/products/metaphactory to learn more about metaphactory.
This AMI-only deployment option offers maximum flexibility. It is set up for users who already have a graph database running, such as Amazon Neptune or any other SPARQL 1.1 compliant database. The license is suitable for cases where you want to utilize the full metaphactory feature set but where metaphactory is not exposed as a service to end users or applications. Common scenarios include development, staging, sandbox or training systems.
Highlights
- Knowledge Graph Management - metaphactory makes working with RDF data, SPARQL queries, and ontologies easy and straightforward: UI for data loading, ontology library, SPARQL query UI and query catalog, data quality dashboard and more.
- Rapid Application Development - metaphactory provides Web components for search, exploration, authoring & editing, visualization and interacting with graph data; the components can be set up and combined in minutes for rapid application development.
- End-user oriented interaction with Knowledge Graphs - metaphactory leverages the advantages of the Knowledge Graph for end users by providing intuitive interfaces for drug discovery, supply chain optimization, library management, and many more.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
m5.large Recommended | $15.50 |
m5.2xlarge | $15.50 |
t3.large | $15.50 |
m5.12xlarge | $15.50 |
t2.large | $15.50 |
m5.24xlarge | $15.50 |
m5.xlarge | $15.50 |
t3.2xlarge | $15.50 |
t3.medium | $15.50 |
t2.2xlarge | $15.50 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
For the hourly licensed AMI, metaphacts does not offer refunds, you may cancel at any time.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
You can access the application via a browser at http(s)://Public_DNS_(IPv4)_of_EC2_instance which should prompt you for login. To log in, use the user "admin" and ID of the EC2-instance as password, e.g. "i-12345...". To connect to the operating system, use SSH, the username "ec2-user" and the key you provided during setup. A detailed guide to configure your instance can be found here: https://help.metaphacts.com/resource/Help:AWSDeploymentGuide
Resources
Support
Vendor support
Support is included with metaphactory. Contact us at support@metaphacts.com to submit your request. We also offer a full range of professional services to build domain-specific Knowledge Graph applications, incl. consulting for ontology modeling, data transformation & integration, data quality assurance, data & ontology visualization, rapid application development, and end-user oriented UI design, as well as RDF & SPARQL trainings and workshops. Contact us at info@metaphacts.com to learn more.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

FedRAMP
GDPR
HIPAA
ISO/IEC 27001
PCI DSS
SOC 2 Type 2
Standard contract
Customer reviews
Ontology design has streamlined product recommendations but still needs native data integration
What is our primary use case?
The main use case for metaphactory in my daily work was the design and creation of ontologies and taxonomies.
A concrete example of a project where I used metaphactory to design an ontology was the product data integration project for product recommendation.
Initially, metaphactory was adopted for designing ontologies and taxonomies, but we extended it to implement applications built around the data integrated thanks to the ontologies. This allowed us to define and implement inference rules in order to create more data and more knowledge, and therefore reach fully automated recommendations.
How has it helped my organization?
The positive impact that metaphactory has had on the organization has been access management. metaphactory also manages access in terms of privileges at different levels. Domain experts could manage ontologies, knowledge engineers could carry out data integration, and developers could build APIs to manage data access. Other knowledge engineers could do reasoning. You can have several different profiles in metaphactory, with different tasks but all managed at different levels of responsibility and fully integrated in metaphactory. This made it possible to make everyone accountable for their role and duties, which was very practical.
It was still the same project, integrating product data in order to optimize product recommendations during purchases. Domain experts from the manufacturing department had to extract knowledge from their brains, and the knowledge engineer had to take the ontology and integrate the data coming from the product manufacturing department, leading to a knowledge graph that would then be visualized by the stakeholders.
What is most valuable?
The best features that metaphactory offers are, first, the interface to create ontologies and taxonomies, which is very intuitive. Second, it allows you to connect to triple stores such as GraphDB, Stardog, or RDFox to manage large volumes of data and to visualize them. Finally, the last feature, which may be a bit more complex but is also good for experts, is the ability to implement applications around this data directly in RDF format.
What I like most about metaphactory’s ontology and taxonomy creation interface is the direct integration between several taxonomies in the same domain. It allows you to automatically reuse ontologies or taxonomies that have been created in the same domain, using IRIs.
I would say that metaphactory is very easy to get started with. Even non-experts, mainly what we call domain experts, who are experts in the business domain but not experts in knowledge engineering, can model ontologies with metaphactory, or at least very easily.
What needs improvement?
metaphactory could be improved in terms of data integration. For now, you can design ontologies and taxonomies, but you cannot directly implement, natively, the integration of data associated with the different taxonomies, which makes the integration of mapping engines like R2RML very useful.
It would be interesting if metaphactory could also integrate engines for creating inference rules, because the goal of knowledge graphs is to create inference rules, and managing inference rules as well would be interesting.
Regarding metaphactory’s artificial intelligence capabilities, I would say that governance and data security is something that for me is not integrated. Overall, when I look at metaphactory, I don’t think of security; I think of integration, and while there is access management, security is something else.
At the beginning, the AI features were really just tests, and the results, in terms of reliability and accuracy, were not really there yet, remaining quite tentative. Since then, I haven’t had the chance to test the AI side further.
I do not have any other improvements to suggest.
For how long have I used the solution?
I have been using metaphactory for 4 years.
What do I think about the stability of the solution?
metaphactory is very stable in my environment.
What do I think about the scalability of the solution?
Scalability is good. We haven’t experienced particular problems regarding load increase, as very few people used metaphactory at the same time, with about twenty people connecting per day.
How are customer service and support?
I rate metaphactory’s customer support as good.
I would give metaphactory’s customer support a score of 8 on a scale of 1 to 10.
Which solution did I use previously and why did I switch?
When I arrived at the company, metaphactory was already in use. Before metaphactory, they had tried using PoolParty, which was complicated and didn’t fulfill the mission. Now they are considering Ontop because it allows them to perform mapping directly without needing to understand the underlying technology.
How was the initial setup?
metaphactory is deployed on-premises in the company’s private cloud, making it accessible to all members of the company internally.
What about the implementation team?
We purchased metaphactory directly from the metaphactory company, where we obtained a license, and we ourselves carried out the deployment on Azure servers and set up access based on the different authorization levels within the company.
What was our ROI?
From my point of view, there was clearly a time improvement because it became easier to present the data, visualize it, and access it. Over time, many domain experts became familiar with it and worked with it, transforming metaphactory into a knowledge-sharing platform.
What other advice do I have?
I would rate metaphactory a 7 overall.
I gave it a 7 precisely because, as I said, metaphactory can do better. I took off more points than I added because it is a more or less complete tool, but since we cannot do integration, implement inference rules, and also manage advanced rules, I took off roughly one point for each shortcoming.
I advise other professionals to take the time to experiment, starting with the design of ontologies and taxonomies, then moving on to data visualization itself, and finally developing truly customized visualization applications using metaphactory’s application development tool.
Allows domain experts who aren't software developers to create domain models
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with the product for two years.
What do I think about the stability of the solution?
I've never had issues with the tool's stability. I would rate it as eight out of ten.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I haven't personally had experience with their technical support, but I haven't heard any complaints either.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
The product is expensive.
What other advice do I have?
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.