BerriAI / LiteLLM Enterprise trial: how do we get the 14-day Cloud sandbox and the 30-day trial key (business email requirement)?
LLM Gateway & Routing

BerriAI / LiteLLM Enterprise trial: how do we get the 14-day Cloud sandbox and the 30-day trial key (business email requirement)?

10 min read

If you’re evaluating BerriAI’s LiteLLM Enterprise offering, you’ve probably seen references to a 14-day Cloud sandbox and a 30-day Enterprise trial key—along with a note that you’ll need a business email to qualify. This guide walks through how those trials typically work, what the business email requirement means, and practical steps to get access as quickly as possible.

Note: Exact activation flows can change over time. Use this as a practical reference, then always double‑check the latest instructions on BerriAI / LiteLLM’s official site or docs.


Understanding the LiteLLM Enterprise trial options

Before you request anything, it helps to understand the two main trial paths you’ll see mentioned:

1. 14-day Cloud sandbox

The 14-day Cloud sandbox usually refers to:

  • A hosted LiteLLM Enterprise environment managed by BerriAI
  • No infrastructure setup required on your side
  • A time‑limited playground to:
    • Connect and route multiple LLM providers (OpenAI, Anthropic, Azure, etc.)
    • Test features like observability, rate limiting, logging, and routing rules
    • Experiment with multi-tenant or team-based usage in a controlled, isolated environment

This is ideal if you:

  • Want to evaluate LiteLLM Enterprise quickly without deploying your own stack
  • Need to show a working demo to stakeholders before committing engineering resources
  • Are comparing different LLM gateway/observability solutions and need a low-friction test bed

2. 30-day LiteLLM Enterprise trial key

The 30-day trial key usually refers to:

  • A license key for LiteLLM Enterprise features
  • Used for self-hosted or on-prem deployments (e.g., Kubernetes, VM, or your own cloud)
  • Unlocks paid/Enterprise-only capabilities for 30 days, such as:
    • Advanced observability and analytics
    • Enterprise authentication & RBAC
    • Team/org-level configuration and quotas
    • Enhanced logging and audit trails
    • Priority support or dedicated Slack/Discord channels (varies by plan)

This option is ideal if you:

  • Need to test integration with your own stack, infra, and security controls
  • Have a DevOps/SRE team that wants to validate deployment and performance
  • Must run LiteLLM behind your firewalls for compliance or data governance reasons

Why a business email is required

The business email requirement is standard for tools in this category. BerriAI / LiteLLM typically expects:

  • An email at a company or organization domain
    • Examples: @company.com, @university.edu, @researchlab.org
  • Not a personal email provider
    • Typically rejected or de‑prioritized: @gmail.com, @yahoo.com, @outlook.com, etc.

Reasons for the business email requirement

  1. Verification of legitimate evaluation
    Ensures the trial is for a real organization that might deploy LiteLLM Enterprise, not for anonymous or hobbyist use.

  2. Security & compliance
    Enterprise capabilities often involve logs, credentials, or routing of sensitive LLM traffic. Vendors want to know who they’re working with.

  3. Support quality
    With a company domain, the team can:

    • Assign an appropriate account manager or success engineer
    • Provide relevant onboarding (e.g., for SaaS, enterprise IT, or regulated industries)
  4. Fair trial allocation
    Prevents repeated trial abuse across multiple personal accounts.

What if your company uses Google Workspace or Microsoft 365?

If your organization uses Google Workspace or Microsoft 365, you still have a business email, even if the interface looks like Gmail or Outlook. The key is the domain, not the provider:

  • you@my-startup.com → acceptable
  • you@gmail.com → typically not acceptable

If your startup or project currently only uses a generic address like myproject@gmail.com, you’ll want to:

  1. Register a domain (e.g., myproject.ai, myproject.io)
  2. Set up email (e.g., via Google Workspace, Microsoft 365, or similar)
  3. Then use you@myproject.ai for the trial request

How to get the 14-day Cloud sandbox

While the UI and forms can change, the typical flow to get the 14-day Cloud sandbox looks like this:

