On call, 24/7
Picks up alerts the minute they fire, finds the cause in logs, deploys and code, fixes it and tells you what happened. You read it over coffee.
For small teams without an SRE
The AI engineer who's on call, so your team isn't.
Pagerless joins your Slack, takes tickets from your board, watches production and fixes what breaks: code, CI, cloud settings, DNS. It learns your system week by week and asks before anything risky.
From €1,000 a month plus AI usage at cost. No hiring, no rotation.
# prod-alerts
Example
Checkout API: error rate 18% for 5 min
On it. Started right after the 02:58 deploy: the new payment webhook times out on a missing index.
- Reproduced on staging
- Fix + migration in PR #482, tests green
- Deployed to staging, errors back to 0%
Production deploy needs your OK under your rules.
Approve
Not now
Live in production. Error rate 0.1%. Card moved to Done with the root cause.
Works where your team already works
- Slack
- Telegram
- GitHub
- Jira
- Trello
- Linear
- AWS
- Cloudflare
- Sentry
- Docker
- Postgres
What it does
Not a coding assistant. A teammate who finishes the job.
Coding agents turn a ticket into a pull request. Pagerless takes it from the first message to production and stays with it after.
Takes the backlog
Assign it a card in Jira, Trello or Linear, or just ask in a Slack thread. It writes the code, runs your checks, ships through your pipeline and moves the card.
Owns the boring infra
Red CI, expiring certificates, DNS records, cloud settings, dependency and security updates. The work nobody has time for gets done.
Learns your system
Keeps notes on your architecture, your conventions and your past incidents, so week four is faster than week one. It never starts from zero.
How it works
Earns trust step by step.
-
Week 1
Its own machine, read-only
Every customer gets a private sandbox: its own computer, browser and accounts. We connect your repos, board, chat and monitoring, and it starts by reading and mapping your system.
-
Weeks 2–3
Small tickets, with your OK
It takes real cards and real alerts. Every deploy and every outside change waits for one tap from you in Slack or Telegram.
-
After that
Autonomy you choose
You decide what it does alone, what it does and reports, and what always waits for you. Change it any time.
Safety
Clear rules for what it may touch.
An example of the rules a team starts with. Yours can be stricter or looser.
Does it alone
Reads code, logs and metrics. Writes code and tests, opens pull requests, fixes CI, deploys to staging.
Does it, then tells you
Production deploys of changes that passed every check. Routine updates you allowed.
Asks you first
Spending money, access and permissions, deleting production data, stopping servers.
Never
Showing or sending secrets, force-pushing, wiping a production database.
- Isolated per customer. Your code and accounts live only in your own sandbox.
- Every action logged. See what it did, why, and what it cost.
- Your AI account. Bring your own Claude or OpenAI account, or we pass usage through at cost.
Why Pagerless
What you'd do without it.
Coding agents
AI SRE tools
Hiring a DevOps engineer
Pagerless
Writes the code
YesNoYesYes
Answers alerts at 3 am
NoDiagnosesSometimesFixes
Cloud, DNS and CI
NoRead-onlyYesYes
Ships to production
NoNoYesWith your rules
Ready in
MinutesWeeksMonthsAbout a week
Pricing
Priced like a tool, works like a hire.
Team
€1,000 / month
plus AI usage at cost
- One private sandbox for your team
- Slack or Telegram, your board, repos and monitoring
- 24/7 alerts and fixes under your rules
- Setup and onboarding by us
- Monthly, cancel any time
Agencies
Per client project
for teams that maintain many clients
- A separate sandbox for every client
- Maintenance and on call across all of them
- Usage reported per client
Preliminary pricing for the pilot. AI usage is shown in your log as it happens.
Questions
Fair questions.
Who is it for?
Product teams of 2 to 10 developers with production to run and nobody whose job is to watch it. Agencies that maintain many client projects too.
Does it replace my developers?
It takes the work that keeps them from building: on call, red builds, upgrades, small bugs and infra chores. Think of it as the next engineer you'd hire.
What if it gets something wrong?
Changes go through your own checks and staging first, risky steps wait for your OK, and every release can be rolled back. It tells you what went wrong and fixes forward.
Can it see our secrets?
It uses them only inside your sandbox to do the work, and it never prints, sends or commits them. Access you give it can be taken back any time.
Which AI models does it use?
The strongest available from Anthropic and OpenAI, picked per task. Simple work runs on cheaper settings, so usage stays predictable.
We're starting with a few pilot teams.
We set it up with you, on your real system, and you see in a month what it handled on its own.
Pilot applications open soon.