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)?

12 min read

If you’re evaluating BerriAI’s LiteLLM Enterprise and wondering how to actually access the 14‑day Cloud sandbox and 30‑day trial key, the key steps revolve around using a valid business email, filling out the correct forms, and understanding what each “trial” really includes. This guide walks through the process, typical approval flow, and how to troubleshoot common issues with the business email requirement.


Understanding the BerriAI / LiteLLM Enterprise trial options

Before you sign up, it helps to clarify the two distinct pieces you’re asking about:

  • 14‑day Cloud sandbox
    This is usually a hosted LiteLLM Enterprise Cloud environment provided by BerriAI. It’s designed so your team can:

    • Spin up a managed LiteLLM instance
    • Connect to supported LLM providers
    • Try enterprise features like logging, rate limiting, observability, or routing rules
    • Test integrations with your internal services in a safe, time‑boxed environment
  • 30‑day trial key
    This is typically:

    • A time‑limited license or API key that unlocks LiteLLM Enterprise features
    • Usable for self‑hosted or hybrid deployments
    • Intended for more in‑depth technical evaluation (e.g., running LiteLLM in your own VPC, Kubernetes cluster, or on‑prem)

In many cases, companies use both:

  1. Start with the Cloud sandbox for immediate hands‑on testing.
  2. Use the 30‑day trial key to validate a production‑like deployment in their own environment.

Why BerriAI / LiteLLM requires a business email

BerriAI generally requires a business email address (e.g., @company.com) rather than a free mailbox (@gmail.com, @yahoo.com, etc.) for Enterprise trials because:

  • Enterprise qualification – The Enterprise edition is aimed at organizations with teams, budgets, and security/compliance requirements.
  • Security & compliance – Many Enterprise features involve logs, audit trails, and potentially sensitive data. Verifying the business domain is a basic security step.
  • Support & onboarding – BerriAI’s team needs a reliable way to identify your company, provide onboarding, and assign a proper account manager.

If you don’t currently have a business email or are working under a startup or research umbrella, see the “What if you don’t have a business email?” section below.


Step‑by‑step: Getting the 14‑day Cloud sandbox

While the exact UI may change over time, the general flow to get the LiteLLM Enterprise Cloud sandbox looks like this:

1. Go to the LiteLLM / BerriAI Enterprise trial page

Typically you’ll find it through one of these:

  • The LiteLLM Enterprise section on the BerriAI or LiteLLM website
  • A “Get a demo” or “Try Enterprise” button on the main product page
  • Links in the LiteLLM documentation or GitHub README that mention “Enterprise Cloud” or “Cloud sandbox”

Look for wording like:

  • “Start 14‑day LiteLLM Enterprise Cloud sandbox”
  • “Try LiteLLM Enterprise Cloud”
  • “Request Cloud sandbox access”

2. Fill out the trial / sandbox request form

On the request form, you’ll typically be asked for:

  • Full name
  • Business email (required for Enterprise evaluation)
  • Company name
  • Company size or role (e.g., 1–10 employees, 50–200, etc.)
  • Intended use case – such as:
    • Centralized LLM gateway for multiple teams
    • Cost optimization and routing across multiple LLM providers
    • Logging, observability, and governance for AI usage
    • Internal tools, RAG systems, or customer‑facing AI apps

Provide clear information. Teams reviewing these forms prioritize requests that show:

  • A plausible production‑grade use case
  • A real organization with potential to adopt Enterprise
  • Some clarity on security or compliance needs (e.g., SOC2, data residency, VPC isolation)

3. Verify your business email

After submitting the form, one of two flows typically happens:

  • Automatic email verification

    • You receive a message at your business email address.
    • Click a verification link to confirm your domain.
    • Once confirmed, an account is created for the Cloud sandbox.
  • Manual review + onboarding

    • For some companies (especially large enterprises or regulated industries), BerriAI may do a quick human review.
    • They might schedule a brief call or email exchange to confirm requirements and set up the sandbox with the right configuration.

If the verification email doesn’t arrive:

  • Check spam/junk folders.
  • Ensure your corporate mail gateway isn’t blocking external links.
  • If there’s an “Resend verification” option on the trial page or in the account portal, use it.
  • If all else fails, contact BerriAI support or sales (see troubleshooting section).

4. Receive access to the 14‑day Cloud sandbox

Once approved and verified:

  • You’ll get a welcome email with:

    • Login URL for the LiteLLM Enterprise Cloud dashboard
    • Temporary password or single‑sign‑on (SSO) link (depending on configuration)
    • Summary of what’s included in the sandbox and the 14‑day limit
  • Inside the Cloud sandbox, you can normally:

    • Configure LLM providers and keys (OpenAI, Anthropic, Azure, etc.)
    • Set up routing, fallback, and cost controls
    • Enable usage logging and analytics
    • Invite a small number of additional team members (depending on plan)

