CloudMonkey field notes
Trust should be checkable.
Start with public information. Ask for scope-specific evidence before treating a process, screenshot or product description as proof of an outcome.
People and expertise
Meet the team and its published roles. We do not attribute a specialist review or certification to anyone without a record of it.
Meet the CloudMonkey teamSupport commitments
Read the published service-level terms, then confirm coverage, exclusions and escalation for your contract. Written terms are not historical response-time evidence.
Read service-level termsService status
Use the public status page as a starting point. A current indicator is not a historical uptime audit or proof that every customer workload is monitored.
Open public statusPrivacy responsibilities
Review the published privacy and POPIA information alongside the data flows and supplier terms for your proposed implementation.
Read POPIA informationEvidence we request before publishing a delivery story
A dated implementation record, a clear scope, approval for named or anonymous publication, and a redaction review. Quantitative results also require a measurement method, observation period and supporting evidence. If those are missing, we leave the result unpublished.
For managed backups, ask for a scoped restore-test record. For monitoring, ask which services are covered and how alerts are escalated. No customer restore records, monitoring dashboards or private platform screenshots are published here at present.
Public screenshots must show only cleared material: no account identifiers, credentials, private addresses, customer records or security configuration. A product illustration is never labelled as operational evidence.
Prepare your backup and recovery questions · Browse approved case studies