For software that needs care outside working hours.
Everything in Keep, plus
Incident response outside working hours, in agreed windows
Capacity and cost planning
Improvement time each month for the backlog you choose
A named point of contact who knows the system
How we handle access.
Each of us uses a named account of our own. We never share logins.
Access goes through your accounts, such as your cloud, code host and hosting, so you can see it and remove it at any time.
Credentials live in a password manager, never in email, chat or code.
When an engagement ends, we hand back every credential, remove our access and confirm it in writing.
Everything we set up lives in your accounts and is documented, so you can take it elsewhere.
Agreed in writing.
No prices or response times here. Both depend on what you run, so we agree them in writing after we have looked at your system. New features are scoped separately; a plan keeps what exists healthy.
BusyLake