5. Keep track of the 14‑day timeline

The sandbox is typically time‑boxed:

  • Day 1–3: Basic configuration, connect providers, try the UI and basic API calls.
  • Day 4–7: Integrate with your internal tools, run POCs or synthetic tests.
  • Day 8–14: Run more realistic workloads, evaluate dashboards, cost controls, and security features.

Near the end of your 14‑day period:

  • You’ll usually receive reminder emails.
  • You can discuss extending the sandbox or transitioning to a paid Enterprise plan with the BerriAI team.

Step‑by‑step: Getting the 30‑day LiteLLM Enterprise trial key

The 30‑day trial key is slightly different from the Cloud sandbox: it’s typically used for self‑hosted or hybrid deployments. The general process is:

1. Indicate that you need a trial key for self‑hosting

When you fill out the trial form (or talk with the sales/solutions team), explicitly mention:

  • You want a 30‑day LiteLLM Enterprise trial key
  • Whether you plan to:
    • Run LiteLLM inside your own VPC or on‑prem cluster
    • Integrate with existing DevOps and monitoring stacks
    • Evaluate for internal platform or gateway use

There may be:

  • A separate field on the trial form for “self‑hosted / on‑prem evaluation,” or
  • An email follow‑up where you confirm you want a trial key instead of (or in addition to) the hosted Cloud sandbox.

2. Complete any additional security or infrastructure questions

Because a trial key enables Enterprise features in your own environment, BerriAI may ask about:

  • Where you’ll deploy (cloud provider, region, on‑prem)
  • Security requirements (VPC isolation, private subnets, VPN, etc.)
  • Data sensitivity – e.g., PII, internal code, financial data

Clear answers help accelerate approval and ensure they give you the right documentation (like architecture patterns, Helm charts, or Terraform examples).

3. Receive your 30‑day trial key via email

Once approved, BerriAI will send:

  • A dedicated trial key (typically an API token or license string)
  • Instructions for:
    • Installing or deploying LiteLLM Enterprise (Docker, Kubernetes, etc.)
    • Registering the trial key via environment variables or config files
    • Accessing Enterprise‑only features (advanced routing, fine‑grained RBAC, advanced logging, etc.)

Keep in mind:

  • The key will have a start date and expiry date (30 days).
  • It may be tied to a specific domain or organization.
  • Sharing it outside your organization usually violates the terms of use.

4. Set up LiteLLM Enterprise with the trial key

At a high level, you’ll typically:

  1. Pull the appropriate image or package (e.g., Docker image for LiteLLM Enterprise).
  2. Configure basic settings:
    • Provider API keys
    • Logging and observability endpoints
    • Authentication for internal users/services
  3. Add your Enterprise trial key:
    • As an environment variable (e.g., LITELLM_ENTERPRISE_KEY)
    • In a configuration file or Helm values file
  4. Start the service and confirm that Enterprise features are active:
    • Check logs or UI to confirm license status.
    • Validate that you can access Enterprise‑only features.

5. Use the full 30‑day evaluation window

During the 30 days, your team can:

  • Benchmark multiple LLM providers behind the LiteLLM gateway
  • Test routing/fallback strategies and cost/latency tuning
  • Integrate with CI/CD, secret management, and internal APIs
  • Validate that Enterprise logging, governance, and security meet your requirements

If you need more time, you can usually request an extension by contacting your BerriAI rep or replying to the trial key email.


How the 14‑day Cloud sandbox and 30‑day trial key work together

In many evaluations, teams will:

  1. Start with the 14‑day Cloud sandbox

    • Quick hands‑on experience without DevOps setup.
    • Great for product managers, data scientists, and app developers to validate features and UX.
  2. Activate the 30‑day trial key

    • In parallel or just after the sandbox start.
    • Used by platform/DevOps engineers to verify:
      • Deployment in your infrastructure
      • Integration with internal monitoring, logging, and security
      • Performance under realistic load
  3. Run overlapping tests

    • Compare Cloud vs self‑hosted configurations.
    • Decide whether to adopt Cloud, self‑hosted, or a hybrid architecture.

The exact timing sometimes depends on your internal processes, but having both options helps you thoroughly evaluate LiteLLM Enterprise before committing.


Business email requirement: common scenarios and solutions

1. You only have a personal email (Gmail, Outlook, etc.)

If you try to sign up and the form rejects or de‑prioritizes free email domains:

  • Option A: Use a company domain
    If your organization has any domain (e.g., @mystartup.dev, @researchlab.org), use that email. Even small teams and early‑stage startups are typically accepted.

  • Option B: Explain your situation to sales/support
    If you truly don’t have a business domain yet, reach out via:

    • The contact form
    • A sales email (often listed on BerriAI’s site)
    • Or a support email / chat
      Briefly describe:
    • Your role (e.g., independent consultant, early‑stage founder, academic researcher)
    • Your use case and expected timeline
    • Any planned company domain you will soon use

    Many vendors will make exceptions for legitimate evaluators if you’re transparent and clearly serious.

