Selection, Orders & Support

Classify your request first,
then include the details we need

Planning to rent a Cloud Mac? Email us with your workload, region, and term. For existing orders, connection issues, or billing questions, sign in to the console and submit a ticket so the order context stays with your request.

Start renting a Cloud Mac Sign in to submit a ticket
Sales & security inquiries
Email support@vmoak.com
Orders & technical issues
Submit a ticket with your order number
Available catalog
2 models · 6 regions
INQUIRY / ROUTING

Inquiry routing board

Two ways to contact us
01
Model & region selection Include build frequency, concurrency, memory, and target region
Email
02
Multi-node enterprise deployment Share node count, regional distribution, and expected rollout schedule
Email
03
Order & billing status Include your order number, billing date, and issue time
Ticket
04
Remote connection issue Include the node, client environment, and redacted error details
Ticket
05
Security inquiry Describe the timeline, scope, and reproducible evidence
Email
Do not submit private keys or complete access credentials support@vmoak.com
Structured inquiry email

Include your engineering constraints in one message

This form only prepares an email subject and body in your browser; it does not submit data to the website. When complete, it opens your system email app with support@vmoak.com as the recipient.

Choose a request type
Preferred region
Planned rental term
Have an existing order? Submit a ticket

Sales inquiries

What should you email us about?

  • Compare VMOak M4 Branch and VMOak M4 Pro Canopy
  • Evaluate build frequency, concurrency, memory, and storage growth
  • Plan multiple devices, fixed CI/CD capacity, or distributed teams
  • Ask about credential practices, access boundaries, or security materials
Email support@vmoak.com
Order support

What should go through a console ticket?

  • A delivered node cannot connect or its credential status is abnormal
  • Build processes stop, or you have disk-capacity or remote-display issues
  • You need to verify an order, term, billing status, or service expiration
  • The issue must be linked to a specific order, node, and support history
Sign in to the console
Sales inquiry template

Recommendations depend on workload, not project name

“I need a development machine” is not enough to estimate memory, storage, or term. These five groups of details help us provide actionable advice across the two catalog configurations.

01

Build frequency

Describe daily or weekly build counts, duration per build, and whether workloads concentrate before releases. Short, frequent jobs and sustained usage affect term selection differently.

02

Concurrent tasks

State normal and peak concurrency, distinguishing compilation, testing, signing checks, and artifact uploads. Do not substitute team size for task count.

03

Memory requirements

List your Xcode project size, simulator count, and container or model-inference workloads. 16 GB and 64 GB support different working-set limits.

04

Storage growth

Estimate growth in repositories, DerivedData, dependency caches, and build artifacts, and explain what is periodically transferred back or cleaned up.

05

Target region

State where primary operators and code services are located, then choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West.

OUTPUT

Actionable recommendation

The reply will stay within the VMOak M4 Branch and VMOak M4 Pro Canopy catalogs and specify the recommended model, region, term, and any likely storage add-ons.

Enterprise Mac solutions

Confirm capacity and rollout before finalizing the order

Enterprise inquiries are suited to fixed CI/CD capacity, parallel builds across projects, and cross-region collaboration. Provide the required physical node count, each node’s primary role, regional distribution, and expected activation order.

The catalog remains limited to the two models currently available. Quantities, regional arrangements, and delivery timing are not commitments until confirmed in an order; available combinations are determined by the console in real time.

Send enterprise requirements
CAPACITY BRIEF Capacity details to include
Node count
Initial count, expected expansion, and whether confirmation will be phased
Task roles
Interactive development, build runners, testing, audio/video processing, or AI experiments
Regional distribution
Operator regions, code-service locations, preferred and fallback regions
Capacity profile
Continuous operating hours, peak concurrency, launch milestones, and expected term
Access methods
Network requirements for remote desktops, SSH, or automated tasks
Orders & billing

Include your order number and billing date for billing questions

When requesting order verification, include the order number, billing date, selected term, model, region, and add-ons in the console ticket. Do not submit complete card details or private wallet information.

Payment methods

Two payment options only

On-chain settlement
USDT-TRC20
Card payment
Visa / Mastercard / Amex (via Stripe)
Billing currency
US dollars (USD)
Actual gateway
Available methods returned by the backend when you place the order
Ticket fields

Start verification with the right records

  • Order number and account work email
  • Billing date and selected daily, weekly, monthly, or quarterly term
  • VMOak M4 Branch or VMOak M4 Pro Canopy
  • Region, storage, and Thunderbolt 5 expansion add-ons
  • The specific amount line or order status to verify
Submit a billing ticket
Response expectations

Priority depends on impact and information completeness

The following describes our standard handling after a request enters the queue; it is not a completion-time guarantee for unverified issues. If information is missing, we will first request additional order or environment context.

VMOak inquiry channels, first-response targets, and required information
Request type Recommended channel First-response target Minimum information
Model & region selection support@vmoak.com Confirm whether the request is complete within 1 business day Use case, concurrency, memory, storage growth, target region, and term
Multi-node enterprise deployment support@vmoak.com Confirm the capacity brief and follow-up items within 1 business day Node count, regional distribution, task roles, and expected rollout schedule
Orders & billing Console ticket Update the status after the first order-record review Order number, billing date, term, and details to verify
Active connection issue Console ticket Prioritize impact assessment and provide next checks Order number, node, time of occurrence, client environment, and redacted logs
Security issue support@vmoak.com Confirm receipt first and assess the scope of impact Timeline, reproduction conditions, affected resources, and containment steps taken
Status updates: Email inquiries are updated in the original email thread; console tickets are updated in the same ticket record. Add information to the original thread to avoid splitting one issue into multiple requests.
Pre-submission checklist

Send only the minimum information needed to investigate

Do not submit private keys, complete access credentials, identity documents, complete card details, private wallet information, or unredacted business data in email or tickets. Remove tokens, repository keys, user data, and internal addresses from logs; retain only timestamps, error types, task stages, and necessary context.

  • Use the order number to identify the service; never paste complete access credentials
  • Describe the issue with its timing and steps; do not upload an entire production dataset
  • For security issues, state the impact scope first, then provide the minimum reproducible evidence
  • To correct or delete contact records, email us with the scope of your request
Next steps

Ready to proceed? Choose your Cloud Mac

Both dedicated Apple Silicon physical nodes can be configured by day, week, month, or quarter. Before ordering, review the model, six regions, and add-on details.

Rent a Cloud Mac now View configurations and pricing