Service 13
Hosting, Cloud & Support
Someone responsible for the thing staying up — hosting, backups tested by restoring them, security patches, monitoring, and a named person who answers when something breaks.
- Timeline
- Ongoing, cancel with 30 days
- Deliverables
- 10 items
- First milestone
- Week 1
Anyone running software they cannot afford to have go down
Software is not finished at launch; it is only started. Dependencies get security advisories, certificates expire, disks fill, and a backup nobody has ever restored is a rumour rather than a backup. This is the retainer that makes those somebody's job — and it is genuinely optional, because everything we hand over runs whether or not you buy it.
Typical stack
What you get
Not included
- Cloud infrastructure bills (at actuals)
- New feature builds
- Third-party licences
Listed as plainly as the inclusions. Anything here can be scoped on top — quoted before it starts, never assumed.
How it works
A backup you have watched restore
Backups are verified by restoring them into a scratch environment on a schedule, and the restore time is in your monthly report. An untested backup is the most common form of imaginary safety in small business IT.
Patching before the advisory becomes an incident
Dependency advisories are monitored and patched on a cadence, tested on staging first. This is unglamorous and it is the reason systems quietly keep working for years.
Response times that are written down
Site down: same working day, and out of hours on the higher tier. Something broken but usable: two working days. A change request: inside the monthly allowance. Written into the agreement, not implied.
Your account, your keys
Everything runs in cloud accounts you own and pay for directly at actuals, with no markup. You can revoke our access and keep running — which is exactly the leverage a client should have.
Delivery sequence
- 01Week 1
Takeover audit
Current hosting, backups, certificates, access and known risks documented — including for systems we did not build.
- 02Week 2
Baseline hardening
Monitoring, alerting, automated backups, staging and access control put in place before routine support begins.
- 03Monthly
Ongoing
Patch cadence, change requests, quarterly restore tests and a monthly report.
Support FAQ
Straight answers
Including where the honest answer is 'no' or 'buy something else'.
Will you support software somebody else built?
Often yes, after a takeover audit. If the codebase turns out to be unsupportable — no source, no documentation, abandoned framework versions — we will tell you that and what the realistic options are, rather than charging a retainer to hope.
What does ₹4,000 a month cover?
Monitoring, backups, patching, SSL and domain management, and a small monthly change allowance for one system. Multi-system estates, higher response tiers and out-of-hours cover are priced up from there, and the infrastructure bill is separate and paid by you at actuals.
Is this compulsory after a build?
No. Thirty days of bug fixing is included with every project regardless. After that the retainer is a choice — the code is yours, the deployment is yours, and an in-house developer or another vendor can pick it up from the runbook we hand over.