This release is a pre-release and may not be stable for production use.
Unpage: Build SRE agents that understand your infrastructure
Modern infrastructure is complex. For agents to be effective, they need context and secure access to your dev tools.
With Unpage, you can build production-ready SRE agents in minutes:
- Define agents in YAML: Configure how they respond to events.
- Route intelligently: Match alerts and requests to the right agent.
- Give agents context: Map your infrastructure with plugins and a knowledge graph.
- Integrate securely: Connect agents to logs, metrics, traces, infra providers, and external tools via MCP or shell access.
Unpage Agents
Unpage agents are defined in natural language in YAML files. This is an example agent that investigates SSL/TLS connection failures and provides a summary on the incident:
# SSL-connection-failure-agent.yaml
# Description: Used by the router to determine which agent to use for the alert
description: Investigate SSL/TLS connection failures
# Prompt: Instructions for the agent to follow when acting on the alert
prompt: >
- Extract the domain/hostname from the alert about connection failures.
- Use shell command `shell_check_cert_expiration_date` to check the certificate expiration dates
- Parse the certificate dates to determine if the cert is expired or expiring soon
- If certificate is expired or expiring within 24 hours:
- Post high-priority status update to the incident explaining the root cause
- Include the exact expiration date and affected resources
# Tools: Allows the agent to use the specified tools during its investigation
tools: >
- "shell_check_cert_expiration_date"
- "pagerduty_post_status_update"
Description: When Unpage is running and receives an incident payload from your alerting tool, the router uses the agent description to determine which agent should act on the incident.
Learn more about Unpage's router here.
Prompt: The selected agent will follow the investigation steps listed in the prompt. This will often resemble a runbook for the type of alert.
Tools: In order to do its investigation, the agent uses tools to understand your infrastructure and retrieve more details about the alert, as needed. You can limit the tools that the agent has access to by specifying them in this section.
Note: You can list all available tools by running
unpage mcp tools list
Learn more about connecting plugins and tools here.
Response: In this case, the CPU alert agent will leave a comment on the incident:
ROOT CAUSE IDENTIFIED: SSL certificate for domain ‘expired-rsa-dv.ssl.com’ is EXPIRED. Certificate expired on August 2, 2016 GMT (over 8 years ago). This explains the SSL connection failures. IMMEDIATE ACTION REQUIRED: Certificate renewal needed for affected domain to restore SSL connectivity.
You can customize your agents to automatically respond to different types of alerts and take different actions to address them. See more examples here.
To create your first agent, install Unpage and run Quickstart. You'll have a handful of example agents to start from, or you can create your own!
# Install Unpage
curl -fsSL https://install.unpage.ai | bash
# Quickstart
unpage agent quickstart
If you need help, you can find us in the Unpage Slack community or follow along with this demo: https://www.youtube.com/watch?v=z17sHig2xMk
Installation
On macOS:
curl -fsSL https://unpage.ai/install.sh | bash
For other platforms, first install uv using the official uv installation guide, then run the command above.
Quickstart
To get started, run:
unpage agent quickstart
This will get you up and running with your first agent, which will automatically investigate and add context to alerts from PagerDuty (or your preferred alerting provider). You will also have a chance to set up your infrastructure knowledge graph to provide your agent with more context.
Learn More
- Test and run your agents
- Set up your knowledge graph
- Expand your agent's knowledge with custom scripts
Have a request for the Unpage team? Let us know on Slack or GitHub.
Documentation
Detailed documentation lives in docs/, and is also published via Mintlify to docs.unpage.ai.
License
See LICENSE.md.
Copyright
Copyright (c) 2025 Aptible. All rights reserved.
1 maintainer
Metadata
1 maintainer
Release files for unpage 0.1.0a45
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| unpage-0.1.0a45.tar.gz | 348.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| unpage-0.1.0a45-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 583.6 kB
Release files / unpage-0.1.0a45.tar.gz
| Download URL | unpage-0.1.0a45.tar.gz |
|---|---|
| Size | 348.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1be95dba482ff1a1ee705b679015b309341f101b48119e084baa2df11df49a13
|
|
BLAKE2b-256 checksum How to use checksums |
fc8fb349ffb1f7daf8c02915fe8c90b42a1394996e4f861ea6fb29ae294d981c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.5
|
Release files / unpage-0.1.0a45-py3-none-any.whl
| Download URL | unpage-0.1.0a45-py3-none-any.whl |
|---|---|
| Size | 235.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42d9cd25be55a7b1fbc4b067bf531a491018c34b73e57d4d184540fc6d772a5d
|
|
BLAKE2b-256 checksum How to use checksums |
27e36dfffd5f317fdac94268832f7646d1e95de24e44e1895a574cbb449e8c63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.5
|
