Bound to your device's non-extractable WebCrypto ECDSA P-256 Passkey (...) over TLS 1.3. Click Sign in with Google below, then paste your 4/0AX... code into the box to unlock automatically:
Provision or upgrade a dedicated, self-configuring Gemini 4 Argon REPSL virtual machine in your Google Cloud project. Replacing an existing VM never deletes it: the predecessor is archived to ~/lineage_repsl/, stopped ($0 CPU), and its active cells auto-resume via repsl -r <UID>.
1
Configure & Boot Your REPSL Instance
Authenticated via Google OAuth as
🔑 Website Access Control (Authorized Google Accounts on repsl.net):
✨ Create New Google Cloud Project
✓
Your Sovereign REPSL VM is Online & Ready!
✔ SSH key downloaded & REPSL harness running in ~ (Window 0: bash, Window 1+: REPSL). Paste this once in your local machine terminal to install your key and bind the test alias — after that, just type test anytime on your local machine to log in (assumes Linux and SSH key downloaded to ~/Downloads):
🟢 🚀 New VM Child Launcher (:8081):
🟢 🥚 New VM Egg Enclave (:8443):
🟢 🎥 New VM Meet Recorder (:8092):
Loading project VMs & lineage vault...
🧭 First-Time Google Cloud Project Onboarding ()
This Google Cloud project hasn't had Compute Engine or Billing activated yet. Complete these 3 quick one-time steps in Google Cloud Console (~60 seconds total):
Link a Billing Account: Google Cloud requires a billing account before booting VMs (new GCP users receive $300 in free trial credit; stopped VMs cost $0/hr CPU and .sqsh capsules cost ~$0.001/mo).
Enable Compute Engine API: Click button #2 below, press the blue Enable button on Google's page, and wait ~45–60 seconds for Google to initialize your project's default VPC network.
Enable Vertex AI API: Click button #3 below and press Enable so Gemini 4 Argon runs natively on your VM's Service Account with zero API keys.
✔ Ready? Once Billing is linked and Compute Engine API finishes enabling, simply click 🚀 Launch / Replace REPSL VM above again — no need to sign in again!