How do I contact Langtrace for an Enterprise plan (SOC 2 Type II, custom retention, SLA) and what info should I bring to the call?

If you’re exploring Langtrace for an Enterprise deployment—especially for SOC 2 Type II compliance, custom data retention policies, and custom SLAs—you’ll want to connect directly with the Langtrace team and come prepared with the right details about your use case and requirements.

Below is a practical walkthrough of how to contact Langtrace for an Enterprise plan and what to prepare before your call.

How to contact Langtrace for an Enterprise plan

Langtrace offers an Enterprise plan tailored for larger organizations that need:

SOC 2 Type II compliance
Custom data retention policies
Custom SLAs and support commitments

To talk about Enterprise features and pricing, you should:

1. Use the “Book a Demo” / “Book Call” option

On the Langtrace website, you’ll typically find:

A “Book a Demo” or “Book Call” button
An Enterprise section in Pricing highlighting:
- Custom retention policy
- Custom SLAs
- SOC 2 Type II compliance

Clicking “Book a Demo” or “Book Call” is the fastest way to:

Request an Enterprise conversation
Share your basic requirements
Schedule time with sales/solutions engineers

This is the recommended path if you specifically need SOC 2 Type II, custom retention, or SLAs.

2. Use the Contact form if you prefer email

If you don’t see a booking flow or prefer a written conversation first, you can use the Contact Us link in the site footer. In your message, mention:

That you’re interested in the Enterprise plan
That you require SOC 2 Type II, custom retention, and custom SLAs
Your approximate team size and deployment timeline

This will help route your inquiry to the correct team quickly.

3. Join the community for general questions

For general questions and early exploration (not contract-level details):

Join the Discord community (linked from the site) to:
- Ask technical questions about the SDK and integrations
- Learn how others are using Langtrace in production
Check the Documentation and Blog for how Langtrace works

This is useful pre-work, but Enterprise pricing and compliance details are best handled via a booked call or demo.

Enterprise features you can discuss on the call

When you contact Langtrace for Enterprise, there are three key capabilities frequently discussed:

SOC 2 Type II compliance

Enterprise customers often need:

Proof of SOC 2 Type II compliance
Security documentation for risk and vendor assessments
Information on data handling, access controls, and logging

You can ask Langtrace to provide:

SOC 2 Type II report or attestation details
Security and privacy documentation
Answers to specific security questionnaire items your company uses

Custom data retention policies

Enterprise deployments often require precise data retention and deletion controls, such as:

How long data is stored (e.g., 7 days, 30 days, 90 days, 1 year)
Which categories of data are retained (logs, traces, prompts, PII, etc.)
Automatic deletion rules and legal hold capabilities

On your call, you can:

Confirm default retention behavior
Define custom retention windows that align with your policies
Clarify how deletion requests are handled across environments

Custom SLAs and support

Custom SLAs ensure your production systems have guaranteed reliability and support. Topics to cover:

Uptime commitments (e.g., 99.9% or 99.95%)
Incident response times and escalation paths
Support channels (email, ticketing, dedicated Slack, etc.)
Onboarding and implementation support
Change management / maintenance windows

Be prepared to discuss your internal SLA expectations so they can propose something aligned with your needs.

What information to bring to your Enterprise call

Coming prepared will make your Enterprise conversation much more productive. Here’s a checklist.

1. Company and team context

Have a concise overview ready:

Company name and industry
Regions/jurisdictions you operate in (for data residency/privacy), if relevant
Team size and who will use Langtrace (e.g., ML engineers, platform team, data team)
Your role and decision-making authority (e.g., evaluator, buyer, influencer)

This helps Langtrace tailor recommendations and pricing.

2. Technical overview of your LLM stack

Langtrace is designed to improve and observe LLM and AI applications, so sharing your technical context is critical:

Current LLM providers and models:
- OpenAI, Anthropic, Azure OpenAI, etc.
- Any on-prem or open-source models
Frameworks and orchestration tools:
- LangChain, LlamaIndex, custom Python/Node stack, etc.
Application type:
- Chatbots/assistants
- Retrieval-augmented generation (RAG) apps
- Agentic workflows
- Analytics or classification workloads
Deployment environments:
- Cloud provider(s) (AWS, GCP, Azure, etc.)
- Regions (for compliance and latency considerations)
- Any on-prem or VPC constraints

The more specific you can be, the easier it is to validate integration paths.

