Enverge Cloud / docs

Documentation

A short tour of everything Enverge Cloud does today - instances, queueing, SSH keys, billing, usage history, and account basics.

Instances

An instance is a containerized GPU sandbox running on a DGX Spark host. Each instance has a name, one attached SSH key, and a selected GPU profile.

GPU Types

  • NVIDIA DGX Spark GB10 - single node, 128 GB unified memory. $0.65 / hour
  • 2x NVIDIA DGX Spark GB10 - dual node interconnect, 256 GB unified memory. $1.50 / hour If this profile has no capacity, launch falls back to queueing.

Lifecycle

Once launched, an instance remains available until you delete it. Dashboard status badges reflect live container state (`running`, `exited`, `unknown`).

  • Restart cycles the container without ending the billing session.
  • Delete removes the container and ends billing for that session.

SSH Access

Running instances expose an SSH snippet in the format ssh user@<hostname>.ssh.enverge.dev. First connect after create/restart can take up to a minute while relay state settles.

Queue

When capacity is unavailable, launch requests can enter a queue instead of failing. Queue order is first-in, first-out per GPU type.

Queue wait time is free

Billing starts only when an instance is actually created.

  • You can have one active queue entry per GPU type.
  • Queue entries can be cancelled at any time.
  • When capacity opens, the oldest matching entry launches automatically.

SSH Keys

SSH keys are managed during instance creation through a named key picker.

  • Names are unique per account.
  • Only paste public keys, never private keys.
  • Keys attached to active instances cannot be deleted.
  • Removing an account key does not retroactively remove it from existing instances.

Billing

Billing is metered by usage and settled through Stripe. Session billing spans from create to delete.

Restart does not stop billing

Only deleting an instance ends billing for that session.

Queueing itself is free. Payment method checks occur when an instance is launched.

Usage History

Usage pages show both runtime sessions and queue history.

  • Sessions table: one row per create-to-delete run.
  • Queue history: wait duration and final outcome (launched/cancelled).
  • Both views are paginated and refreshable from the UI.

Account

  • Sign in with email/password or magic link.
  • Password reset flow is available from sign-in.
  • Sign out is available from the user menu in the app.