TigerGraph
Connect your TigerGraph graph databases to Memex for AI-powered graph analytics.
What is TigerGraph?
TigerGraph is a native parallel graph database platform designed for advanced analytics and machine learning. It excels at handling complex, interconnected data and can traverse billions of relationships in real-time. TigerGraph is used for fraud detection, recommendation engines, supply chain analysis, and more. Once connected, Memex can explore your graphs, run queries, and help you analyze your connected data through natural conversation.
What You'll Need
Host
TigerGraph Cloud or server URL
https://myinstance.i.tgcloud.io/
Username
TigerGraph username
tigergraph
Password
TigerGraph password
Your secure password
Graph Name
Name of the graph to connect to
MyGraph
Finding Your Credentials
For TigerGraph Cloud
Log in to TigerGraph Cloud
Navigate to your cluster/instance
Find your connection details in the cluster overview:
Host: Your instance URL (e.g.,
https://myinstance.i.tgcloud.io/)Username: The username you created during setup (default is often
tigergraph)Graph Name: The name of the graph you want to query
Step 1: Access TigerGraph Cloud Console
Log in to TigerGraph Cloud and select your instance.
Step 2: Get Instance URL
Copy your instance URL from the dashboard. It typically looks like: https://your-instance-name.i.tgcloud.io/
Step 3: Get Graph Name
Open GraphStudio from your instance
In the top-left dropdown, you'll see your available graphs
Note the name of the graph you want to connect
Step 4: Verify User Credentials
Use the username and password you set up when creating your TigerGraph Cloud instance. If you need to create a new user, use GraphStudio's Admin Portal.
For Self-Hosted TigerGraph
Contact your database administrator to obtain:
The TigerGraph server URL
A username and password with appropriate permissions
The name of the graph you need to access
Connecting to Memex
Open the Memex Hub from the sidebar
Click on the Connectors tab
Find and click the TigerGraph card
Enter your Host URL, Username, Password, and Graph Name
Give your connection a memorable name (e.g., "Fraud Detection Graph")
Click Add Connection
Verifying Your Connection
Once connected, try asking Memex:
You should see a list of vertex types in your graph.
Using Your Connection
Here are some examples of what you can ask:
Security Considerations
Authentication
TigerGraph uses username/password authentication:
Use strong, unique passwords
Create dedicated users for Memex with appropriate permissions
Avoid using the default
tigergraphsuperuser for applications
User Permissions
TigerGraph supports role-based access control. Best practices:
Create a dedicated user for Memex
Grant read-only permissions on the graphs needed
Use the Admin Portal in GraphStudio to manage users and roles
Network Security
For TigerGraph Cloud:
Connections are encrypted with HTTPS
Configure IP allowlisting if available
Use private endpoints for sensitive workloads
For self-hosted TigerGraph:
Enable HTTPS for encrypted connections
Configure firewall rules to restrict access
Use SSL/TLS certificates
Never share your TigerGraph credentials. For production use, create dedicated service accounts with minimal required permissions.
Troubleshooting
Connection Failed
Verify the Host URL is correct and includes
https://Ensure the TigerGraph instance is running
Check if your IP address is allowed to connect
Verify the instance URL is accessible from your network
Authentication Failed
Double-check your username and password
Ensure the user exists and is active
Verify the password hasn't expired
Check if the user has permission to access the specified graph
Graph Not Found
Verify the graph name is spelled correctly (case-sensitive)
Ensure the graph exists on the instance
Check that the user has permission to access the graph
In GraphStudio, verify the graph is visible in the graph dropdown
Query Errors
Ensure the graph has data (vertices and edges)
Verify the schema is properly defined
Check if installed queries are required for certain operations
Review TigerGraph logs for detailed error messages
Timeout Issues
Large graph traversals may take time—be patient or add limits
Check the instance resource utilization
Consider optimizing your graph schema or adding indexes
Learn More
Last updated
Was this helpful?