Watch the Quick Start Video and Start Your TigerGraph Cloud Solutions in 5 Minutes!
We welcome your feedback for TigerGraph Cloud at firstname.lastname@example.org
Having Trouble Registering for TigerGraph Cloud? Send email to email@example.com and we can assist you with account setup.
A: TigerGraph Cloud gets you up and running with the fastest and best price-performance graph platform in just minutes. TigerGraph's native parallel graph and deep link analytics give you both speed and scale, even on the most complex tasks. In addition, you can now provision a distributed database, as well as a replica cluster for high availability. The GraphStudio visual design interface enables everyone on your team to be a guru in graph. And our starter kits for popular use cases mean you can have a graph application working in minutes. Since it requires far fewer machines to achieve high performance, TigerGraph’s price performance sets a new bar for the graph database industry.
A: Yes, in both instances.
Free Credits: A $25 credit will be automatically granted to each new registered account. The free credit is valid for 30 days after initial use.
Free Tier Instance: When you select an instance type, you will see that one instance type is designated as the Free Tier. For each registered account, you may provision one solution from the Free Tier. Please note, however, that Free Tier instances do not include backup and do not include support.
If no user activity is detected for more than one hour, TigerGraph may automatically stop a Free Tier instance. Users can manually restart the free tier instances from their cloud portal. After 7 days of inactivity, TigerGraph may terminate the inactive free tier instances. For additional information, see TigerGraph Cloud Terms.
Tip: If you need to save your work from a Free Tier instance, export the solution (which saves your graph and queries) and write queries which print all your data to files.
A: Known Capacity Issues: Free Tier instances are provisioned on a common instance type in a data center region of the cloud provider (AWS). During the surge cloud usage period, such as the current global lockdown due to COVID-19, cloud providers across the globe are experiencing capacity issues.
It is possible that when you provision a free tier instance, it will not provision successfully on the first try because of the peak usage in a certain region in the backend cloud platform (AWS). Please be patient and try to provision in another region, or at a later time when there is enough capacity in the region. For any stopped free tier instances, when you restart the solution, it is possible that your solution cannot restart with a machine because of the capacity issue from the cloud provider. In this case, try to restart the solution at a later time when there are more machines available in the region of the cloud provider (AWS). In both scenarios, you can look at the log in "My Activities" and the capacity issue is logged. Submit a support ticket if the capacity issue persists.
To reserve an instance for guaranteed capacity, please submit a support ticket and contact firstname.lastname@example.org to arrange a long term contract for reserved TigerGraph instances.
A: US-West-1 (N.Cal), US-East-1 (N. Virginia), EU-West-1(Ireland), EU-West-2(UK), EU-Central-1(Germany) and AP-Northeast-1(Japan). More regions will be added soon.
A: Yes. In the latest version of TigerGraph Cloud, you can provision a distributed TigerGraph cluster. You may select a partitioning factor up to 10. If you need more than more than 10 instances, please contact TigerGraph at email@example.com
Q: Does TigerGraph Cloud support HA?
A: Yes. In the latest version of TigerGraph Cloud, you can provision a highly available TigerGraph cluster by entering 2 for the replication factor during the provisioning process. Future versions of TigerGraph Distributed Cloud will support higher replication factors. The configuration is active-active, meaning that all copies of the data are available to answer queries.
NOTE: HA systems must have a minimum of 3 instances, This means that the smallest supported cluster configuration for a replicated system is two-way partitioning X two-way replication = four instances.
Q: What services are included?
A: TigerGraph Cloud includes automatic scheduled backup, built-in encryption and other security features, patching, replication and distributed database option. In addition, you can now provision a distributed database as well as a replica cluster for high availability. As a cloud service, many of the administrative and operational tasks - for monitoring, restoring, upgrading, for example - are just a click away. In addition to operations and management for your TigerGraph databases, TigerGraph Cloud also offers Starter Kits to provide instant experience to various graph analytics use cases. The list of Starter Kits can be found here: https://www.tigergraph.com/starterkits/
A: Yes. For basic accounts with credit card billing, there is a limit of 160 vCPUs and 20 instances. A solution is one logical database, which may include several instances due to a distribution database configuration and replication. For accounts running exclusively on Free Credit and that have not yet entered a valid credit card, there is a limit of 16 vCPUs and two solutions. For each registered account (with or without a valid credit card), you may only provision one solution from the Free Tier. To allow more vCPUs and solutions, please contact TigerGraph at firstname.lastname@example.org.
Total number of instances in a cluster = replication factor x partitioning factor
Q: Can I run built-in queries directly after my Solution has been provisioned?
A: Data must be loaded and queries must be installed first. Please perform the following steps after the solution is provisioned:
Connect to GraphStudio through “Open Solution Via Domain” from the cloud portal.
On the Load Data tab, click the Load button to load the sample dataset.
On the Write Query tab, click the Install button to install the sample queries.
Now you can run queries on the starter kit's sample data. Please visit tigergraph.com/starterkits to watch the overview video for each starter kit.
A: TigerGraph Cloud is instance-based and offers an administrator portal to monitor the performance and health of each machine instance.
A: TigerGraph Cloud will provide teams with the flexibility to use the cloud vendor of their choice, so there will be no vendor lock-in. Currently, TigerGraph Cloud offers instances on the AWS platform. More cloud platforms are coming soon. If you require immediate assistance to manage TigerGraph on another cloud provider, please contact email@example.com.
A: Yes, TigerGraph supports TigerGraph cloud users. See the Support Policy terms at https://www.tigergraph.com/support-policy/
A: The TigerGraph GraphStudio™ UI (User Interface) provides an intuitive, browser-based interface that helps users get started quickly with graph-based application development tasks: designing a graph schema, creating a schema mapping, loading data, exploring the graph, and writing GSQL queries.
A: TigerGraph uses GSQL, the query language designed for fast and scalable graph operations and analytics. GSQL’s similarity to SQL, high-level syntax, Turing completeness, and built-in parallelism brings faster performance, faster development and the ability to describe any algorithm.
You can start learning GSQL from our tutorial at docs.tigergraph.com/intro/gsql-101. We also support a RESTful API and JSON output for easy integration with application languages like Python, Java, and C++.
Start learning GSQL and become a TigerGraph Certified Associate today: www.tigergraph.com/certification/
A: TigerGraph's MultiGraph feature, available now in the on-premises TigerGraph Enterprise product, will be coming to TigerGraph Cloud soon.
A: We support AWS S3 import and local file upload. Spark loading is available through our open source JDBC Driver. See https://github.com/tigergraph/ecosys/tree/master/etl
A: As long as there is remaining credit in your account, the data of your solutions will be preserved by the provisioned disk after you stop the solutions even if you don’t have a credit card in your account. The data will be available and accessible after you restart the solutions. The free credit is valid for 30 days after initial use. Your solutions will be deleted automatically if the following scenario is detected: there is no remaining valid credit and there is no valid credit card in your account.
To use “backup and restore” functionality, you need to enter a valid credit card in your account and choose non free tier instances. The non free tier solutions provisioned after the credit card is entered have backup and restore functionality through TigerGraph’s Admin Portal. Note that any solutions provisioned before entering the credit card will not be upgraded with the backup and restore functionality.
If you choose to terminate the instance, your solutions and data will not be preserved. Please see the "Provisioning, Backup and Restore" section for a detailed explanation of the difference between stopping and terminating a solution.
A: Please check your SPAM folder. The activation email could be sent to your SPAM folder. If you can't find it in SPAM folder, and does not receive verification email in your mailbox after resending the verification email, please contact firstname.lastname@example.org so that we can assist you with manual email verification process.
Q: How do I develop a customized application on top of TigerGraph Cloud?
A: Please see Graph Gurus episode 24, where we presented "How to Build Innovative Applications with a Native Graph Database"
Q: I signed up for a TigerGraph Cloud account early, before distributed and HA services were available. Can I still use my earlier solutions? Can I upgrade my solutions to distributed or HA?
A: Our charter TigerGraph Cloud users can access their earlier solutions at our original URL: tgcloud.us. The latest release TigerGraph Distributed Cloud can be accessed at tgcloud.io. We will also be posting additional FAQs in that portal especially for our chapter members.
See www.tigergragraph.com/cloud for pricing information.
A: Yes, there is a discount for contracting with TigerGraph for a one-year term. Please contact email@example.com to request your discount.
Q: What will I have to pay if I delete my instance before the end of the month?
A: If you are subscribed to our standard hourly service, you will be charged only for your hours of use, as described above.
A: We bill you and charge your credit card at the end of each calendar month.
Q: How do I contact you if I have a billing problem that I can’t solve online?
A: You can either open a support ticket from the cloud portal by clicking “Support” on the menu at the left of the page, or you can send an email to firstname.lastname@example.org.
A: If this happens you can contact email@example.com and we will provide you with other payment options.
A: You can find our terms and conditions here: www.tigergraph.com/terms.
A: With TigerGraph Cloud, you only pay for what you use.
TigerGraph Distributed Cloud offers seven different instances, ranging from seven vCPUs with 15 GiB RAM, to 96 vCPUs with 768 GiB RAM. Larger graphs require more RAM. Higher performance calls for both more CPUs and more RAM.
Our pricing table gives initial recommendations for which instance to start with, if you know how much data you will be loading into the graph. We call the input data your "raw data". TigerGraph reorganizes your data into a graph, encoding and compressing it. We have assumed that your stored graph will be about 70% of the size of your raw data. This is a conservative estimate; it's often smaller.
You also need RAM for your graph querying and computation. Workloads vary considerable. In the pricing table, we recommend that your total RAM be about 1.5 times the maximum amount of raw data you think you will load.
If you see you need more space or more compute power, then just scale up.
Contact firstname.lastname@example.org for more help.
Please contact email@example.com.
A: Contact TigerGraph Cloud Support for migrating between different instance types. Instance migration is not yet supported through one-click operation; however, migration can be achieved by using backup and restore for some cases.
A: Distributed database support is not yet available on TigerGraph Cloud, but it is available through our Managed Services or a deployment of TigerGraph Enterprise on your own cloud account.
A: A Root Disk (EBS based) is attached to TigerGraph Instances.
A: If you choose AWS as the backend, TigerGraph Cloud provisions persistent EBS volume as the disk attached to the EC2 machines to hold installation files and data files. The disk holds the following: OS installation, TigerGraph database installation, TigerGraph Graph storage, other data files uploaded to the instance, and any output files generated by querying the database, in addition to system logs generated during the process. Hence, when you consider the size of the disk, please consider the size of the data for all the above installations and files.
A: TigerGraph Cloud has been designed and tested for Chrome. Other browsers may not yet be fully supported.
A: A TigerGraph Solution is a graph database image which can be deployed on a virtual machine instance. Most solutions also come with a starter kit, a sample graph schema, sample data, and sample queries for a common use case, such as Recommendation Engine, Anti-Fraud, and Healthcare Analytics. In a newly provisioned solution, the data files are ready to be loaded, and the queries are ready to be installed.
A: When you provision or restart a solution, there will be a warm-up period for the machine instances and the disk attached to the instances. The larger the data size and the greater the number of instances, the longer the warm-up period will be.
A: When you stop a solution, you shut down the virtual machine instance. The TigerGraph database is frozen in its current state. Billing for that machine instance also stops. Scheduled backups also stop, but the backup copies are kept in EFS. You will still incur charges for disk storage and backups when a solution is stopped. You can start the solution again. After a warm up period, the solution will return to its previous state.
When you terminate a solution, you will deprovision the virtual machine and the attached disk space. The solution is deleted according to the cloud platforms policies and cannot be recovered. A backup file, however, can be used to restore to a new solution within 15 days.
A: Yes. In GraphStudio, go to Admin Portal > Backup and Restore.
TigerGraph Cloud offers full backups on a scheduled or on-demand basis. By default, backup is turned on when instances are running and will be done daily. There are four options you can choose from: backup daily, weekly, monthly, and ad hoc. In current version, the retention policy is to retain up to seven backups. Therefore, if you choose to backup daily; the retention of backup is for a week; if you choose to backup weekly, the retention of backup is for seven weeks; if you choose to backup monthly, the retention of backup is for seven months. if you want to perform an ad hoc manual backup when there are already seven copies of backups, you need to delete an older version of backup in order to save the most recent ad hoc copy. The maximum number of manual backups is six, as the platform always reserves one spot for scheduled backup. When a solution is stopped, backup in EFS will be charged for the time you have the solutions. Please see pricing for backup cost while your instance is stopped.
For a longer retention policy, more options will be coming soon.
Q: Can I restore from a backup from another solution in my account?
A: Only single server solutions can be restored from the backup of another solution in the same account. Distributed and replicated cluster cannot be restored from the backup of another cluster in the same account.
A: To perform an ad hoc backup, use the password of the tigergraph user of your solution. To restore from a previous backup, use the same password that was used to create the backup. This rule applies to restoring from a different solution in your account. All the backups of different solutions in your account can be found through the Admin Portal.
A: We will keep the latest backup for 15 days and then delete. Within that 15 days, you may use your backup to restore into another similar solution if it is a single server solution. To restore a cluster within 15 days, please submit a support ticket through the cloud portal.
A: After you perform a backup, you should wait at least 15 minutes.
A: Please submit a support ticket through the cloud portal.
A: TigerGraph Distributed Cloud offers active-active replication, for increased availability and automatic failover.
A TigerGraph system with HA is a cluster of server machines which uses replication to provide continuous service when one or more servers are not available or when some service components fail. TigerGraph HA service provides loading balancing when all components are operational, as well as automatic failover in the event of a service disruption.
A: Replication factor means how many copies of data are stored, each on a separate machine. The default HA configuration has a replication factor of two, meaning that a fully-functioning system maintains two copies of the data, stored on separate machines. TigerGraph Distributed Cloud currently supports your choice of replication factor of one (only one copy of the data, not recommended for critical systems) or two. Higher replication factors will be supported in the future.
Limitation: In TigerGraph Distributed Cloud, if replication is used, the total number of instances must be at least 3. If replication factor is 2, then the partition factor must be at least 2, for a total of 2x2 = 4 instances.
A: Partition factor means the number of parts or components your graph data is split into, which also equals the number of instances that collectively store one copy of the full graph. For example, if you select a partition factor of 3, each instance will hold approximately 1/3 of your data. Please read https://docs.tigergraph.com/admin/admin-guide/installation-and-configuration/ha-cluster#examples for additional details about partitions and replications.
A: It currently takes about 4 minutes to provision a single instance. If you configure a 2x2 replicated and distributed graph database, it will take about 15 minutes.
A: By default, you will be given your own VPC(s) for your TigerGraph Cloud account. Your instances are separated from other accounts by different VPCs. Within your own account, you have different VPCs for different regions.
A: Yes, TigerGraph Cloud encrypts all data in transit and at rest.
A: You are not sharing storage with other customers. Each TigerGraph solution is provisioned as one or more virtual machine instances of the TigerGraph engine, used only for your account, and provisioned with its own disk space. No two accounts are sharing the same TigerGraph database.
A: The current version of TigerGraph Cloud does not support VPC peering. The feature is coming soon. If you want VPC peering, contact firstname.lastname@example.org for managed services.
Q: How do I change the password to my solution?
A: This is mandatory for your security. The default username/password is tigergraph/tigergraph. Please change the password to protect your system. The ability to change a solution's password is provided through the Admin Portal. Go to GraphStudio > Admin Portal > User Management.
A: When you register your account, you will select a username and password. You can then log in anytime at www.tgcloud.io. You will also be given a URL, using a subdomain name that you select.
A: You can access the database through TigerGraph's GraphStudio visual interface and through RESTful endpoints. Use RESTful endpoints to POST to TigerGraph solutions and develop applications. Please refer to the RESTful API User Guide. To find the RESTful endpoints for queries created in GraphStudio, please read “Show Query Endpoint”. There is also a recorded webinar which demos the process in details: https://info.tigergraph.com/graph-gurus-24
Here are step-by-step instructions:
TigerGraph Cloud enables REST++ Authentication to securely connect TigerGraph Cloud solutions with your application through port 9000.
Step 1: [One time] Navigate to the TigerGraph solution's Admin Portal, and generate a secret from User Management.
For example, the URL for the solution is:
and the generated secret is abcd1234 from Admin Portal.
Step 2: [Need to renew every lifetime] Use the secret generated in step 1 to get a RESTPP token (for example, xyz789) using curl command. Note that the port is 9000.
Here is an example where you obtain a token with a lifetime of 1,000,000 seconds (11 days):
Step 3: Now in your application, use the token in the REST call, for example:
curl -X GET -H "Authorization: Bearer xyz789" 'https://SOLUTIONID.i.tgcloud.io:9000/graph/MyGraph/vertices/Account?limit=3'
TigerGraph's role-based access control with MultiGraph will be available in a future update.
A: When you terminate an instance in TigerGraph Distributed Cloud, the virtual machine instance and its associated storage volume are deleted according to the policies of the underlying cloud infrastructure vendor.
A: TigerGraph Cloud encrypts data at rest and in transit, and SSL is enabled for secure access.
A: The ability to integrate TigerGraph Cloud into an SSO system will be provided at a future date.
A: Access to TigerGraph system and component logs is coming soon via the TigerGraph Cloud portal and administrator portal for provisioned TigerGraph instances.
A: In your cloud portal, on the top bar, you can submit the support ticket by clicking on . This will generate a support ticket in TigerGraph's freshdesk support system. You can track the ticket status in freshdesk.
A: If in rare cases, you cannot submit TigerGraph Cloud support tickets through the cloud portal for your account, you can also submit the support request by email to email@example.com directly. This action will automatically generates a new freshdesk support ticket and you can track the support ticket in freshdesk portal. Please remember to use the email account associated with your TigerGraph Cloud account to submit the support email to firstname.lastname@example.org so that TigerGraph Cloud Support can verify your account.
A: TigerGraph is a native parallel graph database built on C++. It is not built on a NoSQL database or relational database.
A: The GraphStudio visual design tool provides several monitors. The Load Data page includes a real time monitor and statistics. Query performance and many other measures are available on the administrator portal.
A: Due to TigerGraph's massively parallel and hybrid in-memory database design, an instance with more vCPUs and more memory will usually run faster. For a given hardware configuration, performance can be improved by optimizing graph schema, loading jobs, and queries. In TigerGraph Distributed Cloud, you can also choose to provision a cluster with replication factor 2 to increase throughput. Contact email@example.com to discuss for query optimization services.
A: A list of third-party software used in the TigerGraph engine and TigerGraph Cloud is available at https://docs.tigergraph.com/legal/patents-and-third-party-software.