Routing & configuration review

Tell us what you need, then choose the right setup and contact route

Planning to rent a Cloud Mac? Tell us about your workload, concurrency, storage needs, target region, and start date. For connection, billing, or node issues on an existing order, sign in to the console and submit a ticket first so the request is linked directly to the relevant service record.

Before you order
Send a structured email
Existing orders
Console-linked tickets
Support email
support@sdkmac.com
REQUEST ROUTING

Request details and next steps

Two contact routes
01

Before you order

Share your use case, region, rental period, and expected start date for an initial assessment.

Email
02

Configuration review

Include your Xcode version, concurrent workload, memory pressure, and storage requirements.

Email
03

Existing order support

Order, node connection, and billing issues should include the relevant node record from the console.

Ticket
04

Volume & partnerships

Tell us your node count, regional distribution, rollout pace, and team collaboration requirements.

Email
Email: first reply within 1 business day Tickets: follow-up against the order record
Structured consultation email

Capture the details that shape your setup in one go

This form does not submit data to a website backend. When you finish, it creates an email on your device addressed to support@sdkmac.com for you to review and send from your system mail app.

CONSULTATION / 01

Request brief

Review before sending
Give us the name or team role you would like us to use in our reply.
We will use this for configuration guidance and follow-up.
This helps us assess account collaboration and node count, not pricing.
If you have several workloads, note their priority in the additional details.
Choose nodes based on your team's location, dependent services, and real-world connection tests.
Choose the closest option for now; we can discuss the actual workload duration.
Do not include passwords, access keys, or unredacted project data.
Existing customer ticket
EMAIL CHECKLIST

When email is the right choice

  • Compare SDKMac M4 and SDKMac M4 Pro
  • Plan multiple nodes and team rollout order
  • Assess tooling and storage before migration
  • Discuss multi-node or business partnerships
Send an email
ORDER SUPPORT

When to submit a ticket

  • Verify order status or billing records
  • Link a node connection issue to the instance
  • Resolve configuration, region, or storage discrepancies
  • Submit redacted logs and reproduction steps
Open the console
Define the workload

Five types of information shape our recommendation

“I need a remote Mac” is not enough on its own. The details below help the team assess memory, storage, rental period, and node selection with fewer follow-up questions.

01

Xcode & macOS

Share the target Xcode version, minimum OS requirement, whether multiple versions must be validated in parallel, and whether your dependencies are confirmed to support Apple Silicon.

02

Concurrent workloads

Tell us how many builds, tests, or Runners run at the same time, distinguishing normal concurrency from release peaks rather than sizing around a single job.

03

Storage footprint

Estimate the space needed for repositories, dependency caches, build artifacts, models, or media separately, and note whether temporary files are cleaned up regularly.

04

Remote access

Tell us whether your team plans to use the macOS graphical interface or SSH, whether access comes from fixed locations, and whether people need to share access by time slot.

05

Expected start date

Include when you want to begin validation, your migration preparation window, and the first milestone. Actual availability is determined by the console in real time.

Four orderable regions

Choose a region based on dependencies and tested connectivity

The current catalog includes Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Both configurations are available in all four regions, with listed combinations generally in stock; final availability is shown in real time in the console.

If your team spans multiple locations, include the developers' locations, code repositories, and dependent service locations in your consultation email. We will not substitute unverified fixed latency figures for your own connection tests.

SG

Singapore

Well suited to Southeast Asian collaboration, regional testing, and continuous builds.

In stock
JP

Japan (Tokyo)

Well suited to Japan-market validation, Japanese environment testing, and regional collaboration.

In stock
KR

South Korea (Seoul)

Well suited to Korea-market testing, local collaboration, and automated builds.

In stock
HK

Hong Kong

Well suited to cross-region development, remote work, and continuous integration.

In stock
Two configuration options

Start by narrowing the range based on memory and concurrency

Both options are Cloud Mac dedicated physical machines rather than virtual machines. Focus first on sustained memory use, concurrent jobs, and local storage pressure—not just the duration of a single task.

LIGHT TO STANDARD

SDKMac M4

Light workload starting point

M4 · 16GB · 256GB SSD

  • Everyday Xcode development and basic version validation
  • Automated builds with low to moderate concurrency
  • Projects with manageable dependency caches and artifacts
  • Remote work for solo developers or small teams
$19.3 per day
Rent SDKMac M4
HIGH MEMORY

SDKMac M4 Pro

High-memory workloads

M4 Pro · 64GB · 2TB SSD

  • High-concurrency builds, tests, and multi-repository Runners
  • Large media workloads and longer batch jobs
  • Model inference and AI experiments with compatibility confirmed
  • Projects that need a larger local cache and workspace
$60.4 per day
Rent SDKMac M4 Pro

If concurrency, cache growth, or media volume is still unclear, record one representative workload and note its peak memory, disk changes, and runtime before adding the results to your consultation email. For pricing across all four rental periods, see the rental plans.

Existing customer support

Take order issues to the console instead of sending an unlinked description

Console tickets can be linked to order and node records, making them the right channel for connection issues, configuration checks, billing questions, and order changes. Include the order ID, node region, time of occurrence, reproduction steps, redacted logs, and expected result.

SUPPORT TICKET FIELDS Check before submitting
Order ID
Links the service record
Node region
Singapore, Tokyo, Seoul, or Hong Kong
Time of issue
Include the time zone and duration
Reproduction steps
Describe the actual sequence of actions
Redacted logs
Remove passwords, keys, and project secrets
Expected result
Explain what the normal state should be
Payment & settlement

Confirm payment methods and currency before creating an order

01

USDT-TRC20

Orders are priced in USD. The available payment gateway is shown in the console.

02

Visa / Mastercard / Amex

Card payments are processed by Stripe. The available payment gateway is shown in the console.

USD

USD settlement

Plans, add-ons, and order records are all settled in USD.

Information use and sending

Submit only what we need to respond

The name, work email, team size, use case, region, rental period, and additional details in this form are used only to respond to this request. Do not include passwords, access keys, unredacted logs, or unnecessary project data in an email or ticket.

After the email is generated, you can still review, edit, or cancel it in your system mail app. For details about information handling, retention, and requests, read the data privacy policy.

Planning to rent? Start with the workload and region

For a pre-order assessment, send a structured email. For connection, billing, or node issues on an existing order, submit a ticket through the console.