Skip to main content

​
Getting Started

Julius connects directly to your MySQL database, allowing you to analyze your data using natural language; no SQL knowledge required.

Create New Data Connector

Navigate to the Data Connectors page and click “Create new Data Connector”, then select MySQL.

Choose Your Connection Mode

Select how you’ll connect to your database:
  • Direct: Connect directly to your MySQL database
  • SSH: Connect through an SSH tunnel for enhanced security

​
Connection Setup

​
Required Fields

All fields marked with an asterisk (*) are required.
​
Connection Name
string
required
A friendly name to identify this connection in Julius.Example: “Production DB” or “Sales Database”
​
Host
string
required
The server address where your MySQL database is hosted.Format: IP address (192.168.1.100) or domain (db.mycompany.com)Cloud databases: Provided by AWS RDS, Google Cloud SQL, etc.
​
Port
number
required
The network port for MySQL connections.Default: 3306Note: Only change if using a custom port
​
Database
string
required
The specific database name to analyze.Example: sales_data, customers, analytics
​
User
string
required
Your MySQL database username with read permissions.
Create a dedicated read-only user for Julius
​
Password
string
required
Password for your MySQL user account.Security: Encrypted in transit and at rest

​
Network Configuration

Whitelist Julius IP Address

If your database has firewall restrictions, you’ll need to allow connections from Julius.

IP Whitelisting Guide

Step-by-step instructions for AWS RDS, Google Cloud SQL, Azure, and other platforms

Get Julius IP Address

Find your current Julius IP in Data Connectors settings

Test Your Connection

  1. Click “Add Connection” to test your configuration
  2. Julius validates your credentials and network access
  3. If successful, your connector is ready to use!
  • ✓ Host and port are correct
  • ✓ Julius IP is whitelisted in your firewall
  • ✓ Database allows external connections
  • ✓ Username and password are accurate
  • ✓ User has permissions for the specified database

​
Start Analyzing Your Data

Once connected, simply ask Julius about your data in plain English:

Query Data

“Show me all customers from the users table”

Calculate Metrics

“What’s the average order value this month?”

Create Visualizations

“Create a chart of sales by region”

Analyze Trends

“How has revenue changed over the past 6 months?”
No SQL required! Julius automatically writes and executes queries based on your natural language requests.

​
Security & Compliance

SOC 2 Type 2

Certified to meet strict security standards

End-to-End Encryption

All credentials and data encrypted in transit and at rest

Zero Data Storage

Julius only queries what you request—never stores your data

Security & Trust Center

Learn more about how Julius protects your data and maintains compliance

​
Best Practices

Create a dedicated MySQL user with SELECT-only permissions to prevent accidental data modification.
    CREATE USER 'julius_readonly'@'%' IDENTIFIED BY 'secure_password';
    GRANT SELECT ON your_database.* TO 'julius_readonly'@'%';
Verify your connection works correctly using a development or staging database before connecting to production.
Work with your database administrator to ensure proper security policies and performance guidelines are followed.
Keep an eye on database load when running complex queries through Julius, especially on production systems.

​
Troubleshooting

The most common cause of connection timeouts is that Julius’s IP address has not been allowlisted in your database’s firewall.If you see an error like Read timed out or Connection timed out while trying to reach the service, follow these steps:
  1. Go to your Data Connectors settings and copy the current Julius IP address
  2. Add that IP to your database’s firewall allowlist (see our IP Whitelisting guide for step-by-step instructions)
  3. Retry the connection
Other possible causes:
  • Incorrect host or port
  • Database doesn’t allow external connections
  • Database is offline or unreachable
Possible causes:
  • Wrong username or password
  • User lacks database permissions
  • Database name misspelled
Solution: Double-check credentials and verify user permissions
Possible causes:
  • User lacks read permissions on tables
  • Connected to wrong database
  • Tables don’t exist in specified schema
Solution: Verify user has SELECT permissions and correct database is specified

​
Need Help?

Contact Support

Questions? Reach out to [email protected] for assistance