Hire Grant. Your COO and his ops team.

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’s team
  • Grant, COOGrant
  • David, Compatibility and repairsDavid
  • Maya, GitHub CIMaya
  • Liz, AWS costsLiz
  • Noah, AWS runtimeNoah
  • Priya, SecurityPriya
  • Owen, Configuration and lifecycleOwen
  • Iris, World StateIris
Image

Since : 25 public changes across npm, crates.io, GitHub and 1 more.

Latest recorded (UTC). See the changes

Reads from
  • npm
  • GitHub
  • PyPI
  • Rust
  • OpenAPI
  • RubyGems
+7 more sources
Since.dev featured on There's An AI For That

Hire Grant, get the whole team behind him.

Grant leads AI specialists for CI, cloud costs, runtime, security and dependencies, and brings you answers with the evidence attached.

  • Grant, COO

    Grant

    COO

    His team’s briefs, the findings and your decisions

  • David, Compatibility and repairs

    David

    Compatibility and repairs

    World State changes · Repository context

  • Maya, GitHub CI

    Maya

    GitHub CI

    GitHub Actions · Repository context

  • Liz, AWS costs

    Liz

    AWS costs

    AWS costs

  • Noah, AWS runtime

    Noah

    AWS runtime

    AWS runtime metrics

  • Priya, Security

    Priya

    Security

    GitHub security alerts · AWS Security Hub · Repository context

  • Owen, Configuration and lifecycle

    Owen

    Configuration and lifecycle

    Repository context · World State changes

  • Iris, World State

    Iris

    World State

    World State changes

  • Put them to work

    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 free

Illustrative activity Every label is one the product shows while the team works.

Ask Grant. His team does the legwork.

Ask in plain words. Grant brings in the right specialists, shows their sources, and keeps long jobs going until they report back.

ImageGrantFollow-upImageNoah

Lambda errors on checkout-api went from 0.2% to 1.1% after Tuesday’s deploy.

In the same conversation

Check-insDaily on Pro

  • Workflow runs and checksMaya
  • PushesDavid and Owen
  • New alertsPriya

Every six hours on Studio

ImageThe test job is taking longer

Maya · GitHub CI

  • Owner @sam
  • Deferred
  • Revisit on Friday

At the next check-in, new runs are compared with the saved finding.

Outside change. Inside fix.

Connect your GitHub repository. See what changed, find the affected code, and review a supported repair.

  • API changes
  • SDK updates
  • Deprecations
  • Provider changes
A change, followed through.Interactive example
Dependency change detected

The SDK changed.
Now you know.

A scheduled check finds a release and its official migration guide.

Previously observed19.0.009:00
Latest observed20.0.010:15
Migration guide: send → messages.create

Illustrative workflow. Fictional package and observations.

Supported patches and draft PRs by Since.dev. Tests run in your repository.

An illustrated repair workbench joining two connectors in a sunlit garden

Since.dev Draft PR

Small patch. Clear evidence.

Removed: client.sendAdded: client.messages.create

ImageDavid · Reports open repair PRs

Repairs that fit your workflow.

Since.dev traces supported upstream changes to affected code and prepares a focused patch.

  • Your checks, already in place.

    Draft PRs use your existing CI.

  • Revisions on the same PR.

    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.

  • The source behind the fix.

    Upstream evidence stays with the repair.

  • One repair a month on Free.

    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 where you already work. Same Grant. Same team. Same findings.

Ask in a Slack thread, the dashboard or your agent’s MCP client. Each one reaches the same Grant, his team and your findings.

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.

Slack

Illustrative

ops

Grant App

@sam asked Grant

how’s my AWS ops?

Grant App

@sam asked Grant

Done · consulted Liz, Noah Liz · Done Noah · Done

Grant App

Answer for @sam

Compute spend rose from $120 to $156 across same-length periods (Liz). Lambda errors on checkout-api went from 0.2% to 1.1% after Tuesday’s deploy (Noah).

/grant how’s my AWS ops?

Dashboard

Illustrative

How’s my AWS ops?

Consulted Liz, Noah and Priya

  • ImageLizDone
  • ImageNoahDone
  • ImagePriyaStopped. 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-upImageNoah

Lambda errors on checkout-api went from 0.2% to 1.1% after Tuesday’s deploy.

MCP

Illustrative

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": [ … ] }, … }

ImageIris · World State

Watch what your code depends on.

Get API changes, security fixes, and new releases for the things you watch.

Your watch instructions and notifications stay private.

How watches work

ImageIrisWorld StateIllustrative

A watch found a change

example-sdk 19.0.0 to 20.0.0breaking

client.send is replaced by client.messages.create.

Official release notes and migration guide

Give your agents a reality check.

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 verification
Does this still hold?example-sdk.version = 19.0.0
Something changed20.0.0

The observation differs. Your agent gets evidence to review.

Illustrative results · check observation time and source health. Verification reads recorded evidence, without a fresh fetch.

A clearer view of what changed.

Browse published package and API changes, each linked to its evidence.

Explore changes
A little context for every change.
  • breaking
  • deprecated
  • behavioral
  • additive
  • advisory

Start free. Add the team when you’re ready.

Free answers from saved results; paid plans consult the team live on your own model account.

  • No card required
  • Daily check-ins on Pro
  • Bring your own model on paid plans

Grant Free

Meet Grant with one project and a monthly operational baseline.

$0 / month

Free, with no card required

Start free

Grant Studio

Check-ins every six hours across fifteen projects.

$149 / month

$1,490 a year, save 17%

Start free

Grant Enterprise

Agreed project scope, check-in cadence and support for your team.

Custom

Terms agreed with your team

Contact us
See everything in each plan

Free 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.

