Procurement inquiries
Use this to confirm the model, term, additional storage, payment method, and one of six available regions. We’ll identify configurations ready for direct ordering and any budget or concurrency details still required.
Start with the workload, then choose a node
Describe your procurement requirements and build constraints, and we’ll route your request to the right team.
OakVM provides dedicated Apple Silicon physical nodes—not virtual machines. For new projects, discuss configuration, migration, and region by email. For existing orders or running nodes, sign in to the console and submit a ticket so we can link the request to its task ID and support history.
Email inquiries
We aim to confirm receipt within 1 business day and explain what information is needed next.
Console tickets
Best for order and node issues; priority and progress follow the ticket acknowledgment.
CONTACT / ROUTING
Two official channels
Build migration
Use this to move a local Mac, office build machine, or existing runner to the cloud. We’ll outline the migration order for Xcode, dependency caches, signing assets, and job isolation.
Technical collaboration
Use this to evaluate self-hosted runners, remote graphical interfaces, build artifact archiving, or multi-node scheduling. We’ll first define the service boundaries, then list the validation steps.
Do not submit passwords, private keys, access tokens, or complete signing assets through public pages.
support@oakvm.com
Request dossier
Generate a ready-to-send inquiry email
The form does not submit data to the website backend. After you click the button, the page organizes the subject and body locally and opens your system email app; you can review and edit everything before sending.
Email is best for initial assessment
Before placing an order, describe your team size, target systems, concurrency, term, and region by email. We’ll first confirm whether the two available configurations cover your needs, then identify any build data still required.
- Recipient
- support@oakvm.com
- Initial response target
- Within 1 business day
Tickets keep existing resources connected
If you already have an order or node, submit a ticket through the console. Tickets can be linked to your account, task IDs, and support history, making them better than regular email for access issues, order status, and node operation problems.
- Include the task ID and time of occurrence
- State the node region and reproduction steps
- Remove tokens, identity information from paths, and signing assets from logs first
Regional guidance
All six nodes are available for consultation; choose based on your collaboration path
OakVM M4 and OakVM M4 Pro are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West. Standard catalog combinations are generally orderable; live availability is confirmed by the console.
Singapore
Ideal for Southeast Asia collaboration and teams that trigger most builds during Asian working hours.
- Key consultation points
- Team network paths, code source location, remote display requirements
- Catalog models
- OakVM M4, OakVM M4 Pro
Japan (Tokyo)
Ideal for teams in Japan and nearby markets handling daily builds, graphical workflows, and release handoffs.
- Key consultation points
- Primary operator locations, build trigger windows, artifact download paths
- Catalog models
- OakVM M4, OakVM M4 Pro
South Korea (Seoul)
Ideal for teams in Korea and Northeast Asia connecting runners, running automated builds, and performing remote acceptance testing.
- Key consultation points
- CI platform, runner labels, build cache size
- Catalog models
- OakVM M4, OakVM M4 Pro
Hong Kong
Ideal for pipelines shared by teams in South China and Southeast Asia, with evaluation based on each team’s actual network path.
- Key consultation points
- Cross-region team distribution, repository access, log and artifact handoffs
- Catalog models
- OakVM M4, OakVM M4 Pro
US East
Ideal for Eastern North American working hours and teams coordinating release workflows with colleagues in Western Europe.
- Key consultation points
- Collaboration time zones, code source location, overnight job handoffs
- Catalog models
- OakVM M4, OakVM M4 Pro
US West
Ideal for West Coast North American teams running iOS pipelines, test jobs, and Apple Silicon experiments.
- Key consultation points
- Peak concurrency, frequency of remote operations, additional storage needs
- Catalog models
- OakVM M4, OakVM M4 Pro
Don’t choose by city name alone
Also tell us where the primary operators, code repository, CI trigger, and artifact recipient are located. Remote display and automated jobs have different network sensitivities, so describe them separately.
Region is not a performance guarantee
Actual experience depends on your local ISP, routing, project dependencies, cache hit rate, and workload. Define a reproducible build baseline before comparing regions.
Build context
Five data points determine whether our reply can map directly to a configuration
“We need a faster Mac” is not enough to select a model. Break down the toolchain, job structure, and peak workload so we can distinguish compute, memory, storage, and network issues.
-
01
Xcode and command-line tools
State your current Xcode major version, whether multiple versions must coexist, any additional SDK dependencies, and whether command-line and graphical builds behave the same.
-
02
Project and dependency types
Specify whether the project is native, React Native, Flutter, Unity, or another type, and list dependency restoration steps for CocoaPods, Swift Package Manager, and similar tools.
-
03
Average build time
Record cold-cache and warm-cache times separately, and specify whether timing covers compilation, archiving, export, or the full release workflow. This avoids comparing different scopes.
-
04
Peak concurrent jobs
State how many pipelines run simultaneously, whether jobs may queue, and whether each job also starts simulators, tests, or additional packaging processes.
-
05
Runner and isolation model
State whether you use a self-hosted runner, your current label rules, how work directories are cleaned, and whether different projects need separate dedicated physical nodes.
Reproducible baseline
Recommended acceptance criteria
- Same commit, dependency lockfile, and build command
- Record cold-cache and warm-cache results separately
- Record time spent archiving, exporting, and uploading
- Keep runner labels and job priorities consistent when testing multiple nodes
Procurement and billing
Quotes are based only on catalog configuration, rental term, and add-ons
All amounts are displayed and billed in US dollars (USD). Responses break down the selected model, daily/weekly/monthly/quarterly term, region, and add-ons using currently listed options only.
What we need to quote
- OakVM M4 or OakVM M4 Pro
- Daily, weekly, monthly, or quarterly rental
- One of the six catalog regions
- Whether to add a 1TB SSD, 2TB SSD, or Thunderbolt 5 interconnect
Supported payment methods
Only the following two payment paths are supported; the available gateway is confirmed by the console:
- USDT-TRC20
- Visa / Mastercard / Amex (via Stripe)
Before confirming an order, we’ll show the selected configuration, term, add-ons, and amount due. Do not send payment credentials by email.
| What you provide | What we verify | Specific outcome in our reply |
|---|---|---|
| Project type, peak memory use, build cache size | Specification boundaries of OakVM M4 and OakVM M4 Pro | Recommended model and risks to validate first |
| Job frequency, expected term, peak concurrency | Catalog pricing and node counts for daily/weekly/monthly/quarterly terms | Options listed under the established pricing model; no custom discount pricing |
| Primary operators, code source, trigger, and artifact recipient | Singapore, Tokyo, Seoul, Hong Kong, US East, US West | Regional recommendation and network paths to validate |
| Storage growth, artifact retention, and multi-node interconnect requirements | 1TB SSD, 2TB SSD, and Thunderbolt 5 interconnect add-ons | Whether an add-on is necessary and its billing cycle |
Existing order or node
Don’t route operational issues through procurement
Order status, node access, connection errors, failed jobs, and billing records require account context. Sign in to the console and submit a ticket for the relevant order or node, including the time, task ID, region, and redacted logs.
TICKET INPUT
Redact before submitting
- Task ID
- Use it to locate build or operation records; don’t write only “it failed just now.”
- Time of occurrence
- Include the time zone and approximate time range to align the logs.
- Node region
- State the region selected for the current order; don’t substitute your team’s office location.
- Reproduction steps
- List the sequence from trigger to unexpected result and include the expected result.
- Redacted logs
- Remove tokens, private keys, the local part of email addresses, repository credentials, and signing content.
Self-check before contacting us
Check the public documentation first; shorter emails get more precise answers
If the issue can be resolved through specifications, connection steps, or the diagnostic sequence, you don’t need to wait for a reply. If collaboration is still needed, include your self-check results in the email or ticket.
CONFIG
Configuration and workload comparison
Compare the 16GB / 256GB and 64GB / 2TB configurations first to determine whether your memory, cache, and concurrency needs call for M4 Pro.
Open configuration comparison CONNECTFirst connection guide
Check credential delivery, SSH, graphical access, the initial password change, and time zone settings to distinguish configuration issues from local network issues.
Open the operations guide SIGNINGSigning asset management
Verify the import, rotation, permission isolation, and cleanup of certificates, private keys, and provisioning profiles. Never transmit complete sensitive content during an inquiry.
View security steps DISPLAYRemote display optimization
Check resolution, color, frame rate, network jitter, and background tasks layer by layer before deciding whether to change regions or adjust your workflow.
View troubleshooting sequenceOnce your requirements are clear, choose the right channel.
Send new procurement and migration requests to the support email; sign in to the console for existing order and node issues. OakVM provides dedicated physical machines, not virtual machines, and all billing is in US dollars.