ClusterPilot Cloud – Pilot phase in preparation

Security starts with clear responsibilities.

Define access, data handling, updates and incident contacts before a pilot starts. The scope depends on the qualified configuration and written agreement.

Explore plans and costs →Request a pilot proposal →

Agree paid pilot projects individually. Scope and prices are confirmed before the start; general availability has not been announced.

Operating modelManaged Cloud

Cloud accountProvided by ClusterPilot

Cost structurePlatform + infrastructure

StatusPilot in preparation

01 / ClusterPilot Cloud

Define the service boundary in writing.

ClusterPilot is intended to manage the agreed infrastructure and cluster operations. You remain responsible for application code, your data processing and users unless agreed otherwise.

Define access permissions and contacts
Review data location and subprocessors in the proposal
No blanket compliance or certification claim

02 / ClusterPilot Cloud

Qualify backups and high availability.

Multiple nodes do not replace a tested backup. Backup scope, recovery, maintenance and availability targets must be evidenced and agreed for the configuration.

Test application and data restoration
Agree RPO, RTO and maintenance windows before the pilot
No general SLA or 24/7 support commitment

03 / ClusterPilot Cloud

Handle inquiries with minimal data.

The form requires acknowledgment of the privacy notice. Until direct delivery is configured, it prepares an email for you to send yourself. There is no automatic marketing opt-in.

Check the delivery method before sending
No payment details and no separate lead database
Send security reports by email with limited, redacted details

Cloud pilot

Let’s review your use case.

Tell us about your application, capacity and operating needs. We will assess pilot fit together and confirm scope and costs in writing before any work starts.

Inquiry privacy notice ↗

Send your use case →Read the documentation →