How do I sign up for VESSL AI and create an org for team billing?

Most teams hit the same wall: you finally find the GPUs you need, then lose time just figuring out how to sign up, invite teammates, and centralize billing. VESSL AI is set up to make that part fast, so you can get back to running jobs instead of chasing invoices.

This guide walks through how to sign up for VESSL AI, create an organization, and route all usage to team billing—step by step.

Before You Start: What You Need

You’ll move faster if you have this ready:

Work email you want tied to your org (recommended over personal email)
Billing owner decided in advance (who will manage payment methods and invoices)
Rough GPU needs (A100/H100/H200/B200/GB200/B300 class, and whether you need Spot / On-Demand / Reserved)

You can still sign up without sorting all of this first, but it helps align the org from day one.

Step 1: Create Your VESSL AI Account

VESSL AI is the orchestration layer for AI infrastructure. You’ll use a single account to access multi-cloud GPUs, run jobs via Web Console or CLI, and manage org-level billing.

1.1 Go to the VESSL AI signup page

Open https://vessl.ai in your browser.
Click Get Started or Sign Up (top-right, depending on layout).

You’ll land on the account creation flow.

1.2 Sign up with your email

Typical flow:

Enter your work email address.
Set a strong password (or continue with any available SSO option, if shown).
Confirm your email address by clicking the verification link VESSL sends.

Once verified, you’ll be redirected into the VESSL Cloud Web Console.

Step 2: Understand Users vs Orgs (and Why Orgs Matter for Billing)

VESSL separates your personal user identity from organizations:

User account
- Tied to your email.
- Can belong to multiple orgs.
- Has personal settings and API tokens.
Organization (“org”)
- Shared workspace for your team, lab, or company.
- Owns GPU usage, projects, and billing.
- Has roles, permissions, and payment methods.

If you want team billing, you should run workloads under an org, not just a personal account. That’s how you get a single invoice and centralized cost visibility.

Step 3: Create an Organization for Team Billing

From the Web Console:

3.1 Open the org creation flow

Once you’re logged in:

Click your profile avatar or account menu (top-right).
Select “Create Organization” or “New Organization” (label may vary slightly).
You’ll see a short form for the new org.

3.2 Name and configure your org

Fill in the basics:

Organization Name
- Use a clear, official name:
  - Acme AI
  - Acme Robotics Research
  - Acme – GenAI Platform
- This appears in the console and on invoices.
Org slug / ID (if prompted)
- Short, URL‑friendly version, e.g. acme-ai.
- Keep it generic enough to reuse across teams internally.
Org type (if the form includes it)
- Company / Startup / Enterprise – multi-team, production workloads.
- Research Lab / University – academic usage; useful for academic programs.
- Personal – small projects, side experiments.

Click Create to spin up the org. You’re now its owner by default.

Step 4: Set Up Billing for the Org

Creating an org gives you a shared space, but you still need to attach billing so workloads can use GPUs consistently.

4.1 Navigate to Billing

Inside your new org:

Ensure you’re in the right org context (top-left org switcher).
Go to Settings or Admin.
Click Billing, Plan & Billing, or similar.

You’ll see billing options specific to this org—not your personal account.

4.2 Add a payment method

Common pattern:

Click Add Payment Method.
Enter company card details or other supported payment options.
Optionally add:
- Billing contact email (for invoices and alerts)
- Company legal name
- Billing address
- Tax information (if applicable)

Once saved, all org‑scoped usage (compute, storage) will be billed against this method.

4.3 Pick how you want to pay for GPUs

VESSL packages GPUs into clear reliability modes so finance and infra teams can align cost and risk:

Spot
- Uses preemptible excess capacity.
- Best for: large‑scale experiments, non‑urgent batch jobs, hyperparameter sweeps.
- Tradeoff: can be preempted; plan for retries or checkpointing.
On-Demand
- Reliable capacity with automatic failover across providers.
- Best for: production services, long‑running training where interruption hurts.
- Feature: Auto Failover keeps jobs running through provider/region issues.
Reserved
- Guaranteed capacity with commitment, up to ~40% discounts (varies by SKU/term).
- Best for: critical, predictable workloads (e.g., monthly LLM post‑training, ongoing vision pipelines).
- Includes: dedicated support and capacity guarantees.

You don’t “lock in” globally. You pick Spot / On-Demand / Reserved per workload or capacity plan, but decide at the org level how you intend to use each mode so billing owners aren’t surprised.

If you need a larger Reserved block (e.g., dozens of H100s across providers), use Talk to Sales from the site or console to set up a custom agreement and SLAs.

