Managed · PG + MySQL speaks PostgreSQL / MySQL
Connect Scalewayマネージドデータベース to Excel, Sheets and AI
Scaleway Managed Database — PostgreSQL or MySQL. An IP address and a port, with a Private Networks route the agent suits particularly well.
One connection, every surface
Where your Scaleway data can go
Connect Scaleway once and the same read-only connection feeds all of these — no second setup, no second copy of the data. 9 of 11 have a step-by-step guide.
Scaleway to Excel
Microsoft Excel · Excel add-in
Pull live Scaleway results straight into a worksheet and refresh them on demand — desktop Excel, Excel Online, Microsoft 365.
Read the PostgreSQL guide
Scaleway to Google Sheets
Sheets add-on
Run a saved Scaleway query from the sidebar and drop the rows into the sheet. Shared collaborators can refresh it themselves.
Read the PostgreSQL guide
Scaleway MCP server
Claude, Cursor and MCP clients
Give an AI assistant read-only access to Scaleway with the schema it needs to write correct SQL — no credentials in the chat.
Read the PostgreSQL guide
Scaleway REST API
HTTP endpoint
Publish a Scaleway query as an authenticated JSON endpoint any application can call, with an OpenAPI 3.1 spec and ready-made Postman, Insomnia and Hoppscotch collections. No database port is opened.
Read the PostgreSQL guide
Scaleway to Airtable
Automation platform
Sync Scaleway rows into an Airtable base on a schedule, or fetch them inside an Airtable automation script.
Read the PostgreSQL guide
Scaleway to Baserow
Automation platform
Feed a Baserow table from Scaleway over the REST endpoint — self-hosted or Baserow cloud.
Read the PostgreSQL guide
Scaleway to SeaTable
Automation platform
Keep a SeaTable base current with Scaleway data without exporting a file or exposing the database.
Read the PostgreSQL guide
Scaleway to Smartsheet
Automation platform
Push Scaleway results into a Smartsheet grid so plans and reports read from the source system, not last week's export.
Read the PostgreSQL guide
Scaleway to Anvil
Anvil Works · App platform
Back an Anvil Python app with Scaleway through the REST endpoint instead of embedding database credentials in the app.
Read the PostgreSQL guide
Scaleway to Power BI
Power Query M
Paste the generated Power Query M into the Power BI Advanced Editor and the report reads live Scaleway results over HTTPS — no ODBC driver, no database port opened.
How Power BI works no Scaleway walkthrough written yet
Scaleway alerts and reports
Slack · Discord · Email · Webhook
Put a Scaleway query on a schedule and have the rows delivered to Slack, Discord, email or a signed webhook — or hold the message until a row count, threshold or percentage change crosses the line you set.
How alerts and reports work no Scaleway walkthrough written yet仕組み
5 steps, no inbound firewall change
Decide where the agent runs. For a public endpoint, anywhere that can reach it. For a Private Network, install it on a Scaleway Instance in the same VPC and use the private endpoint.
In the Scaleway console open your Database Instance and go to Overview. The IP address and port are shown there.
Pick the engine at the top of the card, PostgreSQL or MySQL, then enter the IP as the host with the port beside it.
Add the database, username and password. Database rdb is prefilled, which is Scaleway's default name.
Leave Use SSL on for a public endpoint, test, and save. Read it from Microsoft Excel, Google Sheets, Power BI, MCP or REST.
Feature deep-dive
What Scaleway gives you
An IP address, not a hostname
Every other managed provider on this site hands you a hostname. Scaleway hands you an address, and a couple of things follow from that.
- The host field is labelled IP address rather than Host, and expects something like 51.159.24.10 from the instance Overview page. The port sits next to it and is assigned per instance.
- Because there is no hostname, there is no provider suffix to recognise. Choosing this card is what records that the connection is Scaleway, rather than the address giving it away.
- That only affects the badge and the branded defaults. Underneath it is ordinary PostgreSQL or MySQL and the agent carries the driver.
- It is still worth picking this card over the generic one, for the defaults and for the guidance below. OCI PostgreSQL is the only other preset in the same position, and for the same reason — private addresses carry no provider signal.
Private Networks are the interesting route
Scaleway supports reaching a Database Instance over a Private Network, and this is where the agent's shape pays off.
- Install the agent on a Scaleway Instance in the same VPC and point it at the private endpoint. The database needs no public exposure at all.
- The agent only makes outbound connections, so no inbound security rule is needed to make that work. Nothing about the VPC changes.
- That is the same pattern as reaching an on-premises database behind a firewall — the agent sits on the inside and dials out — and it applies unchanged here.
- On a private endpoint the traffic never crosses the public internet, which is also why encryption is handled the way it is below.
Encryption follows the checkbox on both engines
Unusually for this site, neither engine is force-encrypted here, and the private-network option is the reason.
- The Use SSL checkbox is on by default and the connection is encrypted while it stays on. On a public endpoint, leave it on.
- The agent does not override it on either engine. For PostgreSQL that is a deliberate exception — a private-network endpoint is a legitimate way to run, and forcing encryption would break a connection that was working correctly.
- So the honest instruction is the one the card itself gives: keep SSL on for public endpoints. On a private endpoint inside your VPC you have a real choice, and the traffic is not crossing the internet either way.
- When encryption is on, the certificate chain is not verified. Read it as protection against anyone reading the traffic in transit rather than proof of which server answered.
- Everything the agent runs is read-only, one statement at a time, and your credentials stay on the machine you installed it on.
-- Read-only, whichever engine you picked\nSELECT c.name,\n COUNT(o.id) AS orders,\n SUM(o.amount) AS revenue\nFROM customers AS c\nJOIN orders AS o ON o.customer_id = c.id\nWHERE o.placed_at >= now() - interval '30 days'\nGROUP BY c.name\nORDER BY revenue DESC;Shared by every database connector
True of every database connector
- 発信専用 — the agent opens one encrypted connection out to Query Streams. No inbound port to forward, no VPN, no IP allowlist, nothing about your database exposed to the internet.
- Credentials stay put — the database username and password live on the machine you installed the agent on. Query Streams never receives them and cannot reach your database on its own.
- 読み取り専用、強制 — one statement at a time, SELECT and friends only. A write is rejected on your own machine before it is ever sent to the server, rather than relying on a permission somebody remembered to set.
- Deploy as many agents as you like — one per site, region or cloud. Every data source they can see arrives in a single dropdown, so nobody has to know which agent hosts what.
What you get once a query is saved
- Share the capability, not the SQL — a colleague or an outside partner can run your query and change its filters without ever seeing the statement behind it.
- Filters from either direction — declare them yourself as @variables, or let the connector spot the literal values already sitting in your WHERE clause and offer those as dropdowns.
- Read it from anywhere — Microsoft Excel, Google Sheets, Power BI, the REST API, AI assistants over MCP, the Query Builder and Nova all read the same saved query.
- Run several at once — five saved queries into five worksheet tabs, streamed concurrently, however large the results.
- Join it to anything else you have connected — another database, a business API, or a folder of files, in one read-only statement.
Cross-source SQL
Join Scaleway to the rest of your data
One statement can span Scaleway and your other connections at once. Each source runs only the part it can, streams the result back, and the join happens centrally — the sources never talk to each other and nothing is copied anywhere.
3 connections · 3 agents
One statement
-- nothing copied, nothing merged, nothing scheduled
セレクト c.region, COUNT(*) AS orders, SUM(i.amount_due) AS invoiced
フロム scw_db.public.orders1 f
ジョイン erp_sql.dbo.customers2 c ON c.id = f.customer_id
ジョイン 請求する.stripe.invoices3 i ON i.customer = c.stripe_id
GROUP BY c.region
ORDER BY invoiced DESC;The three parts are connection, schema and table — and the connection name is whatever you called it. Illustrative columns; your tables will be your tables. Read-only applies to every piece: SELECT, WITH and EXPLAIN only, with a ceiling on how much any one source may hand over for a single query. フェデレーションクエリの仕組み
Connection details
What Scaleway needs
- Host
- An IP address from the instance Overview page, for example 51.159.24.10. Scaleway exposes no hostname
- ポート
- Assigned per instance and left blank on purpose — copy it from the Overview page
- Engines
- PostgreSQL or MySQL, chosen at the top of the card
- Driver
- Npgsql or MySqlConnector, carried by the agent — nothing to install at the Scaleway end
- Private Networks
- Supported. Put the agent on an Instance in the same VPC and use the private endpoint — no public exposure and no inbound rule
- Defaults
- Database rdb is prefilled. The username is the one you created with the instance
- TLS
- Follows the SSL checkbox on both engines, on by default. Not forced by the agent, so that a private-network endpoint stays possible. The certificate chain is not verified
- Pooling
- None. The agent applies no pooler adaptations for Scaleway
- Identified by
- Choosing the card, not the address — an IP carries no provider signal
- Default schema
- public on PostgreSQL. A MySQL connection is qualified by its database instead
Scaleway is the one card on this site whose own help text already says exactly the right thing about encryption. It tells you to keep SSL on for public endpoints, which is an instruction rather than a guarantee — correct for both engines, and correct whether you are on a public address or inside a VPC. That is a better shape than a promise that only holds for one of the two engines, and this page follows it.
The IP-rather-than-hostname detail is minor in practice but it does change one thing worth knowing: nothing about the address tells the system it is Scaleway, so picking this card is what records the fact. If you ever create the connection as generic PostgreSQL instead, it will still work — you just lose the branded defaults and the badge.
For a cross-source query the qualifier follows the engine rather than the badge. A PostgreSQL connection you called scw_db is written scw_db.public.orders; the same connection on MySQL is qualified by its database instead. Either joins to a folder of CSVs, an on-premises system of record or a billing API in one read-only statement.
Vendor documentation: www.scaleway.com
Same wire protocol
These connect the same way
They share every guide above; only the connection string differs.
FAQ
Questions about Scaleway Managed Databases
Which tools can read Scaleway Managed Databases data through Query Streams?
All of them, from one connection: Excel, Google Sheets, MCP, REST API, Airtable, Baserow, SeaTable, Smartsheet, Anvil, Power BI, scheduled alerts and reports. Connect the database once and every surface reads the same read-only connection — there is no per-tool setup and no second copy of the data.
Do I have to open a firewall port to my Scaleway Managed Databases database?
No. The Query Streams Network Agent runs inside your network and opens a single outbound encrypted connection. Nothing listens for inbound traffic, no VPN is required, and the database keeps its existing firewall rules.
Can Query Streams change data in Scaleway Managed Databases?
No. The agent enforces read-only at the point of execution — one statement at a time, SELECT and friends only. Credentials stay on the agent and are never sent to Query Streams.
What does Query Streams need to connect to Scaleway Managed Databases?
A reachable host, a role and its password — the agent carries the driver, so nothing is installed on the database. Host: An IP address from the instance Overview page, for example 51.159.24.10. Scaleway exposes no hostname. Port: Assigned per instance and left blank on purpose — copy it from the Overview page. Engines: PostgreSQL or MySQL, chosen at the top of the card. Driver: Npgsql or MySqlConnector, carried by the agent — nothing to install at the Scaleway end.
Can I join Scaleway Managed Databases to another database in the same query?
Yes — that is a federated query. One statement can reference Scaleway Managed Databases and your other connections at once, written as connection.schema.table. Each source runs only the part it can and streams the result back; the join happens centrally, so the sources never connect to each other and nothing is copied or scheduled. Read-only applies to every piece — SELECT, WITH and EXPLAIN only — and there is a ceiling on how much any one source may hand over for a single query. Federated queries are a plan feature; the federated queries page carries the current source and size limits.
Is connecting Scaleway Managed Databases different from connecting PostgreSQL?
Only the connection string. Scaleway Managed Databases speaks the PostgreSQL wire protocol, so filters, scheduling, sharing, the Excel and Google Sheets add-ons and the MCP server all behave identically. The Scaleway card pre-fills the host, port and SSL settings that provider expects.
Is there a Scaleway to Excel guide?
Yes — it is the PostgreSQL guide, and it is correct for Scaleway Managed Databases as written. Scaleway speaks the PostgreSQL wire protocol, so Scaleway to Excel, Scaleway to Google Sheets and every other destination follow the same steps. The only Scaleway-specific part is the connection string, and the Scaleway card fills that in for you.
Put Scaleway where the work happens
Install the agent, point it at your database, and pick a destination.
読み取り専用 発信専用 Credentials stay on the agent
English 
Spanish 
German 
French 
Portuguese 
Japanese 
Korean 
Chinese 
Italian 
Dutch 
Indonesian 
Polish