What are we spending on Scaleway this month?
Scaleway connects Memtro to your cloud account. It lists projects, Instances across all ten zones with state, commercial type, image, project and tags, snapshots, and a month's billing consumption by product and resource with totals per currency and category. Costs are untaxed estimates until the invoice is issued. When asked, and once an administrator has granted them by name, it can start, stop, reboot or create Instances, which starts billable compute, back up Instances or snapshot volumes, whose storage is billed, and rename or tag them. Terminating or deleting an Instance or snapshot is permanent and loses local data.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Scaleway tool, reads what it needs, and answers with the source cited.
These tools change something in Scaleway. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Scaleway is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What are we spending on Scaleway this month?
Which Scaleway product cost the most last month?
Which Instances are running, and in which zones?
Stop the staging-worker Instance in fr-par-1 over the weekend.
Snapshot the database volume on db-prod-2 before tonight's upgrade.
Maya Okafor, finance manager at BigCo, asked what Scaleway had cost so far this month. Memtro read the month's consumption and gave the totals per category, with the largest products and their projects. It said the figures are untaxed estimates until the invoice is issued.
Tom Reilly, DevOps engineer at Acme Ltd, asked Memtro to back up the db-prod-2 Instance before a database upgrade. Memtro backed it up to an image of its volumes in Scaleway and reminded him the image's storage is billed until it is deleted.
The teams that lean on Scaleway most, a question each of them asks, and what they connect beside it.
A record in Scaleway is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn the Scaleway console, open IAM → Applications, create an application for Memtro and attach a policy with InstancesReadOnly, BillingReadOnly and ProjectReadOnly, or InstancesFullAccess in place of InstancesReadOnly if Instance actions will be granted.
Under API keys, generate a key for that application and copy the secret key, which is shown once. The access key is not needed.
In Memtro, open Connections → Scaleway and paste Secret key and Organization ID (from Organization settings). Add a Project ID to limit it to one project.
Ask: what are we spending on Scaleway this month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Scaleway tools are the same everywhere.
Only when you ask, and only what it has been granted: start a stopped Instance (billing resumes); stop an Instance, releasing or keeping its hypervisor slot; reboot an Instance; back up an Instance to an image of its volumes (storage is billed); terminate an Instance, deleting its local volumes (permanent); create an Instance of a given type in a zone and project (starts billing); rename an Instance, set its tags or its delete protection; delete an Instance (permanent); snapshot a volume (storage is billed); delete a snapshot (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Secret key and Organization ID, with an optional Project ID. In the Scaleway console, open IAM → Applications, create an application for Memtro and attach a policy with InstancesReadOnly, BillingReadOnly and ProjectReadOnly, or InstancesFullAccess in place of InstancesReadOnly if Instance actions will be granted.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
