
Grant
COO
His team’s briefs, the findings and your decisions
Grant and his specialists watch your CI, cloud costs, runtime, security and dependencies, then bring you what matters with the evidence in Slack, the dashboard or MCP. They’re all AI agents, and nothing merges or deploys.
Grant
David
Maya
Liz
Noah
Priya
Owen
Iris
Grant leads AI specialists for CI, cloud costs, runtime, security and dependencies, and brings you answers with the evidence attached.

COO
His team’s briefs, the findings and your decisions

Compatibility and repairs
World State changes · Repository context

GitHub CI
GitHub Actions · Repository context

AWS costs
AWS costs

AWS runtime
AWS runtime metrics

Security
GitHub security alerts · AWS Security Hub · Repository context

Configuration and lifecycle
Repository context · World State changes

World State
World State changes
Ask Grant anything. Supported fixes arrive as draft PRs, and you set the project scope. Free answers from saved results; paid plans consult the team live.
Hire Grant freeIllustrative activity Every label is one the product shows while the team works.
Ask in plain words. Grant brings in the right specialists, shows their sources, and keeps long jobs going until they report back.
Grant asks up to six teammates at once and answers with citations. Paid plans do this live.
Work still running after about 45 seconds, or when you ask, keeps going in the background and reports back in the same conversation.
The team checks in on your plan’s schedule (daily on Pro, every six hours on Studio) and when GitHub reports a workflow run, a check, a push or a new alert.
Assign an owner, defer to a date or mark it addressed. The next check-in picks up where you left off. Marking it addressed records your decision; it isn’t proof. A disconnected account holds up only its own sources.
GrantFollow-up
Noah
Lambda errors on checkout-api went from 0.2% to 1.1% after Tuesday’s deploy.
In the same conversation
Check-insDaily on Pro
Every six hours on Studio
The test job is taking longer
Maya · GitHub CI
At the next check-in, new runs are compared with the saved finding.
Connect your GitHub repository. See what changed, find the affected code, and review a supported repair.
Illustrative workflow. Fictional package and observations.
Supported patches and draft PRs by Since.dev. Tests run in your repository.

Since.dev Draft PR
Small patch. Clear evidence.
Removed: client.sendAdded: client.messages.create
David · Reports open repair PRs
Since.dev traces supported upstream changes to affected code and prepares a focused patch.
Draft PRs use your existing CI.
Request a revision in the dashboard, or mention the installed GitHub app in a comment on its repair PR. Since updates the same PR and reruns its checks.
Upstream evidence stays with the repair.
Free repositories stay in Monitor only. The allowance is used only when a draft PR opens; failed or rejected attempts do not use it.
Ask in a Slack thread, the dashboard or your agent’s MCP client. Each one reaches the same Grant, his team and your findings.
Like a teammate in the thread. DMs are private and persistent. Nothing Grant says is ephemeral. Channel answers stay within the projects the connection covers.
Watch the team work. Stop any one of them.
Your agent can ask too. 20 tools; start with grant_team_status. Waits up to 55 seconds, then call again with the same requestKey.
Connect in a minute: MCP, an HTTP API and signed webhooks. Catch up on changes since your agent’s last acknowledged update. New watches cover future changes only.
ops
Grant App
@sam asked Grant
Grant App
@sam asked Grant
Grant App
Answer for @sam
/grant how’s my AWS ops?
How’s my AWS ops?
Consulted Liz, Noah and Priya
LizDone
NoahDone
PriyaStopped. Partial results are saved.Grant
Compute spend rose from $120 to $156 across same-length periods (Liz). Priya was stopped, and her partial results are saved. Noah is still working and will post here when he’s done.
GrantFollow-up
Noah
Lambda errors on checkout-api went from 0.2% to 1.1% after Tuesday’s deploy.
Call
grant_question({
input: { content: "How's my AWS ops?",
conversationId: null, waitSeconds: 55 },
requestKey: "ops-review-0929"
})After up to 55 seconds
{ "status": "running",
"answer": null,
"team": [{ "name": "Liz",
"activity": "AWS costs" }, … ] }The same call again
{ "status": "completed",
"answer": {
"content": "Compute spend rose…",
"references": [ … ] }, … }Valid, changed or unknown against the latest recorded observation, with its observation time and source health. Unknown does not mean unchanged.
That’s world state: external facts, versions, and provider conditions, ready for your agents to check.
Explore verificationexample-sdk.version = 19.0.020.0.0The observation differs. Your agent gets evidence to review.
Illustrative results · check observation time and source health. Verification reads recorded evidence, without a fresh fetch.
Browse published package and API changes, each linked to its evidence.
Explore changesFree answers from saved results; paid plans consult the team live on your own model account.
Meet Grant with one project and a monthly operational baseline.
$0 / month
Free, with no card required
Start freeDaily check-ins across five projects.
$49 / month
$490 a year, save 17%
Start freeCheck-ins every six hours across fifteen projects.
$149 / month
$1,490 a year, save 17%
Start freeAgreed project scope, check-in cadence and support for your team.
Custom
Terms agreed with your team
Contact usFree includes Grant plus David, Maya, Liz and Priya in the dashboard, the last 30 days of history (older records are kept) and 250k hosted AI tokens a month. Pro adds Noah, Owen and Iris, Grant in Slack and MCP, full history and daily check-ins. Paid plans consult the team live on your own Anthropic or OpenAI account, or AWS Bedrock from Studio, with any model ID the connection test marks ready for Grant.
More in the docs, or email hello@since.dev. For CI, AWS costs, security and the COO role at a small startup, read DevOps for startups and the other operations guides.
The team runs check-ins on your plan’s schedule and reports back when it’s done.
The night shiftIllustrative
Mayacheck-in (workflow run)
Priyanew high finding · notice posted to #ops
Lizscheduled check-in
Noahscheduled check-inScheduled check-ins run daily on Pro and every six hours on Studio.