Dedicated Apple Silicon

Dedicated cloud Mac,
accelerate Xcode cloud builds

Every order includes one independent Mac mini physical node. No virtual machines and no shared compute resources.

Nodes stay online continuously for builds, testing, signing and archiving, artifact publishing, AI tool validation, and remote development workflows.

iOS CI/CD macOS builds AI experiments Remote development
Node access, system environment, and rental term depend on the order configuration; actual availability is shown in real time by the console.
hexvm / physical-nodes / overview
An isometric cluster of physical nodes made up of multiple Mac mini computers
Node status 6 / 6 healthy
SG-M4-028Singapore · M4 21 ms
JP-M4P-014Japan (Tokyo) · M4 Pro 34 ms
USW-M4-047US West · M4 29 ms
Nodes and data centers6 regions
Typical delivery time≈ 4 minutes
Service target99.9%
Workload console

Orchestrate dedicated nodes around development tasks

From build commands to results, configurations, durations, commit versions, and node regions stay clear and traceable. Status colors indicate progress, success, and steps requiring attention.

Workload

Switch task types to view the corresponding pipeline interface and execution scope.

iOS release pipelineJapan (Tokyo) · JP-M4P-014

After code is committed, the self-hosted runner retrieves the job and runs dependency restoration, tests, archiving, and artifact uploads in sequence.

App / Release 8.4.1main · 8e12d9aSucceeded04:1814:32
UI Tests / iPhone 16feature/paymentsRunning02:4114:38
Archive / Releaserelease/8.4Queued--:--14:41

Nodes can connect to your existing repositories and pipelines, while repository authorization, build keys, certificate permissions, and artifact access rules remain managed by your team. Put long-running tasks in resumable sessions and save failure logs as pipeline artifacts.

View all use cases
Dedicated physical Mac

One order, one independent Mac mini

Not a shared compute instance or a virtual machine. Each node’s chip, memory, and local storage are dedicated to its order, with clear resource ownership and a system environment controlled by your development workflow.

Dedicated physical node boundariesChip, memory, storage, region, and add-ons are determined by the order confirmation page. Remove code, credentials, and build artifacts before releasing a node.

Clear access boundaries

Access nodes with VNC and SSH. Update temporary credentials after the first connection, prefer SSH keys, and limit permissions by repository, pipeline, and team responsibility.

  • Isolate node connection details by order
  • Revoke keys promptly when team members change
  • Sanitize sensitive logs before sharing

More consistent performance

Fixed physical nodes reduce fluctuations caused by contention for shared resources, making them suitable for continuous builds, test execution, signing and archiving, and long-running engineering tasks.

  • Fixed chip and memory specifications
  • Build caches stay on the local node
  • Easier comparison of build times between commits

Controlled toolchain environment

Manage Xcode, command-line tools, dependency caches, build certificates, and script versions by project to reduce environment differences between developer machines and pipelines.

  • Record Xcode and SDK baselines
  • Isolate dependency caches between projects
  • Keep reproducible build commands
Global node regions

6 regions, with every catalog combination available to order

Currently available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West. Consider your team’s location, repository entry point, and artifact upload destination when choosing a region.

SGSingaporeSoutheast Asia builds and remote accessAvailable
JPJapan (Tokyo)Northeast Asia builds and testingAvailable
KRSouth Korea (Seoul)Access for teams in South Korea and nearby regionsAvailable
HKHong KongCross-region Asia pipelinesAvailable
US-EUS EastRepositories and teams in eastern North AmericaAvailable
US-WUS WestDevelopment and releases on the US West CoastAvailable
How to choose a region

Prioritize a region close to your main operators or repository service entry point. If builds upload large artifacts, also test network performance to the target storage path.

Availability note

HexVM M4 and HexVM M4 Pro are available in all 6 regions above. Actual availability and options are shown in real time by the console.

Transparent pricing

Exactly two tiers, matched to your workload

Rent by the day, week, month, or quarter. Starting at $19.3/day —switch the term to review fixed catalog prices for both models.

Choose a rental term

HexVM M4 Pro

Parallel builds, large projects, and continuous tasks

