WhoDB
Integrations/Relational

PostgreSQL, connected in place.

Your orders database runs on PostgreSQL and holds the order system: customers, orders, deliveries and invoices for three legal entities. WhoDB connects to it where it runs, labels what is inside in plain business terms, and lets apps use it alongside every other source.

WHAT IT ISOrders database
QUERY LANGUAGESQL
CONNECTIONRead-only role
WRITESOptional, per table, behind review
MAPS TOSales Order, Customer, Product
ORDERS DATABASE · POSTGRESQL
RELATIONAL · POSTGRESQLWhere PostgreSQL already lives.

Your orders database runs on PostgreSQL. It holds the order system: customers, orders, deliveries and invoices for three legal entities, and none of it has to move.

sales_ordercustomerproduct
SCROLL
How it maps

From tables to business entities.

TABLEENTITYUSED BY
sales_orderSales OrderClidey Sales
customerCustomerClidey WMS
productProductClidey Finance
sales_order_lineInvoiceClidey Sales
deliverySales OrderClidey WMS
invoiceCustomerClidey Finance
Query it in SQL
erp-prod41 MS
select o.order_no, c.name, o.total_gross
from sales_order o
join customer c on c.id = o.customer_id
where o.state = 'locked'
  and o.promise_dt < current_date;

Queries run on PostgreSQL with the permissions you granted. Results come back as rows in WhoDB and can be saved as a dataset, joined with other sources, or used by a function.

Set up PostgreSQL in four steps.

01Create a read-only role for WhoDB
02Allow WhoDB through your network
03Add the source and test the connection
04Pick schemas and map tables to entities
→Private link or VPC peering→SSH tunnel through a bastion→IP allow-list for WhoDB Cloud egress
More Relational