Pre-sales selection
No order yet? Need help choosing a configuration
Share your project type, Xcode version, expected concurrent builds, preferred node, rental term, and storage needs.
Prepare a sales email
Sales & Support
Explain the issue clearly so we can start resolving it in our next reply
Ask us about plan selection, dedicated physical nodes, CI migration, remote access, and order issues. New users can email us; existing customers should submit a console ticket so order and node details are included automatically.
- Include workload, Xcode version, concurrency, node, and term in your sales email
- Submit order and connection issues through the console so we can verify host details
- Remove keys, tokens, signing passwords, and other sensitive data from logs first
CONTACT RUN SHEET
Issue Routing Sheet
2 ways to contact us
MAIL / 01
New inquiry
Send a structured email
Ideal for plan selection, enterprise requirements, CI migration planning, and partnership inquiries. The form below can organize the subject and body automatically.
support@macvpsgo.com
TICKET / 02
Existing order
Submit a ticket in the console
Ideal for connection issues, host delivery, billing verification, and existing orders. Include your order number, node, and time of reproduction.
Open the console
Email: first human review within 1 business day
Ticket: progress and response times are shown in the console
Choose an issue type
Six issue types, each with different information to prepare
First identify the issue type, then prepare the details listed on its card. The more complete the information, the more likely the first reply can move straight to selection, verification, or troubleshooting.
Existing order
Need to verify delivery details, host status, or configuration
Submit a ticket through the console first. Include your order number, model, node, time of occurrence, and the specific details to verify.
Open the console
Technical support
Remote access, Xcode, or CI runner issue
Complete the checks on the support page first, then submit reproduction steps, the full relevant error excerpt, your network environment, and the actions already taken.
View the troubleshooting checklist
Billing clarification
Need clarification about a term, add-on, or payment record
Provide your order number, selected term, main configuration, add-ons, and the billing items to verify. Do not send complete payment credentials.
Submit a billing ticket
Enterprise solutions
Multiple physical nodes with unified CI runner standards
Tell us the machine count, team size, runner labels, cache strategy, node distribution, and any Thunderbolt 5 interconnect requirements.
Share enterprise requirements
Partnership inquiry
Discussing service delivery or technical collaboration
Include your organization name, partnership goals, expected scope, timeline, and points of contact to confirm. All inquiries are handled through the support email.
Prepare a partnership email
Pre-sales information checklist
Base configuration recommendations on real build workloads
Saying “I need a Mac” is not enough to size memory, storage, or concurrency. These six details let us make an informed recommendation between Go M4 Core, Go M4 Plus, and Go M4 Pro.
Project type
Tell us whether it involves native iOS, macOS, React Native, Flutter, automated testing, or AI inference. For multiple projects, identify the primary and secondary workloads.
Xcode version
Include the current version, whether multiple versions must coexist, and any Swift, SDK, or command-line tool requirements.
Expected concurrency
Provide the number of simultaneous build jobs, peak queue length, and whether tests, archives, or dependency installation will also run in parallel.
Required node
Choose Singapore, Tokyo, Seoul, or Hong Kong. Indicate the approximate locations of developers, code repositories, and primary users of the service.
Rental term
Choose daily, weekly, monthly, or quarterly, and tell us whether it is for a temporary release, continuous CI, capacity expansion, or long-term development environment.
Storage requirements
Estimate total usage for code, DerivedData, dependency caches, archive artifacts, and model files, and say whether you are considering an SSD add-on.
Technical issue information checklist
Submit reproducible details—not sensitive credentials
Handle connection and build failures through a console ticket whenever possible. Keep the complete error context, but remove keys, tokens, signing passwords, and private keys before pasting.
Incident record field
Recommended details
Order number
Use it to locate the associated host and service records; do not provide only the model name.
Node
Specify Singapore, Tokyo, Seoul, or Hong Kong, along with the approximate region the connection originated from.
Time of occurrence
Use the date and time with a time zone, such as “around 14:30 China Standard Time.”
Error log
Keep the necessary lines before and after the error, the command name, and exit code. Remove passwords, private keys, tokens, and signing passwords.
Network environment
Specify whether you are on an office network, home network, or another fixed egress, and whether VNC and SSH are both affected.
Steps already tried
List actions in order, such as retrying, switching networks, clearing caches, freeing disk space, or restarting the build job.
Before submitting
View the support checklist
Complete these seven quick checks first
Verify the order status, node address, account credentials, VNC client, SSH connectivity, disk space, and Xcode version.
Existing customers
Open the console to submit a ticket
Automatically link the ticket to your order context
Console tickets are best for connection issues, delivery verification, hardware problems, and billing questions. Further updates will remain in the same record.
Email run sheet
Organize the key details into an email we can act on immediately
This form does not submit data to the website. After you click the button, the page generates the email subject and body locally and opens your system email app.
Enterprise Mac solution consultation
Plan machine count, runners, and caching as one system
Enterprise requirements involve more than adding hosts. Include your team size, build queue, permission boundaries, cache lifecycle, and node distribution so we can assess dedicated node count and collaboration options.
Planning dimensions
Host count is not the only variable
- Queue
- Peak build count and waiting jobs
- Labels
- Project, environment, and Xcode version isolation
- Cache
- Dependency, DerivedData, and archive lifecycle
- Nodes
- Developer, repository, and service-user locations
Configuration boundaries
Combine across three fixed physical configurations
- Go M4 Core: M4, 16GB, 256GB
- Go M4 Plus: M4, 24GB, 512GB
- Go M4 Pro: M4 Pro, 64GB, 2TB
Two official contact options
Email for new inquiries; tickets for existing orders
Do not create multiple contact threads for the same issue. Send new requests to the support email; for existing orders, nodes, connections, or billing, sign in to the console and keep adding information to the same ticket.
support@macvpsgo.com
Ideal for pre-sales selection, enterprise solutions, CI migration, and partnership inquiries. We recommend using the structured subject and body generated by the page.
Send a support emailConsole ticket
Ideal for existing orders, connection failures, delivery verification, and billing issues. Ticket status and subsequent response times are shown in the console.
Open the consoleAlready placed an order? Link it from the console first
Review your order and host details, then submit a ticket. For urgent connection issues, use the support checklist to record the node, time, network environment, logs, and steps already tried.