High performance
$59.5/ day

Suitable for projects requiring more memory and local storage.

ChipM4 Pro
Memory64GB
Storage2TB
  • Large Xcode project builds
  • Parallel multitasking and continuous execution
  • Large caches and build artifacts
Order HexVM M4 Pro
USDT-TRC20 Visa / Mastercard / Amex (via Stripe) All charges settled in USD Available gateways depend on the backend response
Delivery and reliability

About 4 minutes from payment confirmation to credential delivery

Delivery has four steps: payment confirmation, node assignment, system checks, and credential delivery. Service status is tracked separately to distinguish order delivery issues from node operation issues.

Automated node delivery timeline

Each step has clear inputs, checks, and completion results.

About 4 minutes total
  1. 01Payment confirmationVerify the order amount, currency, and payment result, then proceed to node assignment.About 1 minute
  2. 02Node assignmentMatch the region, model, rental term, and add-ons in the order.About 1 minute
  3. 03System checksConfirm network, local storage, the macOS graphical interface, and command-line status.About 1 minute
  4. 04Credential deliveryProvide the node address, username, and temporary connection details through the order channel.About 1 minute
Typical total delivery time≈ 04:00

After receiving the connection details, first verify the node region and model, then update the temporary credentials. If the details do not match the order, sign in to the console, submit a ticket, and include the node ID.

Service availability dashboard

The last 90 days are shown day by day; green cells indicate a normal daily record.

Service target
99.9%
NormalIncident markers
Observation period90 days
Operating statusYear-round continuous operation
Service target99.9%

If monthly availability falls below the service target, submit the node ID, affected period, and incident record according to the service terms. Eligible orders are handled through service credits; impacts caused by force majeure or user actions are excluded.

View security and service targets
Developer workflows

Connect to your existing repositories and pipelines

Connect a dedicated Mac node as a self-hosted runner or remote development environment. Keep commands, logs, and outputs at every step to reproduce build results and locate failures.

01

Xcode build

Pull the code and locked dependency versions, then verify the project, scheme, SDK, and target architecture. Record Xcode and command-line tool versions before building.

xcodebuild build
02

Signing and archiving

Manage certificates, provisioning profiles, and keychain access with least privilege. Check signing results after archiving and never print sensitive data in ordinary logs.

xcodebuild archive
03

Test validation

Run unit and UI tests, saving result bundles, failure screenshots, and key logs. Preserve evidence needed for analysis before cleaning DerivedData.

xcodebuild test
04

Artifact release

Upload archives, test results, and verification data, then write the release status back to the pipeline. For large transfers, choose a region closer to the artifact destination.

fastlane release
Before connectionPin the Xcode baseline, configure repository permissions, and confirm the region and network path.
While runningKeep build logs, monitor disk space, and restrict access to keys and certificates.
Before releaseExport required artifacts, revoke authorizations, and delete code and sensitive credentials.
Before you order

Delivery, access, and billing

Use the information below to quickly understand service boundaries. For connection or build issues, visit the Help Center for step-by-step troubleshooting.

Is HexVM a virtual machine?

No. Each order includes one independent Mac mini physical node. The chip, memory, local storage, and region are specified on the order confirmation page. Nodes do not share compute resources with other tenants.

How soon can I connect to the node after payment?

Typical delivery takes about 4 minutes, including payment confirmation, node assignment, system checks, and credential delivery. After receiving the connection details, first verify the node ID, region, and model.

Which payment methods are supported?

Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are settled in US dollars (USD); available gateways depend on the backend API response.

How can I access the cloud Mac?

Use VNC for graphical access or SSH for command-line access. On the first connection, verify the host fingerprint, update temporary credentials, and preferably configure a dedicated SSH key.

Will the node stay online?

Nodes operate continuously throughout the valid rental term. Before expiration, confirm your renewal plan and promptly export any code, logs, and build artifacts you need to retain.

Deploy a dedicated node

Choose your dedicated Mac

Compare the two models, then choose a region, rental term, and add-ons. After purchase, view orders, nodes, and invoices and submit tickets from the console.

All charges are settled in US dollars (USD).