All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

DevOps Dashboard
Start now
More

Features

Industries

Reference

More

DevOps Dashboard · Available now

Follow releases from change review to deployment outcome.

A release manager raises a change for a service, records its risk, scheduled window and rollback plan, and sends it to review. A CAB reviewer records the decision.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Incidents
DevOps Dashboard · Incidents

Open Incidents

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
Increase checkout worker capacityAdmin console
23 Oct
Patch build runner imageCheckout API
27 Oct
Add
Medium2
Investigate elevated API latencySearch indexer
25 Oct
Rotate billing webhook secretCustomer identity service
28 Oct
Add
High1
Deploy order retry fixInventory sync
25 Oct
Add
Critical1
Restore inventory event streamCustomer identity service
15 Oct
Add
Increase checkout worker capacityIncidents · INC-70021
Low
Opened at23 Oct
StatusOpen
ServiceAdmin console
Assigned toAmina Yusuf
CAB reviewINC-70021 · Increase checkout worker capacity

CAB Reviewer decides whether the planned change proceeds.

Waiting for CAB Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
53
Saved views
16
Roles with set permissions
6
Reports and dashboards
8
Features

See release and service work in context

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

Incident response

Acknowledge incidents, investigate impact, and keep response evidence together.

  • Acknowledge
  • Investigate
  • Resolve
  • Incidents
  • Incident updates
  • Response events
  • Service impact assessments
  • Service outages
  • Services
Explore incident response
OverviewMy Assigned Incidents
DevOps Dashboard · Incident response

My Assigned Incidents

Incidents

New
SummaryPriorityOpened atStatusServiceAssigned to
Increase checkout worker capacityLow29 OctOpenBilling workerSamir Patel
Investigate elevated API latencyMedium27 OctAcknowledgedCustomer identity serviceAmina Yusuf
Deploy order retry fixHigh01 NovInvestigatingSearch indexerPriya Srinivasan
Restore inventory event streamCritical01 NovResolvedSearch indexerNadia Chen
Patch build runner imageLow26 OctClosedAdmin consoleHana Kim
6 of 6 records
Increase checkout worker capacityIncidents · INC-92388
Low
Opened at29 Oct
StatusOpen
ServiceBilling worker
Assigned toSamir Patel
Example screen with sample data
Process

Follow the release from review to outcome

Review and deliver a release change ships ready to use. One step needs a named approval before the work moves on: CAB review (CAB Reviewer).

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

  1. Change drafted

    Prepare the service, risk, window and rollback plan.

    Increase checkout worker capacityINC-70021 · Release Manager
    Change draftedBy Release Manager

  2. CAB review

    A CAB reviewer records the decision and reason.

    Increase checkout worker capacityINC-70021 · CAB Reviewer
    CAB reviewBy CAB Reviewer
    ApprovalCAB Reviewer decides whether the planned change proceeds.

  3. Change approved

    Move accepted work into the delivery schedule.

    Increase checkout worker capacityINC-70021 · Release Manager
    Change approvedBy Release Manager

  4. Deployment pending

    Start implementation with a pending environment record.

    Increase checkout worker capacityINC-70021 · DevOps Engineer
    Deployment pendingBy DevOps Engineer

  5. Deployment outcome

    Record the version and observed environment result.

    Increase checkout worker capacityINC-70021 · DevOps Engineer
    Deployment outcomeBy DevOps Engineer

  6. Change verified

    Close the change against its deployment evidence.

    Increase checkout worker capacityINC-70021 · Release Manager
    Change verifiedBy Release Manager

Start with Release change review

Inside a record

Bring delivery evidence into the service record

Open any incident to see its service outages, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Opened at, Status, Service and Assigned to.

  2. 2
    Service outages

    Each line is linked to this incident.

  3. 3
    Who works on it

    Incident Responder and Service Desk Manager, each with their own permissions.

  4. 4
    Process stages

    Incident acknowledged and Incident investigated, with the role that acts.

  5. 5
    Approvals

    CAB review, with who decides.

Open IncidentsIncrease checkout worker capacity
DevOps Dashboard · Incidents

Increase checkout worker capacity

Admin console · Low

