Engineering and operations connectors
Issues, changes, incidents and the decisions behind them, searchable by people who do not use the tracker.
- GitHubIssues, pull requests, code and commits, searchable by anyone who can ask a question.Token or OAuthHourly sync
- AWS CloudWatchLogs, metrics and alarms from AWS, answered in plain English with the query that found them.IAM access key
- SentryAsk what is breaking in production and get the stack trace, not a dashboard.Auth tokenHourly sync
- ServiceNowTickets, changes and knowledge without the eleven-tab ServiceNow trip.API key (username and password, HTTP Basic)
- OktaWho has access to what, answered from the source.API key (SSWS token)
- TwilioAsk what happened to your messages and callsAPI key
- AWS CloudTrailWho changed what in your AWS account, answered from the audit log.IAM access keyHourly sync
- GitLabIssues, merge requests, pipelines and code from GitLab.API keyHourly sync
- BitbucketPull requests, pipelines and code from Bitbucket Cloud.API keyHourly sync
- VercelDeployments, build logs and domains from Vercel.API keyHourly sync
- PagerDutyIncidents, timelines and on-call from PagerDuty.API keyHourly sync
- DatadogAsk what is alerting, what the logs say and how a metric moved, without opening Datadog.API key + application keyHourly sync
- GrafanaRun the queries behind your dashboards and ask what is firing, straight from chat.Service account tokenHourly sync
- incident.ioEvery incident, its timeline, owners and follow-ups, remembered and searchable.API keyHourly sync
The questions that cross systems
Most engineering and operations questions are only half answerable inside engineering and operations. These pairs are where the rest of the answer lives.
Who asks for this
- EngineeringKeep decisions from evaporatingDecisions, owners and deadlines are extracted from conversations and tool results into a typed, time-aware memory. Corrections supersede old facts instead of piling up next to them.
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.
- ProductHear what customers actually ask forFeature requests are scattered across tickets, call notes, Slack threads and issues. Memtro reads them where they live, links them to the customers who raised them, and remembers which decision closed each one.
Other categories
Connect one and ask it something
Seven days free. Connectors, jobs and memory are never metered, and model usage stays on your own provider keys.