Documentation

v1 tenant journey — deep links instead of unified SSO. Replace placeholder URLs when FireEdge, Kubero, and Lago portals are provisioned.

Getting started

  1. Choose a plan on the pricing page.
  2. Complete checkout through the Lago-hosted Stripe flow.
  3. Wait for the provisioner to create your isolated VDC (target: under 5 minutes).
  4. Open the links in your welcome email.

After payment

Your welcome email includes separate links for each surface:

  • Billing portal — invoices, payment methods, usage (Lago customer portal)
  • VPS console — FireEdge self-service for VMs, SSH keys, templates
  • App platform — Kubero dashboard for Git deploys
  • Inference API — endpoint URL and tenant API key (when enabled on your plan)

Cloud VPS

Provision Linux VMs from approved templates. Quotas enforce CPU, memory, and disk per VDC. VMs may run on lab hardware or provider-attached clusters as capacity expands.

Kubernetes

Platform plans include a dedicated OneKE (RKE2) cluster. Download kubeconfig from the tenant onboarding flow and use standard kubectl workflows.

App platform

Connect a Git repository in Kubero, set environment variables, and deploy. Each push triggers a build with logs and rollback support.

GPU inference

Call the OpenAI-compatible /v1/chat/completions endpoint with your tenant API key. Usage is metered and exported to Lago for billing.

Support

Email [email protected] for provisioning issues or billing questions. Include your tenant ID from the Lago portal.

Full platform architecture and billing integration are documented in the operator workspace plan linked from the OpenNebula bare-metal platform program.