Skip to main content
Analytics access is a normal Postgres connection: host, port, database name, username, and password. That is enough for Power BI, DBeaver, DataGrip, Azure Data Studio, or any other Postgres client.

​
Before you connect

Analytics only fills after CargoWise is pointed at the Analytics outbound target and deliveries start projecting into reporting. See How Analytics works if the Analytics page still shows waiting for data.

​
Create credentials

1

Open Analytics

In your organization, open Analytics from the workspace sidebar.
2

Create a credential

Under Connection, create a credential. Lambda shows the password once — copy it immediately.
3

Store the password

Save it in your team’s secret store or Power BI connection settings. If you lose it, revoke that credential, create a new one, and update every client that used the old password.
You can keep up to two active credentials at a time. Create a second one when you need a separate login for another team or tool. Revoke access when someone leaves or a login is no longer needed. There is no rotate action — replace a credential by revoking it and creating a new one.
The password is shown only once on create. Copy connection details before you close the dialog.

​
Connection facts

Use the host, database, username, and password exactly as Lambda shows them. Prefer the replica-oriented username when Lambda provides one. Do not point reporting tools at other Lambda database endpoints.

​
Connect with a database client

1

New Postgres connection

Create a connection in your client and paste host, port 5432, database, username, and password.
2

Require TLS

Enable SSL / TLS. Connections without encryption are rejected.
3

Open reporting

Connect, then open schema reporting. Start with shipments for everyday questions.

​
Connect with Power BI

Use the PostgreSQL connector with the same host, database, username, and password. Require encryption, then load schema reporting. Full model guidance — storage modes, relationships, and publish ownership — is in Power BI.

​
What stays live

As long as the credential exists and has not been revoked:
  • the connection keeps working
  • new long-term data keeps landing in reporting
  • you do not reconnect just because the dataset updated
When you revoke a credential, remove or replace that login in Power BI and every other client.

​
Common mistakes

  • Looking for an Analytics API instead of Postgres — day-to-day reporting uses the database login
  • Expecting stamping ingress traffic to fill Analytics — Analytics needs its own CargoWise outbound target
  • Querying without choosing schema reporting
  • Sharing one password across many unmanaged tools — prefer one credential per team or integration, and revoke what you no longer need
  • Opening unbounded queries against cargowise_xml_observations — always filter by date (and usually by field path or label)