1. Acceptance and Service Provider
Accessing the DebugMac website, creating a console account, submitting an order, paying fees, or using a node confirms that the user has read and agrees to these terms. A user acting for an organization confirms they are authorized to accept these terms for that organization and are responsible for all orders and use under the account.
The service is provided by the platform operator. The operator maintains the public catalog, processes orders, assigns nodes, issues access credentials, provides support, and manages renewals, suspensions, and terminations under these terms. Console records control for specific order details, payment status, and node information.
If the user does not agree to these terms, they must stop creating an account or submitting an order. Users with submitted orders who have questions about the terms version may contact the support team through a console ticket or at support@debugmac.com and must confirm before continuing to use the service.
2. Service Definition
DebugMac provides remotely accessible dedicated physical Mac servers in the cloud. Each valid order corresponds to a dedicated physical node assigned for that order; tenants do not share the same physical node environment. The service is not a virtual machine.
Users may use SSH and the macOS graphical interface with the connection details in the delivery receipt for software builds, automation, testing, Apple Silicon inference, audio and video processing, and other tasks permitted by these terms. The delivery receipt lists the node region, host address, username, host fingerprint, access issuance status, and term end time.
The service does not include models, regions, or additional capabilities outside the catalog. Users are responsible for managing the software, repositories, keys, build artifacts, task configurations, and system actions they initiate.
3. Orders and Configuration
Only one configuration is currently available: Debug M4, featuring a Mac Mini M4, 16GB RAM, and a 256GB SSD. Before ordering, users should verify the model, memory, base storage, term, node region, and add-ons. After confirmation, the console order details define the delivery scope.
Available node regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States—a total of five nodes. Debug M4 can be ordered in any listed region; real-time availability is shown in the console.
Submitting an order does not entitle the user to hardware outside the catalog or to move between regions. To change the term, region, storage, or Thunderbolt 5 daisy-chain option, the user must first confirm the available process, data migration plan, and applicable fees through a console ticket.
4. Pricing and Payment
Debug M4 pricing is $19.5/day, $52.8/week, $97.7/month, and $265.7/quarter. Each billing period has its own catalog price; prices are not calculated by simply multiplying the daily rate and do not guarantee future pricing. The USD amount shown at checkout controls.
All orders are settled in USD. Payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The console determines which payment gateway is available. Before paying, users should verify the network type, recipient details, card billing information, and order amount.
Payment is complete only after system confirmation. An order may remain pending when network confirmation is delayed, payment details do not match, or processing is incomplete. Users must not pay for the same order twice; if the status appears incorrect, retain the order ID and payment receipt and submit a console ticket.
Unless mandatory applicable rules or these terms expressly provide otherwise, charges for a delivered term are not automatically refunded because the user did not connect to the node, stopped tasks early, or deleted data. Confirmed duplicate payments or billing errors will be handled based on the verification results.
5. Add-ons
+1TB SSD pricing is $2.3/day, $6.1/week, $11.3/month, and $30.7/quarter; +2TB SSD pricing is $4.6/day, $12.2/week, $22.6/month, and $61.4/quarter. Add-on storage is enabled per order in addition to the base 256GB SSD. The delivery receipt controls the mounting method and usable capacity.
Thunderbolt 5 daisy chaining is billed per device at $1.7/day, $4.6/week, $8.5/month, and $23.1/quarter. Users must confirm the number of linked devices, intended workflow, and connection requirements when ordering. Unless confirmed, this option does not mean unlimited external devices or shared capacity.
Add-ons use the same billing period as the base term and appear separately in the order details. Adding, removing, or replacing an add-on during the term may require related tasks to be stopped, data to be copied, or delivery information to be reissued. Users must confirm the scope before execution.
6. Acceptable Use
Users must not use the service for unlawful activity, unauthorized access, credential theft, malware distribution, phishing, denial-of-service attacks, abusive network scanning, resource destruction, or any other conduct that may affect node, network, or infrastructure stability.
Users must not bypass access controls, falsify identity or order information, resell unauthorized access, interfere with other nodes, continuously consume abnormal network resources, or use the service to store or distribute content that infringes others' rights.
Users must securely store SSH private keys, VNC credentials, and console login details, promptly revoke access that is no longer needed, and remain responsible for scripts, automated tasks, and administrator actions performed under the account. If credentials are exposed or an unusual connection is detected, immediately end the relevant session and submit a console ticket.
Where there are reasonable grounds to believe conduct may create an immediate security risk or infrastructure damage, the platform may take necessary measures such as restricting connections, isolating tasks, or suspending access. Where feasible, it will explain the reason, scope of impact, and conditions required for restoration.
7. Uptime and Claims
The node uptime target is 99.9%, measured by calendar month as the proportion of time delivered nodes can establish remote connections and perform basic computing tasks. All nodes operate continuously 365 days a year.
Uptime calculations exclude the user's network failures, incorrect credentials, user-initiated shutdowns or high-risk system actions, user software or script failures, third-party payment processing status, events beyond reasonable control, and restrictions imposed because of the user's violation of these terms. Brief network jitter that does not make a node continuously inaccessible is not counted as a complete outage period.
If the user believes a service interruption occurred, they must submit a console ticket within seven calendar days, providing the order ID, node region, start and end times, host fingerprint verification, connection logs, and troubleshooting steps completed. The support team will confirm the scope of impact using node and network records.
If verification shows uptime below the 99.9% standard, the platform may provide service credits based on the affected duration and corresponding order charges. Credits apply only to eligible future orders or renewals, have no cash value, are non-transferable, and may not exceed the base service fees paid for the affected order's measurement period.
8. Renewal, Suspension, and Termination
The console order record controls the term end time. Users who need to continue using a node must confirm renewal and complete payment before the deadline; renewal takes effect only after system confirmation. Orders not renewed will enter the access-revocation process after the term ends.
The platform may suspend or terminate related access when the term expires, payment is incomplete, acceptable-use rules are seriously violated, credentials are confirmed to pose a security risk, or user activity has a continuing impact on infrastructure. Except where immediate action is needed to control a security risk, the platform will explain the reason and next steps through account-linked information or a console notification.
Users must export repositories, build artifacts, logs, models, media files, and other required data before the term ends. The platform is not responsible for serving as the user's long-term storage for working data and does not guarantee that node data can be recovered after the term ends.
Access revocation includes invalidating issued credentials, ending remote sessions, and starting the node cleanup process. Account termination does not remove payment obligations incurred before termination, liability for violations, or confidentiality and liability provisions that are intended to remain effective.
9. Liability and Disputes
Users should maintain independent backups of source code, signing materials, build artifacts, models, media files, and business data, and verify recovery procedures before system updates, disk changes, automated cleanup, or high-risk commands. A single copy on a node is not a substitute for the user's own backup system.
To the maximum extent permitted by applicable rules, the platform is not liable for lost profits, business interruption, lost opportunities, or other indirect losses. The platform's aggregate liability for a single dispute is limited to the service fees actually paid by the user for the corresponding order during the relevant term, except where applicable rules do not permit such a limitation.
If an event beyond reasonable control causes delay or prevents performance, the affected party must take reasonable mitigation measures and notify the other party where feasible. Notices sent through the console, to the account-linked email address, or from support@debugmac.com are deemed delivered when normally sent and available for receipt.
These terms are governed by the laws of the jurisdiction where the platform operator is established. In a dispute, the parties should first seek good-faith resolution through a console ticket or support@debugmac.com. If unresolved, the dispute will be submitted to a court with jurisdiction in that jurisdiction.