Request routing

Start with the issue type and send your details directly to the right team.

Use the same support email for presales advice, existing orders, technical issues, security reports, privacy requests, and partnerships. For existing orders, submit a ticket from the console first; order and node details are linked automatically to reduce repeated questions.

Public support email
support@bookamini.com
Existing orders
Console tickets preferred
Initial email reply target
Within 1 business day
REQUEST / BAM-06

Choose the right path

Available
01
Presales & partnerships Workload, configuration, term, node, and team size
Email
02
Orders & billing Include your order number to link transaction records
Ticket
03
Connections & builds Include region, client, error text, and reproduction steps
Ticket
04
Security & privacy Use a verifiable account email to describe the scope and request
Email
Do not submit passwords, recovery codes, or private keys 6 request types / 2 channels
Structured email

Include all required details at once

This tool organizes the email subject and body in your browser, then opens your system email app. It does not submit form content to the website server.

Issue type

Choose the closest option. For existing orders or node failures, use a console ticket first.

Describe the use case or symptom; avoid writing only “inquiry” or “not working.”
Related model
Current or target region
Remove passwords, recovery codes, private keys, and other sensitive content that could be used to sign in.
Presales selection

Describe the workload before choosing a model

Specify the task type, concurrency, and usage period instead of asking only which tier is faster. BAMini currently offers two Cloud Mac tiers on dedicated physical machines, not virtual machines.

01 / WORKLOAD

Describe the task and concurrency

Tell us whether you are remotely maintaining Xcode projects, running a self-hosted runner, testing Apple Silicon workloads, or handling video encoding and automated exports.

  • Single project or multiple projects in parallel
  • Whether you need a continuously running build queue
  • Whether you depend on graphical desktop operations
02 / CAPACITY

Provide memory and storage requirements

If you have a local environment, share peak memory usage, project directory size, cache growth, and the daily volume of generated build artifacts for typical tasks.

  • M4 Core: 16GB / 256GB
  • M4 Plus: 24GB / 512GB
  • Optional extra storage: +1TB or +2TB SSD
03 / DELIVERY

Describe the term, team, and node

State the expected continuous usage period, how many members need to hand off tasks, and where the team is mainly based. Choose a node based on measured team network performance.

  • Billing period: day, week, month, or quarter
  • Team size and handoff hours
  • Target node and acceptable input latency
Two available configurations

BookAMini M4 Core starts at $20.1/day; BookAMini M4 Plus starts at $41.5/day. Actual availability is returned in real time by the console.

View full plans
Technical troubleshooting template

Error text, timing, and reproduction steps are all essential

“Cannot connect” or “build failed” is not enough to identify the cause. Keep the original error text and record the environment, actions, and results in chronological order.

CASE INPUT / REQUIRED

Fields to include with a ticket

7 items
Time of occurrence
Include the time zone and state whether it is ongoing
Required
Node region
Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, or US West
Required
Related model
BookAMini M4 Core or BookAMini M4 Plus
Required
Client
Client name, version, and local operating system version
Connection issue
Error text
Copy it in full; do not submit only the final truncated line
Required
Reproduction steps
Start from the normal state and record each click or command in the actual order
Required
Actions already tried
Local network checks, client reconnection, rerun results, and corresponding outcomes
Recommended
Copyable format

Technical request body order

Issue type:
Order number:
Model and region:
Time and time zone:
Client and version:
Expected result:
Actual result:
Complete error text:
Reproduction steps:
Actions already tried:
Does it reproduce consistently:

Remove project keys, access tokens, and personal paths from logs before submitting. Do not send passwords, recovery codes, private keys, or anything that can be used to sign in.

View troubleshooting guide first
Security & privacy

Use a verifiable email to describe the scope, impact, and request

Send both security reports and data rights requests to support@bookamini.com. They require different information, so do not combine vulnerability details and personal information requests in one email.

Security report

Define the reproducible scope first

Include when you found it, the affected page or feature, prerequisites, reproduction steps, observed impact, and a contact method for follow-up.

  • Start the subject with “Security report”
  • Separate observed facts from risk assessment
  • Remove account and order details from screenshots when necessary
  • Do not attempt to access data that is not yours
Acknowledgment target Within 1 business day
View security boundaries
Privacy request

Specify the request type and verification method

For access, correction, deletion, processing restriction, or objection requests, use a verifiable email associated with the account and specify the data scope to be handled.

  • Start the subject with “Privacy request”
  • Specify access, correction, deletion, or processing restriction
  • Provide the information needed to locate the account
  • Do not attach login credentials to the email
Acknowledgment target Within 1 business day
Read the privacy policy
Ready to start

Choose one of two configurations and place an order in one of six node locations.

Cloud Mac on a dedicated physical machine, not a virtual machine. Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West are all available in the configuration flow; actual availability is returned in real time by the console.