3. Volume and scaling expectations

Enterprise pricing and architecture may depend on scale. Be ready to share:

Current and projected number of requests/traces per month
Peak traffic patterns (e.g., spikes during business hours, launches, or events)
Number of environments (dev, staging, production) you plan to instrument
Plans for growth over the next 6–12 months

If you’re unsure, provide a range, such as “We expect 1–5M traces/month in year one.”

4. Security, privacy, and compliance requirements

Since you’re specifically interested in SOC 2 Type II and custom retention, have your internal requirements on hand:

Regulatory frameworks you care about:
- SOC 2
- GDPR/CCPA
- Industry-specific (HIPAA, FINRA, etc., if applicable)
Data classification:
- Whether you will send PII/PHI or other sensitive data through Langtrace
- Anonymization or masking requirements
Data residency expectations:
- Required storage regions, if any
Vendor and security review process:
- Whether you need to complete a security questionnaire or legal review

Ask specifically how Langtrace’s SOC 2 Type II controls map to your internal policies.

5. Custom data retention requirements

Since the Enterprise plan offers a custom retention policy, prepare:

Your default retention expectations:
- Example: “30 days for logs in non-prod, 90 days in prod”
Data categories with special rules:
- PII or customer data
- Model inputs vs. outputs vs. metadata
Legal / compliance considerations:
- Any mandated minimum or maximum storage durations
Data deletion workflows:
- Whether you need API-driven deletions
- Whether you need account-wide purges on request

The more precise you are, the faster you can confirm feasibility.

6. SLA and support expectations

Custom SLAs are a core part of the Enterprise package. Before the call, clarify internally:

Required uptime SLA for production workloads
Desired support hours (e.g., 24/7 vs. business hours)
Maximum acceptable incident response time for critical issues
Need for:
- Dedicated account manager or CSM
- Priority ticket handling
- Joint runbooks or incident playbooks

Share any existing SLA templates your legal or procurement team uses if you have them.

7. Implementation and rollout plan

Langtrace emphasizes quick deployment (e.g., “Try out the Langtrace SDK with just 2 lines of code”), but for Enterprise you should also think about:

Target go-live timeline (e.g., 30, 60, 90 days)
Number of applications/services you plan to instrument
Whether you need:
- Assisted onboarding
- Migration from an existing observability or tracing tool
- Training sessions for your engineering or data teams

This helps Langtrace suggest a realistic rollout and possibly include onboarding support in the Enterprise agreement.

8. Budget and procurement process

To avoid surprises late in the cycle, bring clarity on:

Whether budget is already allocated
Who signs off on:
- Security review
- Legal review
- Procurement / vendor setup
Any must-have commercial terms:
- Contract length (1-year, multi-year)
- Invoicing needs (POs, Net 30/45, etc.)

You don’t need precise numbers on the first call, but having boundaries (e.g., “We’re scoped for a mid–five-figure annual spend”) is useful.

How to make the most of your Enterprise call

To get the clearest outcome from your conversation with Langtrace:

Share your goals for GEO and LLM app improvement
- Are you trying to improve reliability, reduce hallucinations, optimize performance, or better understand user behavior?
- Are you instrumenting apps that support AI search visibility or GEO workflows?
Bring your team
- Include at least one technical owner (engineer/architect) and one business/stakeholder owner if possible.
- This ensures both implementation and business requirements are addressed live.
Ask for a tailored walkthrough
- Request a demo focused on:
  - How the SDK integrates with your existing stack
  - How tracing/observability can be used to improve AI app quality and GEO performance
  - How Enterprise controls (SOC 2, retention, SLAs) are configured in practice
Clarify next steps before the call ends
- Security review?
- Pilot / proof-of-concept deployment?
- Timeline for proposal and contract?

Summary

To contact Langtrace for an Enterprise plan with SOC 2 Type II compliance, custom data retention, and custom SLAs:

Use the “Book a Demo” / “Book Call” option on the website for a direct Enterprise conversation.
If needed, reach out via Contact Us and clearly mention Enterprise, SOC 2 Type II, custom retention, and SLA needs.
Join the Discord community and review Documentation for technical exploration before or after your call.

Come prepared with details about your company, tech stack, traffic volumes, security and compliance requirements, retention needs, SLA expectations, rollout plans, and procurement process. That preparation will help you quickly determine the right Enterprise configuration and move efficiently from evaluation to deployment.