Accessing, ordering, or using the service means you accept these Terms
By visiting this website, creating an order, completing payment, receiving node information, or using a Cloud Mac, you confirm that you have read, understood, and agreed to be bound by these Terms. If you act for a team or other organization, you must confirm that you are authorized to accept these Terms and manage the related orders on its behalf.
If you do not agree to these Terms, stop creating orders or using the service. Plan pages, order confirmations, configuration records in the console, and specific service notices form part of the order relationship. If general information conflicts with a specific order record, the order details you finally confirmed prevail.
Confirm the model, rental period, location, storage add-ons, Thunderbolt 5 parallel connection requirements, payment method, and contact email. Do not create an order based only on browser cache, an old screenshot, or a verbal description.
The service provides a private Apple Silicon physical Mac
MacVPSGo provides private Mac mini Apple Silicon physical Mac rentals. Each valid order corresponds to dedicated resources on a physical node. The service is not a shared virtual machine and does not replace the chip, memory, or storage configuration listed in the order with virtualized resource allocations.
The service supports Xcode cloud builds, iOS CI, macOS self-hosted runner, Fastlane automation, remote development, and Mac-based inference workloads within the resource limits. You receive the right to use the device and basic connectivity for the agreed period, but do not acquire ownership and may not dismantle, move, or modify the physical facilities.
- Resource type
- Mac mini Apple Silicon physical node
- Resource allocation
- Dedicated for the order period; configuration quotas are not shared with other users
- Access method
- Connect through the graphical interface or command line using the delivery information
- Service scope
- Node delivery and basic connectivity; hardware ownership is not transferred
Three configurations and four rental periods
The current catalog includes three plans: Go M4 Core, Go M4 Plus, and Go M4 Pro. Orders can be created by the day, week, month, or quarter. Every model is available in Singapore, Tokyo, Seoul, or Hong Kong, subject to real-time availability shown in the console.
| Plan | Configuration | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|---|
| Go M4 Core | M4 / 16GB / 256GB | $20.7 | $55.8 | $103.3 | $281 |
| Go M4 Plus | M4 / 24GB / 512GB | $39.6 | $106.8 | $197.8 | $538 |
| Go M4 Pro | M4 Pro / 64GB / 2TB | $60.2 | $162.6 | $301.1 | $819 |
Additional storage and Thunderbolt 5 parallel connections are billed for the selected order period and must match the host period. After creating an order, use the primary configuration, add-ons, location, and period shown on the confirmation page. Do not combine individual prices from different periods.
All orders are billed in USD
Service prices and order totals are quoted in US dollars. The only supported payment methods are USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe. Actual gateway availability is determined by the result returned at checkout.
- Order total The total is based on the model, period, location, and selected add-ons. Check the full amount before paying.
- On-chain payment When using USDT-TRC20, verify the network, address, and amount. Transfers sent to an incompatible network or address may not be recognized automatically.
- Card payment Visa, Mastercard, and Amex payments are processed by Stripe. This site does not store full card numbers.
- Payment confirmation The console record determines the order status. Unconfirmed payment information does not constitute completed delivery.
You must ensure that the payment source is lawful and that you are authorized to use the selected payment method. For delays caused by incorrect details, an incorrect blockchain network, issuer declines, or failed payment verification, first check the console record, then submit the order number and payment evidence through a support ticket.
Connect and verify the environment promptly after receiving node details
Delivery information may include an order identifier, node address, system credentials, and connection instructions. View and manage this information through the console, restrict access appropriately, and never publish or transfer credentials to unauthorized people.
-
1
Verify the order
Check that the model, memory, storage, location, and rental period match the confirmation.
-
2
Test the connection
Use the delivery information to test the graphical interface and any required SSH connectivity. Confirm that the keyboard, network, and basic access work normally.
-
3
Check the environment
Confirm that macOS, Xcode, command-line tools, available disk space, and the dependencies required by your project meet the workload requirements.
-
4
Protect credentials
Limit team-member permissions and avoid exposing passwords, private keys, tokens, or signing passphrases in repositories, build logs, screenshots, or support tickets.
If you find a configuration or connectivity problem, stop high-risk changes and preserve the necessary logs. Submit the order number, node, time of occurrence, symptoms, and steps already taken through a console support ticket so the issue can be diagnosed from the actual records.
Users manage code, permissions, signing assets, and data
The platform is responsible for delivering the physical node and basic connectivity specified in the order. You are responsible for account settings, code, build artifacts, certificates, provisioning profiles, signing assets, access permissions, software licenses, third-party service authorization, and all actions performed on the node.
Accounts and permissions
Set appropriate access controls, grant permissions only to team members with a genuine business need, and revoke access promptly when team membership changes.
Code and sensitive information
Manage repository permissions, environment variables, private keys, tokens, and signing passphrases yourself. Do not include sensitive information in public logs or support materials.
Licensing and compliance
Ensure that installed software, dependencies, models, datasets, and build content are properly licensed and comply with applicable rules.
Backups and cleanup
Keep independent backups of important code, build artifacts, and configurations. Export required data and remove unnecessary sensitive information before the rental ends.
You are responsible for your automated tasks, runner configuration, concurrency strategy, and disk-cleanup rules. Long-running tasks should include logging, timeouts, and failure cleanup to prevent abnormal loops from consuming resources or filling storage.
Do not use a node to harm others or disrupt infrastructure
You may not directly commit, assist with, or allow a third party to commit any of the following through your order. The platform may verify activity using node logs, support records, risk signals, and actual impact.
- Unauthorized access Attempting to access an account, system, network, repository, service, or data without authorization.
- Malicious scanning and attacks Exploiting vulnerabilities, credential stuffing, denial-of-service attacks, malicious scanning, or distributing malware.
- Infrastructure disruption Interfering with nodes, networks, power, monitoring, or other users’ services; bypassing security controls; or concealing the source of an attack.
- Resource abuse Running tasks that clearly depart from the ordered purpose and continuously endanger the equipment, network, or overall service stability.
- Illegal activity Storing, processing, or distributing content that violates applicable law, or using the service to infringe intellectual property, privacy, or other lawful rights.
Security testing is permitted only against targets you clearly own or are authorized to test in writing, and must remain within controlled scope and traffic limits. You may not bypass authorization requirements by claiming development, testing, or research purposes.
Nodes operate year-round; incidents are diagnosed from actual records
All available nodes are provided with a continuous 365-day-a-year operating target. Hardware failures, network issues, power events, upstream connectivity changes, force majeure, or user configuration errors may still affect connectivity and task execution.
When an issue occurs, the platform diagnoses it using monitoring records, node status, network paths, order information, and reproduction materials submitted by the user. The usual process is to confirm the impact, verify connectivity, identify hardware or network causes, restore basic access, and record follow-up actions.
Order number, node, time of occurrence, connection method, complete error text, reproduction steps, affected tasks, and troubleshooting already completed. Remove passwords, private keys, tokens, and signing passphrases from support materials.
Issues caused by user code, runner scripts, third-party dependencies, certificate status, repository permissions, full disks, or local networks require the user to adjust the relevant configuration. Diagnostic conclusions are based on verifiable operation and support records.
Overdue payments, abuse, or security risks may trigger restrictions or termination
In cases of overdue payment, clear abuse, unauthorized access, security risks, illegal activity, or serious impact on infrastructure stability, the platform may restrict access, suspend tasks, require remediation, or terminate the service according to the level of risk. When immediate risk control is necessary, the platform may apply necessary restrictions first and explain the reason through account records or support communications.
Before the service ends, export the data you need and remove sensitive information. After an order is terminated, existing connection details may stop working. Do not continue attempting to access the node or connect with expired credentials.
If you have questions about order status, payment records, service actions, or the application of these Terms, submit a support ticket through the console or email support@macvpsgo.com. To help us verify the issue, provide the order number, issue category, event time, and relevant records. Do not send passwords, private keys, tokens, or signing passphrases.
These Terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first seek to resolve disputes through good-faith communication. If negotiation fails, either party may submit the dispute to a court with jurisdiction in that jurisdiction.