Help Center

Our fully automated system typically completes initialization and delivers within 1–5 minutes after payment confirmation. You will receive an email notification and console alert with your login credentials. If not activated after 10 minutes, please contact support.

On the order details page in the console, the top action bar provides Power On, Power Off, and Restart buttons to remotely control the device power state, with real-time status updates.

Log in to the console, click the corresponding order to view the details page. The Device Info section displays full hardware specs: model (Mac Mini M4), CPU cores (10-core), memory (16 GB), storage (256 GB NVMe SSD), bandwidth (1 Gbps dedicated), and public IPv4 address.

Yes. You have full macOS system access and can install any remote tool such as Apple Remote Desktop, TeamViewer, or Tailscale. You can also enable macOS's native Screen Sharing service.

Dedicated physical machine, not virtualized. Each user gets a real Mac Mini M4 device with exclusive access to all CPU, memory, and storage — no resource contention, 100% performance.

Yes, each device is assigned one dedicated public IPv4 with an exclusive 1 Gbps network port — no shared bandwidth. Optional Thunderbolt 5 Link service (80 Gbps) is also available for building multi-machine clusters.

This is MacLogin's premium interconnect service that uses Thunderbolt 5's 80 Gbps bandwidth to physically link multiple Mac Minis into a high-performance compute cluster. Ideal for iOS compile farms, render clusters, and distributed AI inference. Add this service at checkout.

Hardware specs and pricing are identical across all nodes. The difference is geographic network location:
• Singapore: Low latency for Southeast Asia, ideal for overseas businesses
• Japan (Tokyo): Premium East Asia node, stable and low-latency
• South Korea (Seoul): Ideal for Korea and nearby markets
• Hong Kong: Friendly access from mainland China
• US East: Coverage for North America and Europe
All nodes are Tier 3+ data centers with dedicated IPv4 and 1 Gbps bandwidth.

After logging into the console, the left sidebar lists all orders and their current status (Running / Expired / Pending Payment). Click any order to view the expiry date, days remaining, and full transaction history.

Weekly/monthly/quarterly subscriptions have auto-renewal enabled by default. The system sends a reminder email before expiry. You can cancel auto-renewal anytime in the console; the service will stop at the end of the current period without early termination. Daily rentals are one-time payments with no auto-renewal.

We currently support Visa, Mastercard, American Express, and all payment methods supported by Stripe. The payment gateway is powered by Stripe with full 256-bit TLS encryption; no card details are stored.

Visit the Sign In / Register page, enter your email, and the system will automatically determine whether to register or log in. New users simply enter the email verification code and a password to complete registration in about 1 minute.

Visit the login page, enter your email to proceed to the login step, then click the Forgot password? link to reset your password via email verification code.

Yes, one account can order and manage multiple Mac Mini devices. All orders are listed in the left sidebar of the console for easy management.

There are two ways:

• Ticket System (Recommended): Log in to the console → Click Support → Fill in the description, and we will reply within 2–24 hours
• Email: Send an email to [email protected], please include your account email and order number for faster processing

Follow these troubleshooting steps:

1. Click the Restart button in the console and wait 2–3 minutes before retrying
2. If still unconnectable after restart, try Power Off → wait 30 seconds → Power On
3. Check your network and confirm you can reach the target node IP
4. If none of the above works, submit a ticket with your order number and we will prioritize it

Zero-Trust means every user and session must be explicitly authenticated before accessing a Mac node — even within your team. There are no shared admin accounts. Each user gets a dedicated login credential with scoped permissions, enforced at the network and OS level. Every session is logged and auditable.

Yes — MacLogin supports multi-user isolation on dedicated Mac mini M4 nodes. Each user account operates in a separate macOS user space with its own home directory, environment variables, and file permissions. Users cannot access each other's data without explicit macOS system permissions.

Shared admin accounts break audit trails — you can no longer tell who made a specific change or accessed sensitive data. If a shared credential is leaked, the entire Mac node is exposed. Individual accounts with least-privilege access are the foundation of any Zero-Trust security model.

MacLogin logs all SSH and VNC session events at the infrastructure level, including connection timestamps, source IPs, and authentication results. For detailed application-level audit logging, you can configure macOS's built-in audit subsystem (auditd) or integrate with your preferred SIEM solution.

You can configure macOS Application Firewall rules and SSH AllowUsers / Match directives to limit what each user can access. For network-level isolation between users or workloads, we recommend running each AI agent or service in a separate macOS user account, and using Tailscale or similar Zero-Trust network overlay to define service access boundaries.

OpenClaw is an AI agent framework that can execute shell commands, access the filesystem, and interact with external services. Running it on your primary development machine creates significant risk — a misconfigured agent or supply-chain attack could expose your private keys, source code, and personal data. A dedicated Mac mini M4 cloud node provides full hardware isolation: even if an agent goes rogue, it cannot reach your local machine.

The recommended setup is:

1. Provision a dedicated Mac mini M4 node (separate from your primary work node)
2. Create a dedicated macOS user account for OpenClaw with no sudo privileges
3. Store API keys and secrets using macOS Keychain or a secrets manager — never in plaintext config files
4. Restrict outbound network access to only the domains the agent needs
5. Enable session logging so you can review what the agent did

Contact support if you need help with initial OpenClaw configuration.

Yes, but we recommend isolating them in separate macOS user accounts if they handle different projects or have different permission scopes. Both OpenClaw and Claude Code can execute arbitrary shell commands, so sharing a single user account between them eliminates the isolation boundary. For sensitive workloads, use separate Mac mini nodes entirely.

Never store secrets in plaintext files, shell history, or environment variable exports in .zshrc/.bashrc. Use macOS Keychain for local secret storage, or a purpose-built secrets manager. Rotate API keys regularly, especially after any agent execution that touched external services. Audit which keys each agent account has access to.

Use the MacLogin console to restart or power-cycle your Mac mini node. For automatic recovery, configure macOS launchd to restart the OpenClaw process on failure. You can also set up a lightweight health-check script that monitors the agent process and triggers an alert (via email or webhook) if it stops unexpectedly. Contact support if you need help with automated recovery configuration.