Grant Free

  • 1 active project
  • 1 hosted baseline + 5 follow-up check-ins per UTC month
  • 25 analysis credits a month
  • Grant plus David, Maya, Liz and Priya
  • Grant in the dashboard only
  • 30 days of history
  • 250k hosted AI tokens a month
  • 50 repository dependencies monitored
  • 5 World State watches, every aspect of each
  • 1 draft repair PR a month, on demand
  • 100 verification calls a month
  • 1 workspace member

Grant Pro

  • 5 active projects
  • Daily check-ins
  • Bring your Anthropic or OpenAI key
  • Grant and the whole team
  • Grant in Slack, MCP and the dashboard
  • Full history
  • No repository dependency count limit
  • 150 World State watches, every aspect of each
  • Automatic repairs and draft PRs
  • 500 verification calls a month
  • 3 workspace members

Grant Studio

  • 15 active projects
  • Check-ins every 6 hours
  • Bring Anthropic, OpenAI, or AWS Bedrock
  • Grant and the whole team
  • Grant in Slack, MCP and the dashboard
  • Full history
  • No repository dependency count limit
  • 500 World State watches, every aspect of each
  • Automatic repairs and draft PRs
  • 2,000 verification calls a month
  • 10 workspace members

Grant Enterprise

  • Custom project allowance and cadence
  • Your Anthropic, OpenAI or AWS Bedrock models
  • Workspace limits agreed by contract
  • Sales-led onboarding and billing

Good questions. Clear answers.

Read the docs
Who is Grant?
Grant is the COO for your software operations, an AI agent built by Since.dev. He leads a preset team of specialists who watch your GitHub Actions CI, AWS costs and runtime metrics, existing GitHub and AWS security findings, repository configuration and lifecycle, and dependency compatibility. Each reads its own sources and saves a brief. Ask Grant in Slack, the dashboard or your agent's MCP client: he consults the teammates your question needs, answers in one voice with the evidence and keeps track of what you decide. Free answers in the dashboard from saved results; paid plans consult the team live on your own model.
Are Grant and his team real people?
No. Grant and every specialist on his team are AI agents built by Since.dev, not people. They read the GitHub and AWS evidence you connect; supported repairs arrive as pull requests for your review, and nothing merges or deploys. Grant covers your software operations only: he doesn't hire, manage people or handle finance.
What's the difference between Free and paid?
Free covers one project with a hosted AI allowance: one baseline and five follow-up check-ins per UTC month. Free 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. Grant answers from saved results and says as of when; he does not consult the team live. Pro adds Noah, Owen and Iris, Grant in Slack and MCP, full history and daily check-ins. Paid plans consult the team live in Slack, the dashboard and MCP, check in daily on Pro or every six hours on Studio, and also check in when GitHub reports a workflow run, a check, a push or a new alert. Paid work runs on your own Anthropic or OpenAI account, or AWS Bedrock from Studio, with any model ID the connection test marks ready for Grant.
What do I need to connect?
Start on Home: choose GitHub or AWS and connect it. On GitHub, install the Since.dev app and pick a repository; it becomes your first project. On AWS, create a read-only role from the template we prepare, then name the project and choose what the team reads. On a paid plan, connect one AI provider. Then choose Approve and start check-in, and your team runs its first check-in right there. Only following public sources? Create a World State watch instead. Existing repositories and watches remain connected. Slack and signed webhooks are optional. Missing connections and unsupported resources appear as coverage gaps.
Can Grant change my cloud or production systems?
No. Check-ins and consults only read your connected GitHub and AWS evidence. Grant can record decisions and follow up, but cannot change AWS resources, rerun workflows or enable scanners. The existing repair flow can open draft pull requests for human review, and nothing merges on its own. Compatibility repairs keep their repository permissions, eligibility and repair settings. A cloud or security finding does not grant permission to write code or make production changes.
What can Grant see in Slack?
Once your Slack and Since identities are linked (automatically when your Slack email matches your Since account), ask with /grant or a mention in a channel: Grant answers publicly in that thread and discusses only the connection's projects, every project unless an owner narrowed them. DM Grant for a private, persistent chat over your own access. Grant reads only messages addressed to him (mentions, /grant and DMs with him), never broad channel history.
Does it repair my code automatically?
New paid repository connections default to Automatic draft PRs. Since automatically checks impact, prepares supported repairs, and opens draft PRs. Choose Monitor only to prepare repairs on demand. Repairs cover small, documented compatibility fixes in code and configuration. Routine version bumps and lockfile changes are outside that scope. If the evidence is insufficient, no PR is created. That does not prove your code is unaffected. Where GitHub doesn't offer draft PRs (private repositories on GitHub Free or Pro), the repair opens as a regular PR titled [Needs review]. CI runs in your repository. Since.dev never merges or deploys.
How does bringing my own model work?
On Pro, connect Anthropic or OpenAI. Studio and Enterprise also support AWS Bedrock. Type any model ID your provider account can use, or pick a suggestion; the connection test checks it before saving, and Grant needs strict tool calling. One provider and model serves Grant, his team and repository AI. Your provider bills paid Grant and repository model usage directly. If the selected provider fails, work waits for recovery instead of silently switching accounts. Free repairs and World State watches include Since AI within their separate allowances. A watched subject counts once across its aspects and attached agents.

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.

Clock out. Grant’s team is on.

The team runs check-ins on your plan’s schedule and reports back when it’s done.

The night shiftIllustrative

  1. ImageMayacheck-in (workflow run)
  2. ImagePriyanew high finding · notice posted to #ops
  3. ImageLizscheduled check-in
  4. ImageNoahscheduled check-in

Scheduled check-ins run daily on Pro and every six hours on Studio.