Scan your companyScan
PRODUCT

How Auterim protects what you run on.

From finding your dependencies to proving what was handled: what each part of Auterim does, and where it stops.

Scan your companySee pricing
01DiscoverFind the services you run on, from a scan and the tools you connect.02WatchRead each provider’s own changelogs, docs, pricing and policies.03DecideSet aside the noise, then match what remains to your context.04ActVerify in your code, prepare a fix for review, hand it to your team.
Read the full walkthrough on How it works
01DISCOVER

Start from what is already visible.

Auterim builds your dependency list from what your website shows first, then from the tools you choose to connect. You confirm every entry.

Dependency discovery

ALL PLANS

A scan of your website reads response headers, scripts, linked hosts and pages. Each finding carries the signal it came from and how sure Auterim is.

yourcompany.com · scan complete5 likely dependencies
Vercel · Hostingx-vercel-id response headerHIGH
Cloudflare · CDNcf-ray response headerHIGH
Stripe · Paymentsjs.stripe.com on /checkoutHIGH
Supabase · Databaserequests to *.supabase.coMEDIUM
OpenAI · AIapi.openai.com in page configPOSSIBLE
Possible matches stay unconfirmed until you confirm them.

Connectors

Connect the tools that see what a scan can’t. Each one asks for the narrowest permission it needs.

GitHubPRO
READ-ONLYContents of the repositories you select
SlackALL PLANS
WRITE · ONE CHANNELPost alerts to a channel you choose
LinearPRO
WRITE · ONE TEAMCreate issues in a team you choose
SentryPRO
READ-ONLYProjects and issues, for runtime context
02WATCH

Read the source, not the rumour.

Each dependency is tied to the pages its provider maintains. Auterim checks them continuously and keeps the exact text that changed.

Authoritative monitoring

ALL PLANS

Every dependency maps to the pages its provider publishes. Auterim reads those, not news, forums or social posts.

OpenAIAI provider · marked criticalWATCHING
Changelogplatform.openai.com/docs/changelog2m ago
Docsplatform.openai.com/docs/api-reference4m ago
Pricingdevelopers.openai.com/api/docs/pricing6m ago
Deprecationsplatform.openai.com/docs/deprecations9m ago
Policiesopenai.com/policies/usage-policies12m ago

Change detection

ALL PLANS

When a page changes, Auterim keeps the exact excerpt that moved, captured from the provider’s own source.

OpenAI · Deprecationscaptured 5 Oct, 14:02 UTC
Shutdown date Model Replacement
Removed: TBD gpt-4o-2024-05-13 TBD
Added: 2026-11-04 gpt-4o-2024-05-13 gpt-4.1
2026-07-14 gpt-4-0613 gpt-4.1
Excerpt from platform.openai.com/docs/deprecations. Nothing paraphrased.
03DECIDE

Most changes are not your problem.

Two filters run on every change: is it material at all, and does it touch the way you use this provider.

Materiality filtering

ALL PLANS

Redesigns, marketing posts and typo fixes are read and set aside. Changes to behaviour, price, limits, deadlines or terms move forward.

Today · 24 changes read1 material
Dashboard navigation redesignedVercel · changelogNO IMPACT
New payment method available in JapanStripe · changelogNO IMPACT
gpt-4o-2024-05-13 shutdown scheduledOpenAI · deprecationsMATERIAL
Typo fixes in Auth guidesSupabase · docsNO IMPACT
Blog: new template galleryResend · blogNO IMPACT
Status page styling updateCloudflare · statusNO IMPACT

Customer relevance

ALL PLANS

A material change is matched against what you told Auterim. Where you haven’t said, it says so instead of guessing.

gpt-4o-2024-05-13 shutdown scheduled
CRITICALITY
Critical, marked by you
MATCH
MODEL IN USE
gpt-4o-2024-05-13
MATCH
ENDPOINT
/v1/chat/completions
MATCH
DEADLINE
4 Nov 2026 · in 30 days
FROM SOURCE
MONTHLY VOLUME
Not provided
UNKNOWN
Relevant to yourcompany.comHIGH URGENCY · 30 DAYS
04VERIFY

