Include all essential details at once

Contact the team responsible for Cloud Mac delivery

Email us for presales selection and migration assessments. For existing orders, node issues, connectivity failures, or billing checks, sign in to the console to submit a ticket and include your order ID.

Rent a Cloud Mac now Sign in to submit a ticket
Email:support@opsvm.com Email target response:Within 1 business day Ticket target response:First review within 4 hours
OPSVM / REQUEST ROUTING Issue routing guide
Two contact channels
No order yet

Discuss plan comparisons, node selection, toolchain compatibility, and migration scope by support email.

Existing order

For node status, connectivity, billing, and delivery issues, create a ticket in the console.

Run a self-check first

Include reproduction steps and redacted logs to usually avoid one round of follow-up.

Email Console ticket USD / 6 REGIONS
Identify the right team first

Choose the right channel and prepare actionable details

Questions without an order ID are best sent by email. Issues tied to a specific physical node or transaction record should be submitted through a console ticket so support can verify the order context.

Sales & migration

Send a structured email

Use this for comparing OpsVM M4 Core, OpsVM M4 Plus, and OpsVM M4 Pro, confirming access options across six nodes, or assessing the scope of code, dependencies, CI jobs, and data migration.

  • State your team location and target node instead of guessing about latency.
  • Specify peak concurrent builds, RAM, SSD, and rental period requirements.
  • The target email response time is within 1 business day.
Fill out the sales email
Orders & nodes

Sign in to submit a ticket

Use this for node connection failures, credential issues, graphical sessions, build failures, and billing checks. Tickets retain order associations, avoiding repeated host ownership checks by email.

  • Create a ticket from the Support area in the console and select the related order.
  • Include the time of occurrence, node region, reproduction steps, and redacted logs.
  • The target ticket response is a first review within 4 hours.
Sign in and submit a ticket
REQ / PRESALES

Describe your workload as configuration requirements

Presales selection

Don’t just say, “I need a faster Mac.” Explain the actual use case, how many tasks run concurrently, the target region, and the data volume so the team can assess whether 16GB, 24GB, or 64GB RAM is appropriate.

Best for email No order has been created yet; you’re comparing configurations and nodes.
Recommended details Peak concurrency, build time per run, additional SSD capacity, and expected rental term.
Available regions Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, US West.
REQ / PRESALES

Generate a presales email

Email
View the three plans first

REQ / MIGRATION

Describe your current environment before discussing the migration path

Migration assessment

Migration assessments focus on reproducibility, not just file size. List your current development system, Xcode version, dependency management method, CI platform, and data types to migrate.

Code & data Specify repository count, dependency caches, build artifacts, and required working directories.
Toolchain List the versions of Xcode, Swift, Fastlane, Git, and command-line dependencies.
Acceptance criteria State your targets for test builds, signing checks, artifact delivery, and CI integration.
REQ / MIGRATION

Generate a migration assessment email

Email
Read the getting started guide

REQ / INCIDENT

Make the issue reproducible step by step

Technical issues

Submit technical issues for existing orders through a console ticket whenever possible. If email is your only option, provide the order ID, node region, client operating system, exact time of occurrence, and the complete sequence of actions from normal to abnormal behavior.

Connectivity issue State whether the issue affects SSH or graphical remote access, and include the error message, port, and client version.
Build issue Include the command run, exit status, key logs, and remaining disk space.
Log requirements Remove tokens, keys, passwords, signing materials, and personally identifiable data.
REQ / INCIDENT

Generate a technical issue email

Use a ticket first
After generating the email, manually attach the selected file in your email client.
Use a console ticket instead

REQ / BILLING

Locate billing details using the order and transaction record

Billing review

Provide the billing period, USD amount, transaction time, and order ID. OpsVM supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); actual available gateways are determined by the console.

Single currency All orders are settled in USD; no conversion to other currencies is performed.
Period definitions Daily, weekly, monthly, and quarterly prices are independent and are not derived from other periods.
Where to submit For existing orders, link the transaction record through a console ticket for a more direct review.
REQ / BILLING

Generate a billing review email

USD
Sign in to review billing

Security check before submitting

Send only the minimum information needed to troubleshoot

Do not submit private keys, account passwords, recovery codes, or unredacted signing materials. If logs contain access tokens, repository URLs, user directories, internal domains, email addresses, or file paths, replace them first with non-executable placeholders.

Private keys and passwords removed
Recovery codes removed
Access tokens hidden
Signing materials redacted
Rule out common issues before submitting

Three self-service paths to complete the basics first

If the issue can be resolved directly through configuration, connection order, or toolchain versions, follow the guide first and record the result. If it remains unresolved, attach those results to your email or ticket.

Troubleshoot by category

Help Center

Check common errors by topic, including deployment, SSH, graphical remote access, file transfer, Xcode, CI/CD, and billing.

Open Help Center
First deployment

Getting started guide

Complete your first deployment in order: choose a configuration, select from six nodes, complete USD settlement, then verify credentials and the toolchain.

View deployment steps
Connection path

Remote access guide

Verify SSH first, then configure graphical remote sessions, file transfer, and network quality settings. Troubleshoot timeouts, authentication failures, and session conflicts in order.

View connection guide

Configuration ready? Create your order directly

All three Cloud Mac plans provide dedicated physical machines, not virtual machines; all six nodes operate normally 365 days a year, with real-time availability shown in the console.

Rent a Cloud Mac now Compare the three plans