Log activity
1
Record details
Opened at23 Oct
StatusOpen
ServiceAdmin console
Assigned toAmina Yusuf
2
Service outages

Increase checkout worker capacity

Site codeComponent numberStarted at
US-WEST-1SO-8403118 Oct
US-EAST-2SO-6950724 Oct
PDX-EDGESO-6594916 Oct
Service outages
6
Total lost request estimate
2,950
3

Who works on it

  • Incident ResponderManage Incidents, incident updates, response events
  • Service Desk ManagerManage service requests, Problems
4

Process stages

  • Incident acknowledgedIncident Responder
  • Incident investigatedIncident Responder
5

Approvals

  • CAB reviewCAB Reviewer
    Approved
Example screen with sample data
Approvals

Record the change decision

Release Manager prepares changes; CAB Reviewer owns the recorded change decision; DevOps Engineer records pipeline and deployment results.

OverviewApprovals
DevOps Dashboard · Overview

Approvals

Signed in as CAB Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-83993Increase checkout worker capacity
    Search indexerRequested by Release Manager
    Low1dActions
  • CHN-14507Investigate elevated API latency
    Admin consoleRequested by Release Manager
    Medium3dActions
  • CHN-67576Deploy order retry fix
    Checkout APIRequested by Release Manager
    High2dActions
  • CHN-96390Restore inventory event stream
    Order event processorRequested by Release Manager
    Low5dActions

Who approves what

DecisionApprover
CAB reviewA CAB reviewer records the decision and reason.CAB Reviewer
Approve ChangesCAB Reviewer
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 DevOps Dashboard to the work that is theirs. Pick a role to see what it starts with.

Release Manager

Owns release change preparation, scheduling and the deployment handoff.

This is the first screen this role sees.

OverviewChange Schedule

Change Schedule

Changes · Release Manager

SummaryServiceScheduled startScheduled endStatus
Increase checkout worker capacityNotification gateway25 Oct02 NovApproved
Investigate elevated API latencyCheckout API23 Oct01 NovImplementing
Deploy order retry fixOrder event processor31 Oct07 NovApproved
Restore inventory event streamSearch indexer23 Oct29 OctImplementing
Patch build runner imageAdmin console30 Oct07 NovApproved
6 of 6 records
Example screen with sample data

Roles and permissions

Reports

Read the result behind each status

Read release outcomes and operational response from their source records.

Overview
DevOps Dashboard · Overview

DevOps Dashboard

This quarter

Changes in view
6
Approved
3
Implementing
3

Incidents by status

How far records got this quarter

StageReachedStep
Open33
Acknowledged2061%
Investigating1260%
Resolved867%

Number of incidents by status

Sample counts per stage

900
90Open
50Acknowledged
30Investigating
70Resolved
40Closed
Example screen with sample data
  1. 01Incident state by service

    Shows incident status and priority within each service.

  2. 02Acknowledgement timing

    Compares opened and acknowledged times for incidents.

  3. 03Change review decisions

    Lists CAB decisions, reviewers and meeting dates by change.

  4. 04Deployment outcomes by environment

    Groups deployment status and version by environment and service.

  5. 05Pipeline run results

    Shows run status and finish time by branch and service.

  6. 06Request completion against due date

    Compares completion and due dates for service requests.

  7. 07Asset service coverage

    Shows assets and verified links under each service.

  8. 08Integration receipt exceptions

    Shows rejected and failed receipts by provider and receipt time.

All reports and dashboards

Who it's for

Fit the way your IT team operates

See how DevOps Dashboard fits your kind of team.

Software platforms

Coordinate frequent service releases and production response.

Managed IT services

Keep service work tied to requests, assets, and incidents.

Internal IT operations

Manage internal service changes and support work with visible owners.

Controls

Keep review and response history visible

Each stage of review and deliver a release change names the role that acts and the status it records, so a change is never anonymous.

OverviewReview and deliver a release change
DevOps Dashboard · Process

Review and deliver a release change

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