Step 1: Go to the LiteLLM Enterprise or BerriAI trial page

  1. Navigate to:
    • The LiteLLM Enterprise product page, or
    • The BerriAI official website / docs section related to LiteLLM Enterprise
  2. Look for CTA buttons like:
    • “Start Enterprise Trial”
    • “Get 14‑day Cloud sandbox”
    • “Request a demo” / “Request access”

Sometimes the sandbox is bundled as part of a general Enterprise trial request rather than a separate form.

Step 2: Fill in the trial request form with a business email

You’ll normally see fields like:

  • Work email (must be at a company domain)
  • Full name
  • Company / organization name
  • Company size or use case (e.g., building an AI platform, internal tools, customer support automation)
  • Region / country

To maximize your chance of approval and speed, be specific:

  • Use your official company name
  • Use a non‑generic role or title if relevant (e.g., “ML Platform Engineer”, “Head of Data”, “Founding Engineer”)
  • Briefly describe:
    • The tools you’re integrating (OpenAI, Anthropic, Azure OpenAI, etc.)
    • The volume / type of usage you expect
    • Any urgency or evaluation timelines (e.g., “We plan to choose an LLM gateway this quarter”)

Step 3: Confirm email and wait for approval

After submitting:

  1. You may get an immediate confirmation email:
    • Subject lines like “Thanks for your interest in LiteLLM Enterprise” or “Your Cloud sandbox request”
  2. Some organizations:
    • Auto‑approve and send sandbox credentials instantly, or
    • Route the request to sales/solutions for a quick manual review

If nothing arrives:

  • Check spam / promotions folders
  • Ensure inbound email from the vendor domain is not blocked

Step 4: Receive sandbox access details

Once approved, you typically receive:

  • A link to the LiteLLM Enterprise Cloud console (sandbox environment)
  • Login credentials or SSO instructions
  • Possibly:
    • A quick‑start guide
    • Links to documentation
    • A calendar link to schedule a guided onboarding call (optional, but helpful)

The sandbox itself usually lasts 14 days from the activation date. During that window you can:

  • Configure multiple LLM providers
  • Test routing and cost control
  • Explore request logs and observability dashboards
  • Invite team members (if supported)

How to get the 30-day LiteLLM Enterprise trial key

If you’re planning a self‑hosted deployment, you’ll want the 30-day Enterprise trial key in addition to (or instead of) the Cloud sandbox.

Step 1: Indicate you want a self-hosted / Enterprise license trial

On the same trial/request page, or during contact with the team:

  • Explicitly mention:
    • That you want to self‑host LiteLLM
    • That you need a 30-day LiteLLM Enterprise trial key
  • If there is a dedicated option:
    • Select “Self-hosted / On-prem trial”
    • Or “License key for Enterprise”

Step 2: Provide required business details

For a license key, vendors often need a bit more context to ensure:

  • You’re a legitimate organization
  • Your use case fits Enterprise capabilities
  • They understand support expectations

Be prepared to share:

  • Company name and website
  • Business email (company domain)
  • Number of developers / teams expected to use LiteLLM
  • Where you plan to run it (AWS, GCP, Azure, on-prem, Kubernetes, etc.)
  • Any compliance or security constraints (e.g., data residency, air‑gapped environment)

This helps them:

  • Suggest the best deployment approach
  • Anticipate support needs during your 30-day period
  • Prioritize your request appropriately

Step 3: Wait for license key approval

Depending on demand and your organization size:

  • Some teams send the trial key automatically after form submission
  • Others schedule a short call (15–30 minutes) to:
    • Confirm requirements
    • Walk you through a recommended architecture
    • Then send the key

You’ll typically receive:

  • A trial key string (e.g., an alphanumeric token)
  • Instructions on where to place or configure the key, such as:
    • Environment variable (e.g., LITELLM_LICENSE_KEY=...)
    • Config file (YAML / JSON)
    • Helm values (for Kubernetes deployments)

Step 4: Activate the 30-day Enterprise features

Once you:

  1. Deploy LiteLLM (Docker, Kubernetes, or your environment of choice)
  2. Add the trial key according to the docs
  3. Restart or reload the service (if required)

