> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.hodi.host/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Is direct access to PostgreSQL provided?

|| Yes, at your request, in one click from Hodiploy. The database is NOT open to the internet by default: you decide whether a remote access is useful, when, and from which addresses.

**You can query your database, perform audits, connect external reporting tools, or carry out advanced technical operations** with your own tools, without going through us. Maintain full control and complete operational freedom over your Odoo environment!

## How you open it

1. Log in to Hodiploy from your Client Area
2. On the instance's row, open the **"Actions"** menu, then **"Remote database access"**
3. Enter the **allowed IP addresses** that may reach the port, one per line (for example `192.0.2.10` or `203.0.113.0/24`)
4. Click **"Open the access"**

The screen then hands you the host, the port, the user, the password and the connection URL, to paste as-is into pgAdmin, DBeaver, Metabase, a spreadsheet or any PostgreSQL client.

## What happens on the server

**The port is only reachable FROM the addresses you listed.** A firewall rule is placed on your server when you open the access; the rest of the internet gets a refusal, including our own machines. You decide who gets in.

**One access per instance**, with a fixed user: `hodiploy`. The port is allocated automatically in the 5433–5533 range, so you can have several instances open on the same server without collisions.

**The password is randomly generated**, 32 characters. It's encrypted at rest and shown in clear only in your screen, so you can copy it into your tool.

## Close without losing

The **"Close"** button shuts the port and removes the firewall rule. **The port and password are kept**: if you reopen the access later, exactly the same ones come back, and your pgAdmin favourites keep working.

A **locked** instance ("Actions" menu, "Lock") refuses any change to its remote access, in either direction. That is what the lock is for on a sensitive production instance.

## Two things to know

**The `hodiploy` user is a database owner**, which is what makes audits, extracts and maintenance operations possible. That's also what makes you responsible for what you do with it: a clumsy query can damage production data. Take [a backup](https://help.hodi.host/en/article/how-do-backups-work-on-my-odoo-instance-17pbt7b/) before a risky operation.

**This is not an end-to-end encrypted tunnel.** It's PostgreSQL over TCP, as-is. For internal reporting from a known workstation, the allowed-address list is the right safeguard. For SQL from a roaming machine without a fixed IP, you're better off using a [terminal inside the Odoo container](https://help.hodi.host/en/article/how-do-i-open-a-terminal-on-my-odoo-instance-sevrbf/) and running `psql` locally on the machine.

## A question?

If you're unsure which addresses to allow, or your PostgreSQL client won't connect, [contact us](https://hodi.host/contact/) and our team will look at it with you.