Step 5: Invite Your Team into the Org

To actually centralize billing, everyone needs to run under the same org, not under personal workspaces.

5.1 Send invites

In the org:

Go to Members, Team, or Access Control.
Click Invite Members.
Enter work email addresses for teammates.
Assign roles (examples; exact names may differ):
- Owner / Admin – full control, including billing and org settings.
- Developer / Member – can run jobs, manage projects, view usage.
- Billing / Finance – can view invoices and usage, maybe adjust billing settings.

Click Send Invites. Teammates will receive emails to join the org. New users will create accounts; existing VESSL users will accept the org invitation.

5.2 Enforce team‑based usage

To keep all spend on one invoice:

Ask users to switch to the org in the top-left selector before starting runs.
In the CLI, make sure they set the org in their config or specify it in vessl commands so runs are charged to the correct organization.

Step 6: Configure Projects, Access, and Guardrails

Once the org is live and billing is attached, structure it so usage is understandable:

6.1 Create projects per team or workload

Within the org:

Projects for workload types
- llm-post-training
- vision-pretraining
- physical-ai-simulation
- ai-for-science-benchmarks
Or projects per internal team
- research-foundation-models
- product-ml-platform
- robotics-lab

This makes it easier to slice costs per project and align with internal budget owners.

6.2 Give the right people the right access

Apply roles at project or org level:

Researchers / engineers: run jobs, view logs, manage artifacts.
Platform team: manage GPU tiers (Spot vs On-Demand vs Reserved), configure Auto Failover, handle Multi-Cluster views.
Finance / ops: read-only billing and usage.

6.3 Set expectations for reliability tiers

Document internally:

Which workloads may use Spot (experiments, one-off sweeps).
Which must use On-Demand with failover (production jobs, critical training).
Which justify Reserved capacity (recurring, high-value work).

That way, your GPU spend matches workload criticality, and org-level billing reflects deliberate choices—not accidents.

Step 7: Connect the CLI for Org-Scoped Runs

Most serious teams end up using the CLI (vessl run) for repeatable workflows.

7.1 Install and log in

Install the CLI (see docs from the console for exact command).
Run:
```
vessl login
```
Authenticate with the same user account you used for the org.

7.2 Set the active org

Ensure runs are billed to the right org:

vessl config set org <your-org-id>

or use the provided org selector command from the docs. From now on, vessl run jobs will be launched under that org unless overridden.

Step 8: Monitor Usage and Invoices

Team billing only works if you can actually see where GPU hours go.

8.1 Track usage in the console

Under Billing or Usage:

View GPU hours by:
- GPU type (A100/H100/H200/B200/GB200/B300)
- Reliability tier (Spot / On-Demand / Reserved)
- Project or user (depending on available filters)
Export usage for internal chargeback if you need to map costs to departments.

8.2 Access invoices

In Billing:

Download monthly invoices.
Confirm charges match internal expectations.
Share invoice PDFs automatically with your finance team by using a billing alias (e.g. finance@company.com) as the billing contact.

If you need custom billing cycles, PO references, or SLAs, talk to the VESSL team through the sales or support contact paths.

Step 9: When to Talk to Sales About Org-Level Plans

For some teams, self-serve signup and a card on file is enough. You should consider a sales conversation if:

You plan to run LLM post-training or AI-for-Science jobs on dozens of H100/H200/B200/GB200/B300.
You need guaranteed capacity (Reserved) multiple months in a row.
You require SLAs, compliance documentation (SOC 2 Type II, ISO 27001), or bespoke onboarding.
You want multi-cloud failover strategies across providers (AWS, Google Cloud, Oracle, CoreWeave, Nebius, Naver Cloud, etc.) formalized.

The result is usually a Reserved capacity plan with discounted rates and dedicated support, all attached to your organization’s billing profile.

Quick Troubleshooting: Common Signup & Org Issues

“I signed up but don’t see my org.”

Check the org selector in the top-left of the console.
Ensure you created an org or accepted the invite sent to your email.

“My job is billed to my personal account, not the team org.”

In the Web Console: switch to the org before starting runs.
In the CLI: run vessl config set org <org-id> and verify.

“Finance can’t see invoices.”

Add them as a Billing / Read-only member of the org.
Set the finance address as the billing contact email.

“We need to enforce On-Demand only for certain projects.”

Define an internal policy per project.
Have platform leads review usage dashboards regularly to ensure the right tier is used.

Final Takeaway

Sign up once. Create an org. Attach billing. Invite your team. From there, you get a single control surface for GPUs across providers, clear team billing, and less “job wrangling” for everyone using the platform.

Get Started