Loading...

Welcome to the Graphlytic Cloud Configuration Tool

Here you can choose the infrastructure for your Graphlytic cloud service.
Scale your plan as you need, pay-as-you-go.

Graphlytic Cloud service consists of two HW components: the graph database where the graph data itself is stored and the web application Graphlytic that is used by users to interact with the graph. Some customers already have their graph database (Neo4j, Cosmos DB, Apache Tinkerpop, ...) and want just the visualization application, some customers don't want to worry about the technical part and just want to start working with the visualization. We support both cases, just choose between the two below.

Graphlytic + Graph DB
Choose this option if you don't have your own graph database or don't know what we are asking
Graphlytic
Choose when you want the Graphlytic service to visualize data from your existing graph DB
Number of Users
{{ cUsers }} 1 /200
Estimated Graph Size
S
M
L
XL
Suitable for graph with up to 100 thousand nodes and 100 thousand relationships
Suitable for graph with up to {{ sizes[size]['nodes_rels'] }}
Application HW: 2GB RAM, 1x vCPU, 50GB storage
Application HW: {{ this.parseHw(matrix[type][cCriticality][size].application_service.hw) }}
Database HW: {{ this.parseHw(matrix[type][cCriticality][size].graph_service.hw) }}
This is just an estimated value that will help us choose the right HW setup for you. If you don't know yet or you are just starting with your graph journey then just select the smallest option. It is possible to upgrade the HW later.
Service Criticality
Low
High
  • Graph service and application service hosted on the same machine
  • Weekly backups
Ideal for evaluation, personal usage, development, and smaller solutions where the data is stored also elsewhere.
We are using DigitalOcean's services to host the Graphlytic service and graph database.
  • Graph service and application service hosted on dedicated machines
  • Daily backups
Suitable for production solutions.
We are using GrapheneDB cloud service for hosting the Neo4j graph databases and DigitalOcean's services to host our Graphlytic application instances.