Connect Nile to Excel, Sheets and AI

One database, every tenant, one query

Nile's model is the interesting part of this connector, and it changes what a reporting connection is good for.

• Nile keeps all tenants in one Postgres database and separates them with a tenant_id column on tenant-aware tables, rather than giving each customer a separate database or schema.
• Your application sets a tenant context per connection and therefore sees one customer at a time. A Query Streams connection does not set that context, so it sees across all of them.
• That makes cross-tenant reporting a plain GROUP BY rather than an integration project. Usage per customer, revenue by plan, or which accounts have not logged in this month are all one statement.
• It also means access control is yours to design. A connection here is not scoped to a tenant, so if you need per-customer reporting, filter on tenant_id in the saved query and share that query rather than the connection.
• Everything the agent runs is read-only, so nothing here can modify tenant data regardless of what the query says.

-- Cross-tenant reporting is an ordinary GROUP BY
SELECT   t.name AS tenant,
         COUNT(o.id)   AS orders,
         SUM(o.amount) AS revenue
FROM     public.tenants AS t
JOIN     public.orders  AS o ON o.tenant_id = t.id
WHERE    o.placed_at >= now() - interval '30 days'
GROUP BY t.name
ORDER BY revenue DESC;

Credentials are shown once, and regional endpoints are ordinary Postgres

Two practical notes that cover most of what happens when setting this up.

• Nile generates a credential id as the username and shows its password a single time. If you lose it, generate another rather than trying to recover the old one.
• Endpoints are regional and end in .db.thenile.dev, on the standard port 5432. There is no pooler in this path and the agent applies no pooler adaptations.
• TLS is required and the agent enforces it for Nile hostnames, so clearing the SSL checkbox does not produce an unencrypted connection. The certificate chain is not verified — read it as protection against anyone reading the traffic, not proof of which server answered.
• The pasted connection string is dropped once the fields are filled, so the password is stored in one place rather than two.