Architecture & Connectivity

Emuluxe is a multi-layered simulation ecosystem. To provide a seamless experience, we synchronize your authentication and hardware configuration across four distinct environments: the Web Platform, the Chrome Extension, the IDE Extensions, and the Local CLI.

1. The Registration Lifecycle

Everything starts with a central identity on the Emuluxe Platform.

• Account Creation: When you sign in via Google or GitHub at app.emuluxe.com, a permanent UID is assigned to your developer profile.
• Global Registry: Your plan limits, team roles, and active session quotas are managed in our global registry.
• Quota Model:
  • Free Plan: 10 Lifetime Sessions (Fixed pool).
  • Pro Plan: 150 Monthly Sessions (Renewing pool, resets on payment).

2. Connecting Devices (The Seat System)

Emuluxe uses a "Seat" model to manage hardware access. A Seat is a unique connection between a physical machine and your account.

• Hardware Discovery: When you first activate the Chrome extension or log in via VS Code, Emuluxe performs a hardware discovery scan.
• Device ID: A unique emx_ identifier is generated for your workstation.
• Ownership: Once verified, this device ID is "claimed" by your account. This prevents unauthorized secondary accounts from using the same hardware seat.

3. Atomic Token Sync (IDE ↔ CLI)

A core part of the Advanced Simulation Engine is the local kernel coordination between your IDE and the Emuluxe CLI.

The Sync Flow:

1. Authentication: You log in via the VS Code or Cursor extension using a secure deep-link.
2. Token Receipt: The extension receives an encrypted authentication token from the platform.
3. Atomic Write: The extension automatically performs an Atomic Token Sync by writing this token to your local system configuration at ~/.emuluxe-cli-nodejs/config.json.
4. CLI Provisioning: When the simulator launches, the underlying CLI engine is already authenticated, eliminating the need for a separate terminal login.

4. Hardware Fingerprinting (Security)

To prevent account multi-tenancy on shared hardware and ensure license compliance, Emuluxe implements a robust Cross-Source Fingerprint.

[!IMPORTANT] Fingerprint Formula: IP Address + CPU Core Count + OS Platform. This hash is stable across the Chrome Extension, VS Code, and the CLI.

Account Locking:

If a machine identifies as being "Owned" by Account A, any attempt by Account B to start a session or verify the device will result in a 403: Account Locked error.

To clear a hardware seat for a new account, you must first "Deactivate" the device from your Devices Dashboard on the original account.

Next, learn how to configure IDE Extensions.