Queued Deployment

Link & Sleep workflow — submit credentials now, your Cloud Engine deploys them automatically when ready.

Queued Deployment — Link & Sleep

The Core Idea

You don't need to wait. After purchase, simply enter your platform credentials and walk away. The system handles everything else.

Your Cloud Engine will automatically:

  1. Encrypt and store your credentials
  2. Provision your dedicated node
  3. Pull credentials and establish connection
  4. Begin monitoring — all while you sleep

How It Works

Step 1: Submit Credentials

Immediately after purchase (or anytime from your Dashboard):

  1. Go to Dashboard → Terminal → Link Account
  2. Enter your platform credentials (MT5 login, Alpaca API key, etc.)
  3. Click "Link & Deploy"

Your credentials are encrypted with AES-256 before leaving your browser. They never exist in plaintext on our servers.

Step 2: Queued Processing

Your deployment enters the secure queue:

You submit → [AES-256 Encryption] → Secure Queue → Cloud Engine picks up → Deploy

The system processes deployments in order. During peak hours, queue time is typically under 5 minutes. During off-peak, it's nearly instant.

Step 3: Automatic Deployment

When your Cloud Engine is ready:

  1. Node boots — Your dedicated execution environment starts
  2. Credentials pulled — Encrypted credentials are decrypted in-memory only
  3. Connection established — Platform connection verified
  4. Monitoring begins — Risk firewall activates

Status Lifecycle

Track your deployment in real-time on the Dashboard:

| Status | Meaning | Action Required | |--------|---------|-----------------| | QUEUED | Credentials received, waiting for node allocation | None — sit back and relax | | PENDING | Node allocated, establishing connection | None — almost there | | EXECUTED | Credentials deployed to node | None — finalizing | | CONNECTED | ✅ Fully operational, risk firewall active | None — you're live! |


Troubleshooting

Stuck in QUEUED for more than 30 minutes

This is rare but can happen during high-demand periods:

  1. Check the Dashboard for any system announcements
  2. Verify your license is active (Dashboard → Profile → Licenses)
  3. Contact support if the issue persists beyond 1 hour

Stuck in PENDING

Usually means the platform connection is taking longer than expected:

  1. Verify your credentials are correct (you can re-submit from Dashboard)
  2. Check if your platform's API is experiencing downtime
  3. For MT5: ensure your broker server allows automated connections

Timeout after EXECUTED

The credentials were deployed but the platform isn't responding:

  1. Your broker/platform may be under maintenance
  2. API key permissions may be insufficient — check the "trading" scope
  3. Re-link with fresh credentials if the issue persists

Security Notes

  • Credentials are AES-256 encrypted at rest and in transit
  • Decryption only occurs in-memory on your dedicated node
  • Credentials are never logged and never stored in plaintext
  • Each deployment is HWID-bound to your authorized device
  • You can revoke credentials at any time from your Dashboard