All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Patch Management System
Start now
More

Features

Industries

Reference

More

Patch Management System · Available now

Track each patch from catalog to asset outcome.

Patch Management System keeps a patch catalog and records each attempt against a specific asset. The team can identify the product, version, severity and release date, then record when installation started, when it completed and whether the outcome was verified, failed or rolled back.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewScheduled patch attempts
Patch Management System · Patch attempts

Scheduled patch attempts

installing waits for the patch operator

New patch attempt
Patch attempts in view
6
Scheduled
6
NameAssetPatchStatusStarted atCompleted at
Apply October kernel update to app node 2Identity gateway primaryReporting engine memory fixScheduled19 Oct
Update database agent on payroll hostBooking service node 3Reporting engine memory fixScheduled20 Oct
Install browser security fix on kiosk 4Identity gateway primaryTLS library certificate fixScheduled31 Oct
Patch label server in west warehouseWest warehouse label serverIdentity gateway session fixScheduled20 Oct
Upgrade TLS library on order APIOrder API node 1Reporting engine memory fixScheduled03 Nov
6 of 6 records
Apply October kernel update to app node 2Patch attempts · PA-20662
Scheduled
AssetIdentity gateway primary
PatchReporting engine memory fix
Started at19 Oct
Review the changePA-20662 · Apply October kernel update to app node 2

Change Manager decides after reviewing service impact with Service Owner.

Waiting for Change Manager
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
14
Roles with set permissions
7
Reports and dashboards
8
Features

Follow the patch on each asset

Every feature works on the same records. Pick one to see the screen your team works in.

Patch catalog

Identify the release before recording work against an asset.

  • Catalog identity
  • Release context
  • Severity
  • Patch catalog
  • Patch attempts
  • Assets
Explore patch catalog
OverviewPatches by severity
Patch Management System · Patch catalog

Patches by severity

Patch catalog

New
Patch IDPatch titleProductVersionSeverityReleased at
PATCH-2026-1011October kernel security updateServer operating system6.4.12High13 Oct
PATCH-2026-1012Database agent stability fixDatabase monitoring agent6.4.13Critical13 Oct
PATCH-2026-1013Browser remote execution fixKiosk web browser8.2.7High28 Oct
PATCH-2026-1014Print spooler security updateWarehouse print service8.3.1Critical02 Nov
PATCH-2026-1015TLS library certificate fixOrder API runtime12.1.4High15 Oct
6 of 6 records
PATCH-2026-1011Patch catalog · PC-33510
High
Patch titleOctober kernel security update
ProductServer operating system
Version6.4.12
Released at13 Oct
Example screen with sample data
Process

From release to verified result

Patch planning to verification ships ready to use. One step needs a named approval before the work moves on: Review the change (Change Manager).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Catalog the patch

    Identify the intended product, version and release.

    Apply October kernel update to app node 2PA-20662
    Catalog the patch

  2. Select the asset

    Confirm the asset tag and affected service.

    Apply October kernel update to app node 2PA-20662 · Patch Operator
    Select the assetBy Patch Operator

  3. Review the change

    Review risk, work window and rollback plan.

    Apply October kernel update to app node 2PA-20662 · Change Manager
    Review the changeBy Change Manager
    ApprovalChange Manager decides after reviewing service impact with Service Owner.

  4. Schedule the attempt

    Record the selected patch and asset for work.

    Apply October kernel update to app node 2PA-20662 · Patch Operator
    Schedule the attemptBy Patch Operator

  5. Record installation

    Capture when installation starts and completes.

    Apply October kernel update to app node 2PA-20662 · Patch Operator
    Record installationBy Patch Operator

  6. Verify the outcome

    Record Verified, Failed or rolled back for the asset.

    Apply October kernel update to app node 2PA-20662 · Patch Operator
    Verify the outcomeBy Patch Operator

Start with Patch planning to verification

Inside a record

Bring your patch and asset sources

Open any patch attempt to see the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Asset, Patch and Started at.

  2. 2
    Linked records

    Records linked to this patch attempt.

  3. 3
    Who works on it

    Patch Operator, Change Manager and Service Owner, each with their own permissions.

  4. 4
    Process stages

    Select the asset and Schedule the attempt, with the role that acts.

  5. 5
    Approvals

    Review the change, with who decides.

Scheduled patch attemptsApply October kernel update to app node 2
Patch Management System · Patch attempts

Apply October kernel update to app node 2

Identity gateway primary · Scheduled

Log activity
1
Record details
AssetIdentity gateway primary
PatchReporting engine memory fix
Started at19 Oct
3

Who works on it

  • Patch OperatorManage patch attempts
  • Change ManagerManage Changes
  • Service OwnerManage Services, Incidents
4

Process stages

  • Select the assetPatch Operator
  • Schedule the attemptPatch Operator
5

Approvals

  • Review the changeChange Manager
    Approved
Example screen with sample data
Approvals

Review service change risk

OverviewApprovals
Patch Management System · Overview

Approvals

Signed in as Change Manager

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-97170Patch app nodes during Sunday window
    Warehouse label printingRequested by Patch Operator
    Low1dActions
  • CHN-52946Investigate TLS errors after library update
    Finance reporting warehouseRequested by Patch Operator
    Medium4dActions
  • CHN-75114Restart label server after spooler fix
    Payroll file transferRequested by Patch Operator
    High5dActions
  • CHN-75308Review kiosk compliance gap
    Order intake APIRequested by Patch Operator
    Low5dActions

Who approves what

DecisionApprover
Review the changeReview risk, work window and rollback plan.Change Manager
Approve ChangesChange Manager
2 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Patch Management System to the work that is theirs. Pick a role to see what it starts with.

Patch Operator

Records asset-specific patch attempts and their outcomes.

