Engineering issues, routed directly to the right team

Send model, build, or billing questions to the right team

Get help choosing between two cloud Mac tiers, planning an iOS build farm, arranging five nodes, troubleshooting SSH or VNC connections, reviewing payment records, and deploying for your team. To reduce back-and-forth, include verifiable device, order, or build details in your first message.

Email Support Sign in to submit a ticket Rent a cloud Mac now
Two contact channels ROUTE / 02

Support email

support@minirents.com

Best for pre-sales evaluations, team planning, security reports, and questions not yet linked to an order. Our target for a first reply is within one business day.

Portal ticket

Open the support area after signing in

Best for device connectivity, build failures, orders, and billing issues. Tickets can link directly to device IDs and order records. Our target for a first technical response is within four business hours.

Do not submit passwords, private keys, or unsanitized signing materials Receive support
Choose an issue type first

Five request types, each with different first-message details

After you choose a type, the page adds it to the email generator below. For issues affecting a running device, order status, or billing records, use a portal ticket first.

Pre-sales evaluation

Share your project type, concurrent build count, build duration, and expected term to compare MiniRents M4 and MiniRents M4 Pro.

Use support email

Technical support

Include the device ID, node, time range of the error, commands run, and redacted logs. For existing devices, use a portal ticket first.

Open a portal ticket

Billing support

Provide the order ID, rental term, node, add-ons, and payment time range instead of submitting screenshots that cannot be matched to a record.

Open a portal ticket

Security report

Describe the vulnerability, reproduction steps, impact, and a safe time to contact you. Never place device credentials or sensitive materials in public channels.

Use support email

Team deployment

Provide the number of developers, repository location, daily build count, concurrency peak, and node preferences to plan the build queue and device count.

Use support email
Structured email generator

Organize the details, then send from your email client

This tool prepares the email subject and body in your current browser only; it does not submit your input to the website server. Clicking the button opens the mail app on your device with the support address prefilled.

Do not enter sensitive credentials. Use device IDs, order IDs, and redacted logs to help locate the issue. Do not enter passwords, SSH private keys, repository tokens, complete signing materials, or payment keys.

A support-ready email should include

  • A clear issue type and expected outcome
  • The relevant model, node, or order ID
  • The time range and reproduction steps
  • Troubleshooting already performed and redacted logs
Redact logs, paths, screenshots, and command output first.

Team deployment details

Evaluate device count and models using four data points

Team deployment depends on more than developer count. Build frequency, task duration, concurrency peaks, and rental term all affect queue length and device configuration.

01

Developer and pipeline scale

Provide the number of active developers, repositories, and pipelines, and say whether multiple projects share one build queue. If your team hands work across time zones, note when build demand peaks.

02

Daily build count

Estimate daily runs separately for development branches, merge validation, and production archives. Tracking short tests separately from full archives gives a more accurate view of caching and queue strategy.

03

Task duration and concurrency

Give the duration of typical and longest-running tasks, and note peak concurrency. Lightweight single-project builds can start with a MiniRents M4 evaluation; high-concurrency builds or Apple Silicon AI experiments are better suited to MiniRents M4 Pro.

04

Node and rental term

Share the approximate locations of your team and code repositories, then choose a node from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or US East. Evaluate terms by day, week, month, or quarter; live availability is confirmed by the portal.

Two available models

Submit the data and receive a configuration recommendation you can verify

The recommendation will specify the model, device count, node, term, and expected queue strategy without adding configurations outside the catalog.

View both plans and fixed pricing
Billing support

Link the order first, then verify the term and add-ons

Submit billing issues through a portal ticket whenever possible, since tickets can link order and device records. Include the order ID, rental term, node, model, and whether it includes +1TB SSD, +2TB SSD, or Thunderbolt 5 daisy-chaining.

Payment is supported only via USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All amounts are charged in US dollars (USD); available gateways are confirmed by the backend.

Sign in to submit a billing ticket

Fields to include with your ticket

BILL / TRACE
Order ID
Copy it from the order record in the portal
Rental term
Day, week, month, or quarter
Node
The node selected in the order
Add-ons
Storage expansion or Thunderbolt 5 daisy-chaining
Issue scope
Payment records, line items, or order status

Do not submit only a cropped payment screenshot. Keeping the order ID and full line-item name reduces manual matching time.

Security reporting channel

Limit the impact first, then send a reproducible report

If you discover an issue that may affect device access, portal accounts, node connectivity, or service boundaries, email support@minirents.com. If the report is directly related to your order or device, you can also sign in to the portal and submit a ticket.

Do not disclose device credentials, host addresses, repository tokens, unsanitized logs, or directly exploitable details in public channels. Our target for a first reply is within one business day. If the report is reliably reproducible and affects a device in use, include the impact scope in the subject line.

  1. 01

    Vulnerability description

    Describe the observed behavior, expected behavior, and discovery point—not just the conclusion.

  2. 02

    Reproduction steps

    List the environment, prerequisites, actions, and results in execution order, and remove sensitive values.

  3. 03

    Impact scope

    State whether the issue involves one device, one order, account access, or node connectivity.

  4. 04

    Safe contact method

    Continue communication through support email. For an existing device, you can use a portal ticket to share redacted materials.

Next steps

Submit a linked ticket for existing device issues

Sign in to link a device or order. For model evaluations, team deployments, and security reports before ordering, send a structured email.

Sign in to submit a ticket Email Support