Failed deploy explained
Dan Fletcher, backend engineer at Northwind, asked why the latest api deployment failed. Memtro read the deployment with its commit, branch and failure reason. He fixed the build setting it named and pushed again.
Why did the latest Koyeb deployment of the api service fail?
Koyeb connects Memtro to your serverless platform. It reads apps, services with their status and current deployment, and deployments with what they run and why they failed. It also reads running instances by region, domains and their DNS state, volumes, the organisation's activity feed, hours of use and plan quotas. When asked and granted, it can redeploy, pause or resume services and apps, cancel a pending deployment, create or rename apps, add, re-check or remove custom domains, and delete services, apps or volumes. Logs, environment variables and secrets are never read, and usage comes as hours, not prices.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Koyeb tool, reads what it needs, and answers with the source cited.
These tools change something in Koyeb. 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 Koyeb 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.
Why did the latest deployment of the api service fail?
Which services are unhealthy right now?
Which instances are unhealthy, and in which region?
How many hours did each service use last month?
Redeploy the worker service.
Dan Fletcher, backend engineer at Northwind, asked why the latest api deployment failed. Memtro read the deployment with its commit, branch and failure reason. He fixed the build setting it named and pushed again.
Sarah Chen, engineering manager at Acme Ltd, asked Memtro to pause the staging app for the weekend. With the action granted, Memtro paused it and every service in it stopped serving. The pause showed in the organisation's activity feed for the team.
The teams that lean on Koyeb most, a question each of them asks, and what they connect beside it.
A record in Koyeb 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.
In Koyeb, open Organization settings → API and create an API access token. It has no scopes and is deactivated when its creator leaves the organisation.
In Memtro, open Connections → Koyeb and paste the API access token.
An administrator grants the actions by name, such as Redeploy a service, to the teams that may use them. The token reaches everything the organisation can.
Ask "Why did the latest deployment of the api service fail?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Koyeb tools are the same everywhere.
Only when you ask, and only what it has been granted: redeploy a service (builds and ships it again); pause a service; resume a paused service; pause every service in an app; resume a paused app; cancel a pending deployment; create an app; rename an app; add a custom domain to an app; re-check a domain's DNS; remove a domain; delete a service; delete an app and its services; delete a volume. 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.
API access token. In Koyeb, open Organization settings → API and create an API access token. It has no scopes and is deactivated when its creator leaves the organisation.
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