Identity & access
Users inherit one role. Roles own read and write permissions by product area. Failed sign-in attempts can lock an account, and sessions are short-lived.
Security, support and supplier evidence
Inspect Sendense before you depend on it.
Review the company, architecture, compatibility, security controls, support routes, customer evidence and current assurance status behind the platform.
Use the same evidence to prepare technical, security and procurement review.
What do you need to approve?
Know the supplier behind the product.
These are the published company facts used across the website identity, Privacy Notice and Terms of Use.
Sendense Limited
- Legal name
- Sendense Limited
- Companies House identifier
- 17296917
- Registered address
- Prime Apartments, 483 Green Lanes, London, N13 4FG, GB
- Legal contact
- legal@sendense.com
- Website
- https://sendense.com
Inspect the architecture and qualify the exact environment.
Compatibility is evaluated across the complete source, storage, repository and recovery path. Start with the environment you actually operate.
01
Source environment
Start from the hypervisor, storage path and recovery target you already operate.
02
Sendense control and data paths
Inspect how capture, orchestration and evidence are separated across the documented appliance roles.
03
Repository and recovery destination
Qualify the repository you control and the destination used for restore, replication or migration.
Review the controls around access, data paths and recovery.
These groups summarise documented controls. Use the security architecture and product documentation for the exact behaviour and qualifications.
Credentials & platform access
The credential vault stores secrets encrypted at rest. Saved secrets are not displayed again, actions leave an audit record, and credentials can be scoped to a site or appliance.
Data paths & network dependencies
Remote nodes are designed to initiate outbound connectivity to the hub on the documented management path. Protected sites are not required to expose broad inbound management.
Repository, retention & deletion
Repository data is encrypted in the documented design. Retention and deletion follow the configured protection pattern and repository governance. Object Lock depends on repository capability and configuration.
Audit & recovery evidence
Audit records cover access and credential actions. Recovery validation can record integrity, mount and boot evidence for supported recovery points when that workflow is enabled.
Current assurance status, stated plainly.
Sendense distinguishes published product evidence from contractual scope and from assurance it does not currently claim.
| Evidence area | Status | Summary | Source |
|---|---|---|---|
| Product architecture documentation | Published | The product architecture page documents SNA, SHA and SCA appliance roles. | Product Architecture |
| Security architecture documentation | Published | The security architecture page documents remote connectivity, the credential vault and encryption at rest. Identity, session, lockout, credential-scope and recovery-validation behaviour are in the product documentation. | Security Architecture |
| Compatibility documentation | Published | Current documented integrations and named platform pages are published. They are not an exhaustive compatibility matrix. | Compatibility & Integrations |
| Public product documentation | Published | Public product documentation covers deployment, operations, credentials, access control and recovery validation. | Documentation |
| Approved customer project evidence | Published | The approved public customer evidence is the Quadris VMware-to-CloudStack migration project. | Quadris Customer Story |
| Independent security assessment | Not claimed | Sendense does not currently claim an independent security assessment on this website. | Not a public evidence source |
| Certifications | Not claimed | Sendense does not currently claim a security certification on this website. | Not a public evidence source |
| Support terms | Contract-specific | Production support responsibilities and escalation are agreed as part of the delivery plan. | Contact |
| Privacy and legal information | Published | The Privacy Notice and Terms of Use publish Sendense Limited's company identity and legal contact details. | Privacy Notice |
Agree support and escalation around the deployment.
Evaluation help is a review process. Production coverage is contractual. This page does not publish a support portal, telephone number or a universal coverage entitlement.
During evaluation
Evaluation starts in a real environment and uses the published documentation.
During implementation
Named owners agree deployment, environment access, acceptance criteria and handoff for the project.
In production
Production support responsibilities and escalation are agreed as part of the delivery plan.
Use the product evidence directly.
These routes are the published product and operating evidence. There is no public system-status page.
Review named project evidence.
The approved public customer evidence is a named VMware-to-CloudStack migration project delivered by Quadris.
Named project evidence
Quadris
Quadris used Sendense for a named VMware-to-CloudStack migration project and continued protecting the estate with Backup as a Service. Results are from one customer project. Timelines vary with estate size, connectivity, workload dependencies and cutover requirements.
Prepare a supplier review from the evidence already published.
Use this checklist to gather the published evidence. There is no downloadable security or procurement pack on this page.
Choose the smallest proof step that answers the buying question.
Start with the evaluation path that matches how you operate. These routes do not publish a deployment-time promise.
Security and Trust FAQs
What company supplies Sendense?
Sendense is supplied by Sendense Limited, Companies House 17296917, with registered office at Prime Apartments, 483 Green Lanes, London, N13 4FG, GB. Legal contact is legal@sendense.com.
Where does Sendense run?
Sendense is downloadable backup, recovery and migration software. It runs within the customer or provider architecture so organisations retain control over infrastructure, repositories and recovery paths.
How should we check whether our environment is supported?
Compatibility is evaluated across the complete source, storage, repository and recovery path. Start with the environment you actually operate, then review the current documented integrations and named platform pages. The public integrations list is not an exhaustive matrix.
Which security information is publicly available?
The Security Architecture page documents remote connectivity, the credential vault and encryption at rest. Public product documentation covers users and RBAC, session and lockout behaviour, credential scope and recovery validation.
Does Sendense claim a security certification or independent assessment?
No. Sendense does not currently claim a security certification or an independent security assessment on this website.
How are support coverage and escalation agreed?
Evaluation starts in a real environment and uses the published documentation. Named owners agree deployment, environment access, acceptance criteria and handoff. Production support responsibilities and escalation are agreed as part of the delivery plan.
Which customer evidence is public?
The approved public customer evidence is the Quadris VMware-to-CloudStack migration project, published on the customer stories pages.
What should we bring to a supplier or procurement review?
Use the published company identity, architecture and compatibility evidence, documented security controls, current assurance status, support-scope boundary, licensing route, privacy and legal terms, and approved customer and product evidence.
What is the next evaluation step?
Choose the smallest proof step that answers the buying question: a Cloud Service Provider evaluation, an Infrastructure Team evaluation, partner opportunity qualification, an Essentials evaluation, or an architecture session.