Image

Self-healing
software.

Your code didn’t change. Everything under it did. Since.dev turns supported API, SDK and model changes into repair PRs.

A change becomes a way forward.
Dependency changeAn API has moved.
Supported repairA draft PR is ready.
Illustrative workflow
Reduced motion

For the dependencies behind what you build.

Imagenpm
ImageGitHub
ImagePyPI
ImageRust
ImageOpenAPI
ImageRubyGems

From outside change to inside fix

Less chasing changes.
More moving forward.

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

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: sendmessages.create

Illustrative workflow. Fictional package and observations.

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

Your code has dependencies.
We keep an eye on them.

API contract

An endpoint moved.Your product shouldn’t have to stop.

Connect a documented API change to the calls that use it. Prepare a supported migration for the affected code.

Explore supported sources
Endpoint deprecatedExample
/v1/messages/v2/messages
src/integrations/messages.ts
Review the supported migration
An illustrated repair workbench joining two connectors in a sunlit gardenSmall patch. Clear evidence.

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 and review the updated patch.

  • The source behind the fix.

    Upstream evidence stays with the repair.

Give your agents
a reality check.

Before an agent acts, check its assumptions against the latest recorded observation.

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.

Unknown does not mean unchanged.

Your dependencies. Your priorities.

Follow what matters.
Know what changed.

Keep up with API changes, security fixes, and new releases in one place.

Your watch instructions and notifications stay private.

How watches work

The updates your team depends on.

Public changes

A clearer view of what changed.

Browse package and API changes, with links to the original source.

Explore changes
Image

One changing world.
Your way in.

Give your agents the changes they need through MCP, HTTP API, or signed webhooks.

ReadProcessAcknowledge

Catch up on changes since your agent’s last acknowledged update.

Read the docs

mcp.json

{
  "mcpServers": {
    "since-dev": {
      "type": "http",
      "url": "https://api.since.dev/mcp",
      "headers": {
        "Authorization": "Bearer sc_live_..."
      }
    }
  }
}

Watch subjects, verify facts, inspect coverage, and catch up from the tools your agent already uses.

Integration guide
A little context for every change.
breakingdeprecatedbehavioraladditiveadvisory

Start free.
Build from there.

Paid plans use your AI provider, billed directly to you. Free includes AI for your first eligible repair PR each month.

Free

For developers trying world state and repository impact.

$0 / month

Free, with no card required

Start free
  • 25 analysis credits a month
  • 1 connected repository
  • 50 repository dependencies monitored
  • 10 World State watches, every aspect of each
  • 1 draft repair PR a month, on demand
  • 100 verification calls a month
  • 1 workspace member

Studio

For agencies and teams maintaining several applications.

$149 / month

$1,490 a year, save 17%

Start free
  • Bring Anthropic, OpenAI, or AWS Bedrock
  • 15 connected repositories
  • 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

Enterprise needs? Contact us

Good questions.
Clear answers.

Read the docs
What does self-healing software mean?
Here, self-healing starts with upstream change: an API moves, an SDK removes a method, or a model is retired. Since.dev finds affected code and prepares supported repairs as draft PRs.
How often are sources checked?
Check frequency depends on your plan and the source. Each watch shows when it was last checked and how often it updates. Changes are detected on that schedule.
What does unknown mean?
There isn’t enough recorded evidence to answer. Check the observation time and source health before relying on the result. Unknown does not mean unchanged.
What can I watch?
Start with a supported package, repository, specification, public page, or status source. Coverage is checked before a watch is created. Private registries, sources behind a login, and sources closed to automated reading are not covered.
What happens while my agent is offline?
Your agent can catch up on changes from its watches since its last acknowledged update. New watches cover future changes only.
What counts toward my plan?
Free includes one repository, 25 analysis credits and one eligible draft PR per month. Pro connects five repositories and Studio connects fifteen. Paid plans use your AI provider, with no Since repository AI or dependency quotas. Watch and verification allowances are separate. A watched subject counts once across its aspects and attached agents. Each login gets one Free workspace. Additional owned workspaces need their own subscriptions.
How does bringing my own model work?
On Pro, connect Anthropic or OpenAI. Studio and Enterprise also support AWS Bedrock. Your provider bills repository AI usage directly, and Since charges for the workspace. Free repairs and World State watches include Since AI. If your provider connection fails, repository AI work pauses until you reconnect it.
Do I need to add every repository dependency by hand?
No. Automatically monitor dependencies is selected when you connect a repository. Since finds supported public dependencies and shows what it can monitor. Adjust your choices at any time. Free includes 50 repository dependencies. Paid plans have no dependency count limit. Notifications begin with changes detected after the first check.
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. CI runs in your repository. Since.dev never merges or deploys.
How does the Free repair allowance work?
Free repositories stay in Monitor only. Choose Prepare repair on an eligible symbol rename or endpoint replacement that works with your current dependency. The allowance is used only when a draft PR opens; failed or rejected attempts do not use it. There are three generation attempts per UTC calendar month and two requested revisions of that PR within 30 days. AI is included. You need workspace management permission and GitHub write access. The allowance resets on the first day of the next UTC month.
Can I ask for a different fix?
Yes. Request a revision in the dashboard, or mention the installed GitHub app in a comment on its repair PR. Include what you want changed. Repository collaborators with permission can revise that repair. Since updates the same PR and reruns its checks.
Image
A little peace of mind.

Keep building.
We’ll keep watch.

Your dependencies keep changing. Since.dev keeps watch and prepares supported repair PRs for the code they affect.

Start free