Security by Design
Controls are designed into the target architecture from the first landing-zone decision — not added after the fact.
Security, resilience, and operational transparency designed into every engagement.
Controls are designed into the target architecture from the first landing-zone decision — not added after the fact.
Every identity, workload, and engineer receives the minimum access required, scoped and reviewed. Nothing is trusted by default.
Multiple independent layers — network, identity, encryption, and validation — so no single control is a single point of failure.
Disaster recovery is drilled live before handover; cutovers are rehearsed, measured, and instantly reversible.
Our own services run on established cloud providers, and every client migration inherits the same disciplined controls. The providers that process data on our behalf are listed on our Subprocessors page.
Hosting, global edge delivery, and application compute and storage for our website and internal console, with TLS termination and DDoS mitigation in front of public services.
Amazon SES delivers our transactional email. AWS is not used for VoltricEdge application compute or application data storage.
Data at rest is encrypted using industry-standard algorithms, with keys managed under scoped access.
All traffic to and between services is protected in transit with TLS; plaintext channels are not used for sensitive data.
Systems maintain security and audit logs to support operational monitoring, access accountability, and incident investigation.
Regular, encrypted backups paired with rehearsed recovery procedures, so restores are demonstrated rather than assumed.
Protection follows the data through its whole lifecycle — from the network edge to secure deletion.
TLS protects data moving between clients, services, and cloud providers.
Stored data is encrypted with industry-standard algorithms and scoped key access.
Least-privilege access with MFA required for administrative and privileged operations.
Information is kept only as long as an engagement or applicable law requires.
When data is no longer needed it is securely deleted or irreversibly anonymized.
If you are a security researcher and believe you have found a vulnerability in our systems, we want to hear from you.
[email protected]Email [email protected] with a clear description, affected component, and reproduction steps.
We appreciate coordinated disclosure. Please give us reasonable time to investigate and remediate before any public discussion.
Testing that degrades service, accesses other people's data, or destroys information. Act in good faith and stay within scope.
The disciplines behind every engagement — the same controls we apply to our own estate.
Access is granted under least privilege and reviewed as engagements change. Multi-factor authentication is required for administrative and privileged operations.
Changes are planned, peer-reviewed, and reversible. Nothing reaches a production estate without a documented path forward and a path back.
Systems maintain security and audit logs to support operational monitoring, access accountability, and incident investigation, so cutovers are measured rather than guessed.
Backups are encrypted and access-controlled — and restores are exercised. A backup is only counted once it has been proven to recover.
Detection, escalation, and communication follow a defined path, so the response to an issue is rehearsed rather than improvised.
Disaster recovery is designed into the architecture and drilled live before handover, with recovery objectives demonstrated on record.
Our website, internal console, and application data run on Cloudflare, including assessment submissions stored in Cloudflare D1. Amazon Web Services is used only for transactional email delivery through Amazon SES. Migration work itself is performed inside your own cloud accounts and chosen regions — we do not take custody of your production data beyond what a given engagement requires. The providers that process data on our behalf are listed on our Subprocessors page.
Backups are encrypted and access-controlled under least privilege. Recovery is rehearsed as part of every migration, so restores are demonstrated before handover rather than assumed.
Data is encrypted in transit with TLS and at rest with industry-standard algorithms such as AES-256. Encryption keys are managed with scoped, least-privilege access.
Email [email protected] with a description and reproduction steps. We appreciate coordinated disclosure and will acknowledge legitimate reports.
Yes. MFA is required for administrative and privileged access wherever it is supported.
Secrets and credentials are held in a managed secrets store — never in plaintext or source control. Passwords are hashed where applicable, and access is scoped by least privilege.
We do not claim any certification we do not hold. What we can show you is how we operate: least privilege, defense in depth, encryption in transit and at rest, monitoring and logging, validated backups, and rehearsed recovery — set out in our Operational Practices above.
Migration work is carried out by the professionals who planned it, so access to your environment stays with a known, named group. There is no hand-off to a junior delivery team.
Start with a ten-working-day assessment — inventory, TCO comparison, and a disaster recovery gap analysis.