Clarify with PortvMind Cloud
Infrastructure and control-plane scope, support channels, service levels and provider access conditions.
Data Sovereignty
Have a say in your data.
Plan your cloud knowing where data resides, who can access it and how it can be moved.
Explore control areasA cloud decision beyond location.
Evaluate data sovereignty through access, operations and exit terms, as well as hosting location.
Data residencyEvaluate primary data, backups and operational records separately.
- Where will application data and backup copies be stored?
- Where will logs, account information and support records be processed?
- Which data will external services receive, and for how long?
Request before deciding
Service-specific residency scope and a data-flow inventory.
Infrastructure and security approachAccess and key managementDefine who can access data, and under which conditions, from the outset.
- What are the permission boundaries for customer and provider administrators?
- How will access be approved, logged and revoked?
- Which layers will be encrypted, and who will create and manage the keys?
Request before deciding
A permission matrix, access logging policy and service-specific encryption scope.
API access guidePortability and exitPlan how to take data out as carefully as how to move it in.
- Which formats will be available to export data and configurations?
- Which compatibility and restore tests will be run in the target environment?
- What are the transfer time, egress cost and deletion schedule for remaining copies?
Request before deciding
Service-specific export methods, test results and retention/deletion terms.
Object Storage usage guideContract and operationsRead technical controls alongside service scope and responsibilities.
- Who is the contracting party, which subcontractors are involved and what are the data processing terms?
- Which terms govern incident notification, support and service levels?
- Who will carry out backup and restore tests?
Request before deciding
The service contract, data processing terms, SLA and responsibility matrix.
Support and service termsThis framework covers data residency, access, portability and the contract.
Base your decision on documents.
Review the published guides. Complete workload-specific scope and terms through your proposal and contract.
Infrastructure and security
Control layers and the shared responsibility approach.
Read moreSupport
Channels, routing and contract-specific service terms.
Read moreTechnical documentation
Service usage, API access and configuration guides.
Read morePrivacy and personal data
Personal data processing information for this website; not a replacement for the service contract.
Read moreCertifications
Certificate sourceExplore the certificate list
ISO 37001:2016Anti-bribery management
TS EN ISO/IEC 27001:2022Information security management
ISO 22301:2019Business continuity management
ISO 9001:2015Quality management
ISO 45001:2018Occupational health and safety management
ISO 27701:2019Privacy information management
ISO 27017:2015Cloud service security controls
ISO 20000-1:2018IT service management
ISO 10002:2018Customer satisfaction management
Plan your exit from the start.
Test portability in the target environment. APIs or open source alone do not guarantee a trouble-free migration.
Inventory the workload
List data, configurations, dependencies and retention requirements.
Test the transfer
Export sample data; check integrity and functionality in the target environment.
Plan the cutover
Plan timing, transfer costs, downtime and rollback conditions.
Complete the closure
Revoke access and apply the deletion terms for primary data and backups.
The flow covers inventory, testing, cutover and closure.
Let us clarify your requirements.
Share your data types, access requirements and migration goals. Start the conversation with your workload scope.
Plan an architecture consultation