Zones
GenomeDK is divided into zones. The open zone resembles traditional high-performance computing systems where data can be moved freely in and out of the system.
For projects with additional security or legal requirements, GenomeDK provides closed zones. A closed zone provides additional measures to protect against data leaks and adds increased control over data leaving the zone.
Open or closed zone?
Both zone types use the same GenomeDK platform. The open zone is the default; closed zones add isolation and data controls for projects with additional security or legal requirements.
| Feature | Open zone | Closed zone |
|---|---|---|
| Pay per usage, no pre-allocation or reservation required | ✓ | ✓ |
| Project folders to control access to data | ✓ | ✓ |
| Network isolation between zones | ✓ | ✓ |
| Virtual desktop access | ✓ | ✓ |
| Ad-hoc usage reporting and project quotas | ✓ | ✓ |
| Direct SSH access | ✓ | — |
| Free data movement in and out | ✓ | — |
| Copy and paste to or from the local computer | ✓ | — |
| Owner-approved and logged data exports | — | ✓ |
| Owner-managed zone access | — | ✓ |
| Owner-configurable Internet restrictions | — | ✓ |
A closed zone is not tied to a single project. One or more project folders belong to the zone, so users in a zone can still organize and share their data via project folders inside the zone.
Users will need a separate account/user for each closed zone they need access to.
If you think that you need a closed zone for your projects, feel free to get in touch.