# Volume or Disk level Encryption | Cycle.io

Canonical URL: https://cycle.io/community/threads/69a093035caa8c2b9b2b72a4/volume-or-disk-level-encryption

## Volume or Disk level Encryption

[feature-request](https://cycle.io/community/categories/feature-request)

Hi Cycle team 👋

We’d love to see support for encryption at rest — either at the server disk level or at the individual volume level.

For teams deploying workloads in third-party virtualized environments, this is becoming a pretty standard requirement.

⸻

Why We’re Asking

When running in a virtual provider environment, we don’t physically control the underlying hardware. Even though TLS handles encryption in transit, we still need guarantees around data stored on disk.

For many companies (especially those dealing with customer or regulated data), encryption at rest isn’t optional — it’s table stakes for production.

This impacts things like: • Enterprise security reviews • SOC 2 / ISO 27001 compliance • GDPR / HIPAA workloads • Internal security policies • Risk mitigation around snapshots / host access

Without it, some workloads just can’t move onto the platform.

⸻

What Would Help

Any of the following would be great:

1️⃣ Host-Level Disk Encryption • All server disks encrypted by default • Transparent to containers • Configurable per environment if needed

2️⃣ Volume-Level Encryption • Encryption on specific persistent volumes • Visible status in the UI and API • Clear documentation on how it’s implemented

3️⃣ Key Management Options (Stretch Goal) • Bring Your Own Key (BYOK) support • Key rotation visibility

-   Christopher Aubuchon...
    
    Hey Jeff, sorry for the delay on update here - this one slipped through the cracks on me.
    
    Definitely looking into this and it is added to the tracker. Will update you, hopefully soon, on progress.
    

#### Join the conversation

Sign in with your Cycle account to reply to this thread.

Sign in

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
