Data & Cloud
24x7 monitoring and on-call for your cloud systems
Brihat Infotech watches your systems around the clock and answers when an alert fires. A pod of site reliability engineers (SREs) holds the pager, and each environment has a named first and second on-call engineer.
What the cover includes
- Monitoring and response
24x7, with alerts routed to the on-call engineer.
- Patching and lifecycle
operating system and software updates on a schedule, plus planned retirement of old versions.
- Backup and recovery checks
restores are tried, so a backup is known to work.
- Quarterly reviews
performance and cloud spend, with a list of changes to make.
- Capacity reviews
whether each system has room for the load you expect next.
- Escalation to builders
a problem beyond the runbook goes to the engineers who know the code.
- Runbooks and knowledge transfer
written steps for your own staff, kept current.
Systems we did not build
The cover is not limited to our own work. If your platform came from another vendor or your own team, we take it on. A handover period comes first, running alongside whoever supports it today, so the first alert is not our first look.
When an alert fires
The on-call engineer takes the alert and follows the runbook for that system. A problem the runbook does not cover goes to the engineers who built or know the code. Each incident has a severity level and a named escalation path, and ends with a written review of what happened and what changes.
How the cover is arranged
- 01Handover. We read your systems and runbooks, and sit beside your current support.
- 02Start of cover. Our on-call pod takes the pager on an agreed date.
- 03Quarterly review. You and an architect look at incidents, cost and the next changes.
The cover is ongoing, with a 3-month minimum. It is priced as a monthly retainer, set by the number of environments and the level of cover, and reviewed each quarter. For how a project is staged, see How we engage.
What stays with you
- Runbooks for every environment we cover
- Reports from each quarterly review
- The option to move support to your own team at any time, with a handover at standard rates
Where this service fits
Support usually follows a move or a build, and the Google SRE book describes the on-call practice we follow. See cloud architecture and migration for the move, DevOps and reliability for the release routine, and security and compliance for testing of what we run.
Tell us which systems page your team at night.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.