Connections page

The Connections page is where you connect STYD to your databases. Each connection belongs to the currently selected workspace and can be used by chat threads in that workspace.

Connections are now primarily managed from Settings → Connections. The standalone /connections route may still exist for compatibility and deep links.

What the Connections page is for

Connections define how STYD accesses your data. A connection stores the database type, host, port, database name, and credentials required to read from your database.

STYD currently supports PostgreSQL and MySQL connections.

Create a connection

Open Settings → Connections
Click to add a new connection
Select PostgreSQL or MySQL
Enter your database credentials
Test the connection
Save the connection

Test before saving

The test action checks whether STYD can reach your database using the credentials provided.

Validates host and port access
Checks database credentials
Confirms database type
Helps catch configuration mistakes early
If the test fails, review the server address, port, database name, username and password. The address must be a public one (localhost and private network addresses are refused, and there is no SSH tunnel option), and a firewall that restricts access must allow STYD’s addresses, which the form and the Common connection errors page list.

After saving a connection

After you save a database, STYD offers to analyse it with the AI Guide. Your first analysis is included while your workspace has an AI Guide setup left (see Pricing) and starts by itself; otherwise STYD shows its price in prompts and an owner or admin confirms it. You can chat with the connection before the analysis is done, but answers improve once it is.

When the analysis runs:

Tables are discovered
Columns are analyzed
Sample values are reviewed when available
AI-drafted descriptions are created

You can create a chat thread attached to the connection and start asking questions straight away; you do not have to wait for the analysis.

Edit or archive connections

Existing connections can be updated when database credentials, host details, or configuration values change.

Edit
Update connection details and save the new configuration.
Archive
Hide a connection and erase its password, API key or Bridge token. Past answers, sample values, descriptions, linked Odoo users and checkup results stay until the workspace is deleted. Archived connections are listed, collapsed, under Archived.
Reconnect
Bring an archived connection back: its saved settings are filled in, you enter the password, API key or token again, and it returns with its history.
Testing, syncing and archiving a connection never need a plan or free prompts. Owners and admins can always do it. A connection is never deleted from the interface: archive it when it should no longer be used, reconnect it to use it again.

Best practices

Use read-only credentials
Create a database user that can read data but cannot insert, update, or delete.
Use clear connection names
Name connections by company, environment, or database purpose.
Check the selected workspace
Connections are created inside the active workspace.
Run the AI Guide analysis again after schema changes
If new columns are added later, run the AI Guide analysis again so STYD can understand them. Running the analysis again costs prompts, about 1 for every 500 columns (at least 1), and the price is shown before you confirm.