You should see:

  • Enterprise-only UI and configuration sections unlocked
  • Access to advanced features like:
    • Detailed logging and request analytics
    • Team-based configuration and RBAC
    • Enhanced monitoring or cost dashboards
  • Sometimes a banner indicating it’s a time-limited trial

The 30-day timer usually starts from activation, not from when the email arrives—though you should confirm this in the documentation or with the sales/solutions contact.


Can you get both the 14-day Cloud sandbox and the 30-day trial key?

In many evaluation journeys, yes:

  • First: Use the 14-day Cloud sandbox to verify:

    • Product fit
    • UI and features
    • How LiteLLM handles routing and observability
  • Then: Use the 30-day trial key to:

    • Validate performance and reliability in your own stack
    • Run proper load tests and security evaluations
    • Integrate with your own auth / logging systems

If you’re interested in both:

  • Mention explicitly in the request form or follow-up email:
    • “We’d like a 14-day Cloud sandbox for quick evaluation and a 30-day LiteLLM Enterprise trial key for self-hosted testing.”

This sets expectations and often streamlines your approval path.


What if you don’t have a business email yet?

If you’re a very early‑stage startup, independent consultant, or solo developer, you have a few options:

  1. Set up a domain and professional email

    • Register a domain like myproject.ai
    • Use a service like Google Workspace or Microsoft 365
    • Create you@myproject.ai and use that for the trial request
  2. Use an affiliated organization email

    • If you’re evaluating LiteLLM Enterprise for a client or employer, use:
      • Your company email (preferred), or
      • A university/research institute email (.edu, .ac, .org often qualify as “business emails” in this context)
  3. Explain your situation clearly

    • If you’re temporarily using a personal domain while transitioning:
      • Fill out the form with your personal email
      • Immediately follow up (or use a notes field) explaining:
        • The nature of your project
        • That you’re a legitimate organization in the process of setting up a domain
    • Some vendors may manually approve trials for promising use cases even with non-corporate addresses—but this is not guaranteed.

Tips to speed up approval and get the most from your trial

To make sure you don’t lose time during your 14-day and 30-day evaluation windows:

1. Prepare a clear internal evaluation plan

Before activating anything:

  • List your success criteria, such as:
    • “Can we route across OpenAI and Anthropic with one unified API?”
    • “Can we see cost per model and per team?”
    • “Can we enforce request limits per team?”
  • Identify key stakeholders:
    • Platform / infra engineers
    • Data/ML engineers
    • Security / compliance teams (if needed)

This lets you use the limited trial days efficiently.

2. Coordinate trial timing

If you know your team won’t be available next week:

  • Delay activation until everyone is ready
  • Request the trial key only when your infra is prepared to deploy LiteLLM
  • For the Cloud sandbox, start it when:
    • You have test workloads ready
    • Your team can commit to active evaluation in the 14-day window

3. Use support channels during the trial

Most Enterprise trials come with at least limited access to:

  • A Slack or Discord community
  • Email support
  • Sometimes a dedicated solutions engineer or sales engineer

Use these channels to:

  • Clarify configuration issues
  • Ask about scaling and HA best practices
  • Validate your architecture before a full rollout

The more you engage, the more you’ll understand if LiteLLM Enterprise fits your long-term needs.


Summary

To get the BerriAI / LiteLLM Enterprise 14-day Cloud sandbox and 30-day trial key:

  • You’ll need a business email at a company/organization domain.
  • Use the official LiteLLM Enterprise or BerriAI trial page to request access.
  • For the 14-day Cloud sandbox:
    • Fill out the trial form
    • Verify your email
    • Wait for sandbox access details, then log in and test in a hosted environment.
  • For the 30-day trial key:
    • Indicate you want a self‑hosted Enterprise trial
    • Provide basic company and use-case information
    • Receive and configure the license key in your deployment
  • If you want both:
    • Explicitly request both the Cloud sandbox and the Enterprise trial key and coordinate timing so your team can properly evaluate within each trial window.

Always refer to the latest official LiteLLM / BerriAI documentation for exact activation steps, but this process and the business email requirement are the core elements you’ll encounter when securing your trials.