Process stages
11
Approval steps
1
Roles involved
5
Tables touched
8
Change drafted
Release Manager
StatusDraft → Review
RecordsServices, Changes
Change approved
Release Manager
StatusReview → Approved
Pipeline run checked
DevOps Engineer
StatusRunning → Passed
RecordsPipeline runs, Services
Review and deliver a release change
  1. Start
    Change draftedDraft → Review
    Services
  2. Approval
    CAB reviewCAB Reviewer
    Changes
  3. Step
    Change approvedReview → Approved
    Release Manager
  4. Step
    Pipeline run checkedRunning → Passed
    Pipeline runs
  5. Step
    Deployment pendingApproved → Implementing
    Deployments
Example screen with sample data

See each stage in detail

AI agent

Ask Proto about the next handoff

Ask Proto to help inspect records and prepare the next operational handoff.

It can

  • Release Manager: Find changes awaiting review and summarize their service, risk, window and rollback plan.
  • CAB Reviewer: Prepare the change context and existing review history before the reviewer records a decision.
  • DevOps Engineer: Compare pipeline run results with the deployment records for a service and environment.
  • Incident Responder: Gather the incident state, assigned person, recent updates and affected asset for a shift handoff.

Stays with a person

  • Proto can help read and organize the work, but a CAB reviewer must make the change decision.
  • The responsible engineer records the observed deployment result, and the incident responder checks the situation before closing response work.
  • Review an action against the live record and your access policy before applying it.
  • Agent use follows the metering and access rules of the customer's ERP.AI workspace.

Set up an agent

Integrations

Connects to the tools you use

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

  • DevOps Dashboard
  • Source control and CI
  • Deployment infrastructure
  • Incident intake
  • Provider events
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 53 tables
53tables
  • Incident response7
  • Change review5
  • Delivery tracking5
  • Service requests3
  • Asset context5
  • Operational knowledge4
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. Establish service context

    Name active services, their owners and the assets responders need to identify. Confirm the people who prepare changes, decide CAB reviews and respond to incidents.

  2. Prepare working queues

    Agree change risk rules, request types, priority choices and due dates. Check the incident, change and service request screens with the people who will use them.

  3. Connect evidence

    Map pipeline runs and deployment results to the matching service. Record provider event identifiers and processing states separately. Rehearse a rejected receipt so the team knows where to investigate it.

  4. Rehearse decisions

    Send a release change through CAB review, start implementation and record a deployment outcome. In parallel, capture an incident and verify acknowledgement and investigation evidence.

  5. Review the first cycle

    Compare actual records with the reports for change decisions, deployment results, incident response and request completion.

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 DevOps Dashboard.

All questions
How do I get started?

Click Get started, then use Proto to configure DevOps Dashboard for your business. Begin with an active service, its owner, a release change, a pipeline run and a deployment environment. Rehearse the CAB decision and an incident handoff before widening the scope.

What does the release change cover?

A change records the service, summary, risk, planned window, rollback plan and status. The CAB review records the reviewer, decision, date and reason. The deployment record then follows the environment result.

How is a pipeline run different from a deployment?

A pipeline run records a branch, commit, run time and result for a service. A deployment records the environment, version, time and observed outcome. Read both when deciding whether a release reached the intended environment successfully.

Who decides whether a change proceeds?

The CAB Reviewer records the advisory decision and reason. The Release Manager uses that decision when moving the change forward. The delivery team works from the approved change and its planned window.

Can the team track a rollback?

Yes. A deployment can be marked rolled back and include a rollback reference. Rollback checks can retain expected and actual checkpoint results, while the change retains its rollback plan and final state.

How does incident acknowledgement work?

Capturing an incident starts the acknowledgement workflow and records the first response event. When investigation starts, the workflow moves the incident into Investigating and adds an attributed update.

Can requests be reviewed against due dates?

Service requests carry requested, due and completed times. The manager can follow active work and compare the completion time with the due date in the request report.

Where do asset details fit?

An incident can reference an asset and service. Asset records carry the tag, serial number, location and state, while asset service links record a dependency and verification time.

What should be connected first?

Start with the systems that provide pipeline results and deployment outcomes, then agree how incident intake identifies the matching service and how provider receipts are investigated by event ID. Test a rejected integration receipt during setup so the team knows how to investigate it.

Set up DevOps Dashboard 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 appDevOps Dashboard

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.