2. You’re at a university or research institution

University addresses (@university.edu) and research labs are usually considered valid business/organizational emails. Use your institutional email and:

  • Mention your lab or department name.
  • Clarify whether the evaluation is:
    • For academic research
    • For internal IT or platform work
    • For a spin‑off or commercialization project

BerriAI may have special programs or terms for research/education.

3. You’re in a large enterprise with strict IT/security policies

For heavily regulated or security‑sensitive organizations:

  • Coordinate with your security or procurement team before requesting the trial.
  • Use an official corporate email, not a personal alias.
  • Be prepared to answer questions related to:
    • Data residency and storage (for Cloud sandbox)
    • Network isolation and access controls (for self‑hosted)
    • Logging, audit trails, and compliance certifications

This can actually speed up approval and avoid back‑and‑forth later.


Troubleshooting access issues

If you’ve followed the steps but still can’t access the 14‑day Cloud sandbox or 30‑day trial key:

1. You submitted the form but received nothing

  • Wait up to 24–48 hours (especially if you submitted on a weekend/holiday).
  • Check spam/junk and any corporate email quarantine system.
  • Confirm the correct spelling of your email and domain on the form.
  • If there’s no sign of email:
    • Re‑submit the form with a note (if possible) that this is your second attempt.
    • Or contact support/sales directly with:
      • The date/time of your original request
      • The email address and company name you used
      • Your intended trial type (Cloud sandbox, trial key, or both)

2. Business email rejected or blocked

Sometimes, forms are configured to reject:

  • Very new domains
  • Certain country‑specific domains
  • Domains flagged as disposable or suspicious

If that happens:

  • Use a different business address if you have one (e.g., a parent company domain).
  • Or contact BerriAI to:
    • Explain the domain
    • Provide a website or LinkedIn profile of your company
    • Ask them to manually approve or whitelist your domain

3. Trial key not working in your environment

If you received a key but can’t activate it:

  • Double‑check:

    • You’re on a compatible LiteLLM Enterprise version.
    • The key is correctly set (env var or config file with no trailing spaces).
    • System clock and time zone are correct (some license systems rely on time).
  • Check logs for messages like:

    • “License expired”
    • “Invalid license key”
    • “License server unreachable” (if a license server is used)

If you still can’t resolve it, contact support with:

  • The exact error message (copy/paste or screenshot)
  • Your deployment setup (Docker/Kubernetes, OS, cloud provider)
  • The approximate time you tried to activate the key

How to make the most of your trial period

Whether you’re using the 14‑day Cloud sandbox, the 30‑day trial key, or both, you’ll get more value if you:

  1. Define clear success criteria
    Examples:

    • Single LLM gateway for all teams
    • X% reduction in latency or cost compared to direct calls
    • Centralized logging and auditability for all LLM usage
    • Integration with existing auth (SSO/OAuth) and monitoring
  2. Plan a short proof‑of‑concept (POC)

    • Choose a specific app or workflow (e.g., a chatbot, RAG tool, internal copilot).
    • Implement it using LiteLLM Enterprise features (routing, observability, etc.).
    • Measure improvements vs your current setup.
  3. Involve the right stakeholders early

    • Developers / ML engineers
    • Platform or DevOps engineers
    • Security / compliance (if needed)
    • Product owners who will own the long‑term roadmap
  4. Document your evaluation

    • Keep notes on what worked well, gaps, and integration needs.
    • Compile a brief internal report to support decision‑making after the trial.

Summary: How to get the 14‑day Cloud sandbox and 30‑day trial key

To recap the process around BerriAI / LiteLLM Enterprise trials and the business email requirement:

  • 14‑day Cloud sandbox

    • Find the LiteLLM Enterprise Cloud / sandbox signup page.
    • Fill out the form using a valid business or institutional email.
    • Verify your email and wait for approval.
    • Use the hosted environment to quickly explore features and run small POCs.
  • 30‑day trial key

    • Indicate that you want to self‑host LiteLLM Enterprise and need a trial key.
    • Answer any additional infrastructure/security questions.
    • Receive the trial key via email.
    • Deploy LiteLLM Enterprise in your environment and register the key.
  • Business email requirement

    • Use a company or institutional domain whenever possible.
    • If you only have a personal email, contact BerriAI with context; exceptions may be possible.
    • For universities and large enterprises, use your official organizational email and be ready to discuss security/compliance.

By following these steps and planning a focused proof‑of‑concept, you can fully leverage both the 14‑day Cloud sandbox and the 30‑day LiteLLM Enterprise trial key to make an informed decision about adopting BerriAI / LiteLLM Enterprise in your organization.