What shipped yesterday
Maya Okafor, engineering manager at Acme Ltd, asked what was deployed to production yesterday. Memtro listed each deployment with its service, commit message, image tag and who deployed it.
Is the API service up, and which builds failed today?
Northflank runs your services, jobs and databases, and Memtro reads it for you. It reads projects, services with build and deployment status, builds, deployments with image and commit, jobs and their runs, and database addons. When asked and granted, it can run or abort a job, pause or resume a cron schedule, and restart, pause or resume a service. It can also start or abort builds, manage databases and delete a service or job. Northflank can tell Memtro when a build fails or a container crashes, and a job can start on it. Database credentials are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Northflank tool, reads what it needs, and answers with the source cited.
These tools change something in Northflank. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Northflank for you. Each event can start a job, with the event as its input. Northflank sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Northflank 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.
Is the API service deployed and running?
Which builds failed today?
When did the nightly import job last succeed?
Which databases in the production project are paused?
Restart the worker service.
Maya Okafor, engineering manager at Acme Ltd, asked what was deployed to production yesterday. Memtro listed each deployment with its service, commit message, image tag and who deployed it.
When Northflank told Memtro a service container had crashed at Northwind, a job started. It read the service's recent deployments and builds and posted them to Dan Fletcher, the on-call engineer.
The teams that lean on Northflank most, a question each of them asks, and what they connect beside it.
A record in Northflank 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 Northflank, go to Team settings, then API, then Tokens. Create an API role with the read, update and delete permissions Memtro should have, then create a token with that role.
In Memtro, open Connections → Northflank and paste the API token. For an organisation token, also enter the Team ID.
An administrator grants the service, job, build and database actions by name to the engineers who may use them. Events are turned on from the connection's Events tab.
Ask which builds failed today.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Northflank tools are the same everywhere.
Only when you ask, and only what it has been granted: run a job now; abort a running job run; pause or resume a cron job's schedule; restart a service; pause a service (takes it offline); resume a paused service; start a build of a service from a branch, pull request or commit; abort a service build; restart a database addon; pause a database addon; resume a paused database addon; back up a database addon now; delete a service; delete a job. 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 token, plus Team ID for organisation tokens. In Northflank, go to Team settings, then API, then Tokens. Create an API role with the read, update and delete permissions Memtro should have, then create a token with that role.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Northflank for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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