Hosting & data location
The proposed hosting arrangement, service boundaries and relevant data locations are stated before launch. We favour established managed services over unnecessary infrastructure.
Technical assurance
Small software still deserves grown-up care.
Every proposal is proportionate to the job, but small does not mean casual. These are the operational questions RZLVR resolves before a supported tool becomes part of somebody’s working day.
Access & secrets
Access follows least-privilege principles. Service credentials and secrets are kept outside source code and production access is limited to what support requires.
Backups & recovery
The scope identifies what needs backing up, how recovery works and which third-party services remain responsible for their own data protection.
Monitoring & response
Managed tools receive proportionate availability and error monitoring, with a named route for reporting operational problems and an agreed response window.
Dependencies & change
External APIs, packages and SaaS dependencies are recorded. Material updates are tested and changes are made through a controlled release path.
Documentation & exit
You receive a plain-English account of what the system does, where it runs and what it depends on. Data exports and handover arrangements are designed to avoid hostage-taking.
Third-party services
Dependencies are made visible, not wished away.
Where a solution relies on Microsoft 365, accounting software, a CRM, an API or another SaaS provider, the proposal identifies that dependency and its practical limits. RZLVR cannot control a supplier’s availability or product decisions, but can design sensible failure handling, monitoring and an exit route.
This approach reflects Mark Kaye’s experience operating business-critical technology environments: proportionate controls, explicit ownership and an honest account of what remains outside the system’s control.
If RZLVR stops supporting a managed tool, the documented handover covers source materials, deployment information, data export and known dependencies, subject to the ownership terms agreed for the project.
Assurance should fit the risk