Find where it actually lands.

With GitHub connected, a relevant change is checked against your code. Either it appears, with a location, or it does not.

GitHub Preflight

PRO

For a relevant change, Auterim searches the repositories you connected for the exact identifiers it names: models, endpoints, SDK versions, config keys.

search "gpt-4o-2024-05-13"3 repositories
yourcompany/webNO MATCHES
yourcompany/api2 MATCHES
yourcompany/workersSEARCHING
Read-only. Code is read in memory and not stored.

Verified impact

PRO

A finding is bound to a file, a line and a commit, so anyone can open it and check.

VERIFIEDyourcompany/api · src/lib/llm.ts
LINE 42COMMIT a3f9c21BRANCH main
export async function complete(input) {
return client.chat.completions.create({
model: 'gpt-4o-2024-05-13',
messages: input,
});
1 more finding · src/jobs/summarize.ts:18
05ACT

Prepared for review. Never shipped for you.

Auterim drafts the fix and routes the work. A person on your team decides what merges and what deploys.

Fix preparation

PRO

A proposed change for that exact finding, grounded in the provider’s own guidance. It waits for a person to review it.

src/lib/llm.tsFOR REVIEW
return client.chat.completions.create({
Removed: model: 'gpt-4o-2024-05-13',
Added: model: 'gpt-4.1',
messages: input,
GROUNDED INOpenAI’s deprecation notice names gpt-4.1 as the recommended replacement.
Auterim never merges or deploys.BUSINESSOpen draft pull request

Handoffs

The change, the evidence and the deadline go where your team already works.

#eng-alertsALL PLANS
Auterim 14:10OpenAI shuts down gpt-4o-2024-05-13 on 4 Nov. Verified in 2 files in yourcompany/api. A fix is ready for review.View change
ENG-128PRO
Replace gpt-4o-2024-05-13 before 4 Nov
DUE
3 Nov 2026
FILES
llm.ts:42, summarize.ts:18
SOURCE
Auterim change #A-2291
06PROVE

A record of what changed and what you did.

When someone asks whether you were affected, the answer is already written down, with sources.

Protection history

ALL PLANS

Every change, decision and action is kept with its evidence. Upcoming deadlines stay pinned until someone closes them.

UPCOMING
4 Nov 2026OpenAI · gpt-4o-2024-05-13 shutdownFIX IN REVIEW
1 Feb 2027Supabase · legacy API keys retiredNOT AFFECTED
HISTORY
  1. Linear issue ENG-128 created5 Oct · 14:10
  2. Fix prepared for review5 Oct · 14:09
  3. Verified in 2 files, yourcompany/api5 Oct · 14:06
  4. Marked material and relevant5 Oct · 14:03
  5. Change detected · OpenAI Deprecations5 Oct · 14:02
  6. Supabase pricing update reviewed · no action28 Sep
  7. Stripe API version change resolved12 Sep
EVIDENCE MODEL

Every claim shows its source.

Three layers, each built on the one before. Auterim only says as much as the evidence at that layer supports.

  1. GLOBAL1 / 3

    What changed

    An excerpt from the provider’s own source, with where and when it was captured. The same for every customer.

    source openai.com · deprecations
    excerpt gpt-4o-2024-05-13 · 2026-11-04
  2. WORKSPACE2 / 3

    Why it matters to you

    Matched against what you told Auterim. Unknowns stay unknown; nothing is guessed to fill a gap.

    match critical · model in use
    unknown monthly volume
  3. VERIFIED3 / 3

    Where it hits

    A finding bound to a file, line and commit in your connected code. Present only when it can be shown.

    file src/lib/llm.ts:42
    commit a3f9c21

See what you run on.

Start with a scan of your website. Confirm what’s right, add what’s missing.

Scan your companyHow Auterim handles your data →