Support

The right channel for your type of problem

PortvMind Cloud provides 24/7 technical support. Not every request belongs on the same channel: documentation, the community and the direct support channel serve different kinds of problem. The router below helps you pick the right one before opening a request.

Overview

How does PortvMind Cloud support work?

Support has three layers. Documentation is enough while you are performing a step-by-step operation; approach and architecture discussions run in the community forum; an operational request about a running resource goes from the console straight to the direct support channel. A 24/7 technical support channel is in place.

Support scope — which services and which service level it covers — follows the contract; the availability commitment and service credit terms are defined in the contract.

Router

What type of problem is it?

Pick the case you are in; each case leads to a single channel. The wrong channel is the most common reason a resolution takes longer than it should.

Case A

I do not know how to perform a step

Setup, S3 compatibility, Kubernetes, Terraform and Hermes Agent steps are published in the documentation. Starting here resolves the question without opening a ticket.

Case B

I want to discuss the approach

Architecture choices, release announcements and what others do with the same workload are discussed in the community forum. Release notes are published on the same channel.

Case C

Something is wrong with a running resource

Behaviour of a running resource, quota, access or configuration requests go to the direct channel. A request opened from the console carries its project and resource context.

Channels

Four channels, four uses

Each card states what the channel is for, when to use it and what to write in the request.

Documentation

Self-service

Setup, API access, Object Storage and Kubernetes steps are already published.

When: while performing a step-by-step operation. What to write: nothing — follow the relevant page.

Community forum

discuss.portvmind.com

An open channel for architecture discussions, release notes and community questions.

When: non-urgent, shareable questions. What to write: workload type, the configuration you tried and the behaviour you expected.

In-console support request

Console → Support

Operational requests about running resources are opened from the console and carry resource context.

When: unexpected behaviour on a running resource, quota or access needs. What to write: project name, resource id, time of the event and the observed error.

Contact by email

[email protected]

A direct channel for pre-sales architecture questions, scope and contract topics.

When: architecture consultation, scope and contract questions. What to write: workload, target region and timeline.

FAQ bridge

Frequently asked about support

The three entries below come from the frequently asked questions page.

How is technical support provided?

PortvMind Cloud provides 24/7 technical support. Support channels are in the console. Community and release announcements are published on discuss.portvmind.com.

Can I automate with Terraform and the API?

Yes. By creating an Application Credential through the panel, you can generate secure credentials for your Terraform and API workflows. You can manage your resources, including VKE, with Terraform using the Infrastructure as Code approach. The Project ID and Project Name needed for automation are available in the panel profile menu.

Which security and compliance standards does PortvMind Cloud hold?

Security, business-continuity and privacy certificates are issued to vMind Information Technologies. Current documents are on the vMind certificate page. KVKK and sector obligations are completed through your organisation’s own legal and security assessment.

Open the request on the right channel

Requests about running resources go through the console; scope and contract questions go through the contact channel. The commitment scope is described in the contract.