This is the first screen this role sees.

OverviewChange schedule

Change schedule

Changes · Patch Operator

SummaryServiceRiskScheduled startScheduled endStatus
Patch app nodes during Sunday windowWarehouse label printingLow30 Oct06 NovApproved
Investigate TLS errors after library updateWarehouse label printingMedium22 Oct29 OctImplementing
Restart label server after spooler fixOrder intake APIHigh30 Oct04 NovApproved
Review kiosk compliance gapFinance reporting warehouseLow12 Oct15 OctImplementing
Restore reporting node after rebootPayroll file transferMedium26 Oct04 NovApproved
6 of 6 records
Example screen with sample data

Roles and permissions

Reports

Read outcomes by service

Review patch outcomes, change timing and service exceptions from recorded work.

Overview
Patch Management System · Overview

Patch Management System dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Patch attempts by status

How far records got this quarter

StageReachedStep
Scheduled49
Installing2653%
Verified1246%
Failed975%

Number of patch attempts by status

Sample counts per stage

1000
100Scheduled
100Installing
60Verified
80Failed
90Rolled back
Example screen with sample data
  1. 01Patch attempt outcomes

    Compare attempt statuses by patch and asset.

  2. 02Verification lag

    Compare the start and completion dates of verified attempts.

  3. 03Patch severity by product

    Group catalog records by product and severity.

  4. 04Change review queue

    Show changes in Review by service and risk.

  5. 05Change windows

    Compare scheduled start and end dates by service and status.

  6. 06Service incident trend

    Count incidents by service, priority and opened date.

  7. 07Problem ownership

    Group open problems by service and owner.

  8. 08Integration receipt exceptions

    Group rejected and failed receipts by provider and received date.

All reports and dashboards

Who it's for

For teams maintaining service assets

See how Patch Management System fits your kind of team.

Internal IT

Track patch work across equipment that supports internal services.

Managed IT operations

Keep asset patch outcomes and service decisions understandable to an operations team.

Distributed service teams

Coordinate patch work across assets at different locations.

Controls

Keep failures visible

Each stage of patch planning to verification names the role that acts and the status it records, so a change is never anonymous.

OverviewPatch planning to verification
Patch Management System · Process

Patch planning to verification

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
8
Draft the change
Change Manager
StatusDraft → Review
RecordsServices, Changes
Review the changeApproval
Change Manager, Service Owner
StatusReview → Approved
RecordsServices, Changes
Record installation
Patch Operator, Change Manager
StatusScheduled → Installing
RecordsPatch attempts, Changes
Patch planning to verification
  1. Start
    Draft the changeDraft → Review
    Services
  2. Approval
    Review the changeReview → Approved
    Services
  3. Step
    Record installationScheduled → Installing
    Patch attempts
  4. Step
    Verify the outcomeInstalling → Verified
    Patch Operator
Example screen with sample data

See each stage in detail

AI agent

Prepare the next handoff with Proto

Use Proto to prepare patch work and review the records behind decisions.

It can

  • Patch Operator: Find scheduled attempts for an asset and summarize the linked patch identity before work begins.
  • Change Manager: Gather a change's service, risk, planned window and rollback plan for human review.
  • Service Owner: Compare failed attempts and open incidents for the service they own.
  • Admin: List receipt exceptions by provider for investigation.

Stays with a person

  • A person decides whether a change is approved, whether a rollback plan is adequate and whether installation evidence supports Verified.
  • The agent can prepare a record summary and highlight an inconsistency; the responsible role records the decision.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Patch Management System
  • Patch source
  • Asset inventory
  • Event provider
  • Installation tooling
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Patch catalog3
  • Patch attempts5
  • Changes5
  • Assets and services5
  • Incidents and problems6
  • Requests and receipts6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Confirm ownership

    Name Service Owners, Change Manager, Patch Operator and response staff. Agree who maintains catalog and asset references.

  2. Prepare records

    Load Services, Assets and PatchCatalog. Check asset tags, product and version values, and service links.

  3. Rehearse decisions

    Review a change with risk, scheduled dates and rollback plan. Record an approval and a rejection.

  4. Run attempts

    Record separate attempts for selected assets. Verify one, fail one and review both with the Service Owner.

  5. Review response

    Open an incident for a disrupted service and check the root cause handoff to Problems where needed.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Patch Management System.

All questions
How do I get started?

Click Get started, then use Proto to configure Patch Management System for your business. Begin with one service, its assigned assets and a patch release. Rehearse a reviewed change and an asset-specific attempt before expanding the scope.

What does the patch catalog record?

It identifies the patch ID, title, product, version, severity and release date. The installation result lives on the attempt for an asset.

How do we know whether an asset received a patch?

Open the patch attempt for that asset and patch. Review its status and actual start and completion dates.

Can several assets use one patch catalog entry?

Yes. Each asset gets its own attempt linked to the same patch. Their outcomes can differ.

Where is the planned work window?

The change record holds scheduled start and end dates, risk and a rollback plan. Attempt records hold actual execution dates.

Who approves a service change?

Change Manager reviews the change with Service Owner and records the approval or rejection decision before implementation.

What happens when installation fails?

The attempt remains Failed or rolled back for review. If service was disrupted, Incident Responder records the affected service and asset in an incident.

How is a recurring cause followed?

Problem Analyst opens a problem for the service, assigns an owner and records the investigation and root cause separately from immediate incident response.

What do integration receipts show?

They show provider, external event ID, received time, payload hash and receipt outcome. Check the related operational record before treating an applied event as an installation result.

Where do service requests fit?

A request records its requester, service, timing and decision. A change and a patch attempt carry the separate approval and installation records when the request leads to patch work.

Set up Patch Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appPatch Management System

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.