ENGINEERING CONTACT

Give us the full environment details so Engineering can start troubleshooting

Confirm your configuration and location before ordering. For issues, include your order number and reproduction steps. Email pre-sales and partnership requests; submit existing-order, connection, and billing issues through the console.

Rent a Cloud Mac now Log in to the console to submit a ticket
Pre-sales & partnerships
First replies are usually sent within 1 business day
Existing orders
Tickets are usually triaged within 4 business hours
CONTACT INTAKE

Issue intake board

Two ways to contact us
A

Pre-purchase & migration assessment

Send your configuration, term, location, runner count, and data volume.

Support email
B

Connection, delivery & order issues

Submit a ticket from the console to automatically link your account and order context.

Console
C

USD billing review

Provide the term, location, add-ons, and payment record identifier. Do not send sensitive credentials.

Console
Choose an issue type first

Four request types, two contact paths

Email is best for configuration discussions and partnerships before ordering; console tickets are best for issues tied to an order, location, or handling status.

Before ordering

Explain your workflow first

Share your team size, Xcode or inference workloads, concurrency, expected rental term, and main operator location. We will recommend clear limits across our three available configurations.

Write a pre-sales email
While using the service

Include order context with your ticket

For delivery, remote connection, SSH, macOS sessions, Xcode, or runner issues, submit a console ticket with your order number, location, and reproduction steps.

Log in to the console
Billing

Review by term, location, and add-ons

State the order term, selected location, storage expansion, or Thunderbolt 5 parallel connection count, and include the payment record identifier. Do not submit a full card number or payment key.

Submit a billing ticket
Partnerships

Reduce back-and-forth with one structured email

State your partnership goal, expected scale, technical dependencies, target timeline, and what you need OVPS to assess. Use the support email for all business and technical partnerships.

Send a partnership email
Pre-sales inquiry

Six inputs generate a ready-to-send request summary

The form organizes email content in your browser only and does not submit it to the website. Clicking the button opens your system email client with support@officevps.com as the recipient.

Enter the number of people who will actually use the Cloud Mac.
Enter the number of builds, runners, or inference tasks running at the same time.
Primary use
Preferred configuration
Expected rental term
Target location
Do not submit passwords, private keys, recovery credentials, or complete payment details.

Migration assessment

Break your current environment into verifiable migration inputs

Migration advice depends on version relationships, runner count, data volume, and cutover timing. Saying only “migrate the development environment” is not enough to assess configuration, term, and preparation.

ASSESSMENT FIELDS Four required information groups
01

Xcode and macOS environment

List current versions, minimum project requirements, dependency management, and whether parallel multi-version validation is needed.

02

Runner count and concurrency

Separate total registered runners, simultaneous tasks, build duration, and cache reuse.

03

Data volume and transfer path

Estimate the size of code, dependency caches, build artifacts, and test data, and explain where the data will be migrated from.

04

Cutover date and rollback conditions

Give the target date, permitted validation period, acceptance criteria, and the legacy environment that must be retained if issues arise.

Target cutover date

Location advice

Start near your main operators, then consider the repository and artifact recipients

Cross-border performance depends on local networks, remote protocols, testing hours, and routing. Fixed latency figures cannot replace testing from your actual work network.

Team fit and selection guide for six OVPS Cloud Mac locations
Location Priority team locations Common workflows What to validate Order
SingaporeAvailable in catalog Southeast Asian and cross-region APAC teams Remote development, regional CI, artifact aggregation Test remote desktop and SSH from the main office networks Preselect location
Japan (Tokyo)Available in catalog Japanese and Northeast Asian development teams Xcode development, automated testing, daily remote operations Compare connection performance during work hours and overnight batch processing Preselect location
South Korea (Seoul)Available in catalog Teams in South Korea and nearby regions Continuous builds, mobile app testing, remote desktop Record the local carrier, testing hours, and remote protocol Preselect location
Hong KongAvailable in catalog South China and cross-border collaboration teams Code maintenance, build distribution, regional collaboration Test remote desktop interaction and large-file transfers separately Preselect location
US EastAvailable in catalog Eastern North American and European collaboration teams North American repository builds, overnight tasks, artifact return Check repository location and the route to primary maintainers Preselect location
US WestAvailable in catalog Western North American and trans-Pacific teams Continuous integration, AI inference, long-running batch processing Compare the locations of operators, code repositories, and result recipients Preselect location
Order support

For existing orders, start in the console for the fastest support

Console tickets retain the handling status and let support verify order, configuration, and location details within the authorized scope. Public email is not suitable for sensitive access information.

Required ticket details

Start with the minimum information needed to locate the order

Order number
Copy the complete number shown in the console; do not substitute a host nickname.
Location and model
State the target location and whether it is Office M4 Start, Office M4 Build, or Office M4 Pro Lab.
Time of occurrence
Include the local date, time, and time zone so connection and session log summaries can be matched.
Reproduction steps
Start from the normal state, document each step until the error appears, and note whether it reproduces every time.
Checks already performed
State whether you checked the local network, ports, SSH key permissions, remote session, and disk space.
Log in to the console and create a ticket View the troubleshooting path first

Do not send these in public forms

Passwords, private keys, temporary credentials, recovery credentials, full card numbers, and payment keys must not appear in public email bodies or screenshots.

Initial triage time

Console tickets are usually triaged within 4 business hours. If more information is needed, the status will be updated in the same ticket.

Billing inquiries

Review only the term, location, and add-ons on USD orders

OVPS bills exclusively in US dollars (USD). Payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); the console determines which gateway is currently available.

01 · Term

Check the day, week, month, or quarter first

State the rental term selected for the order and confirm the corresponding model price on the plans page. Do not compare amounts from different terms directly.

02 · Location

Confirm the target location on the bill

Provide the actual order location: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, or US West.

03 · Add-ons

List storage and parallel connection counts separately

Check +1TB SSD, +2TB SSD, or the Thunderbolt 5 parallel connection count instead of providing only a total.

04 · Record identifier

Provide a searchable identifier, not sensitive data

Include the order number and payment record identifier from the console. Do not submit a full card number or a USDT-TRC20 private key.

Need an existing order reviewed?

Log in to the console and create a billing ticket under the relevant order so support can review the term, location, and add-ons in the same context.

Create a billing ticket
Check before submitting

Let Engineering start with reproduction, not questions

An actionable issue report should include the time, steps, evidence, and expected result. Redact sensitive fields in screenshots while preserving the error context.

  1. 01

    Time and time zone

    Record the date, time, and time zone when the issue first appeared and was most recently reproduced, and whether it is ongoing.

  2. 02

    Reproduction steps from a normal state

    List commands, client settings, or interface actions in order, and identify where the result differed from expectations.

  3. 03

    Redacted screenshots or error text

    Keep error codes, context, and the full window scope visible; redact passwords, private keys, recovery credentials, and payment-sensitive information.

  4. 04

    Expected result and business impact

    Explain the correct result, which tasks are affected, and whether a workable alternative exists.

  5. 05

    Troubleshooting already performed

    List checks already completed for the network, ports, key permissions, session status, disk space, Xcode version, and runner status.

READY TO CONTINUE

No order? Email us. Existing order? Submit a ticket directly.

Contact support@officevps.com for pre-sales and partnerships; log in to the console for delivery, connection, billing, and active-environment issues. To rent a Cloud Mac, open the configuration flow and choose from three models and six locations.

Rent a Cloud Mac now Log in to the console to submit a ticket