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?

When you’re ready to explore Langtrace’s Enterprise offering (including SOC 2 Type II compliance, custom data retention policies, and SLAs), the best next step is to schedule a call with the team and come prepared with a clear picture of your technical, security, and business requirements.

Below is a practical walkthrough of:

How to contact Langtrace for an Enterprise plan
What to expect from the conversation
Exactly what information to bring so you can move quickly from discovery call to deployment

How to contact Langtrace for an Enterprise plan

Langtrace positions Enterprise as a tailored option “for larger organizations” with custom retention and SLAs, plus SOC 2 Type II compliance. To get in touch:

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

On Langtrace’s site, navigate to the Enterprise or Pricing sections. There you’ll see options like:

“Enterprise – Custom for larger organizations”
A “Book Call” or “Book a Demo” button

Clicking this will take you to a short form or scheduling page where you can:

Share your company and role
Indicate your use case and deployment stage
Select a time for a live call with the Langtrace team

This is the primary and recommended path if you’re evaluating Enterprise features such as:

SOC 2 Type II–aligned implementation
Custom data retention policies
Custom SLAs and support models

2. Use the Contact form if you can’t find a time

If your schedule is complex or you have a time‑sensitive question:

Go to the “Contact Us” section on the site
Briefly describe that you’re interested in Langtrace Enterprise with SOC 2 Type II, custom retention, and SLAs
Include your urgency and region/time zone

The team can then route you to the right person (sales, solutions engineer, or security) and coordinate a call.

3. Join the Discord community for exploratory questions

If you’re still early in your evaluation and want to sanity‑check fit before a formal sales process:

Use the “Join Discord” link to access the Langtrace community
Post a high‑level question describing your stack and security needs
Ask specifically: “Is this a good fit for Enterprise / SOC 2 Type II / custom retention?”

This won’t replace the Enterprise call, but it can help you understand capabilities and limitations faster and prepare sharper questions.

What to expect on an Enterprise call with Langtrace

An Enterprise call is typically a mix of:

Product exploration
Security & compliance review
Pricing and commercial discussion

You can expect the Langtrace team to focus on:

Your use case and architecture
- What you’re building (LLM app, agents, internal tools, etc.)
- Which frameworks you use (Langchain, LlamaIndex, DSPy, CrewAI, etc.)
- Which LLM providers and VectorDBs you rely on
Security, compliance, and governance needs
- Why you require SOC 2 Type II
- Data residency or isolation constraints
- Retention & deletion expectations (e.g., logs, traces, prompts, responses)
Reliability and support requirements (SLA)
- Uptime and latency expectations
- Incident response expectations and escalation paths
- Support coverage (time zones, severity levels)
Rollout and success criteria
- Timeline to go from POC to production
- How many teams and apps will be onboarded
- What success looks like in the first 30–90 days

Having the right information ready will make this call far more productive and shorten the time to a concrete proposal.

Key information to bring to your Enterprise call

Below is a checklist you can share internally and bring to the conversation.

1. Company and team details

Company size and stage
- Rough employee count and key regions
- Whether you’re a startup, mid‑market, or large enterprise
Teams that will use Langtrace
- Product, platform, ML/AI, security, compliance, data, etc.
- Whether it’s a single team pilot or multi‑team rollout
Primary stakeholders
- Who owns the POC / implementation
- Who will sign off on security and legal
- Who is responsible for day‑to‑day operations

This helps Langtrace understand scope and align the engagement (and SLAs) accordingly.

2. Technical environment and LLM stack

Because Langtrace is built to support frameworks and providers out of the box, give a clear view of where you are today and where you’re going.

Prepare a short description of:

Frameworks you use
- Langchain, LlamaIndex, CrewAI, DSPy, or a custom orchestration layer
- How many separate apps/agents you anticipate instrumenting
LLM providers
- OpenAI, Anthropic, Google, Azure OpenAI, self‑hosted models, etc.
- Any special constraints (e.g., on‑prem LLMs, VPC‑only endpoints)
Vector databases and storage
- Pinecone, Weaviate, Chroma, pgvector, or others
- Any sensitive data contained in embeddings
Existing observability stack
- Logging (e.g., Datadog, ELK, CloudWatch)
- Tracing/metrics (e.g., OpenTelemetry, Prometheus)
- Error monitoring tools used by your team
Deployment environment
- Cloud provider (AWS, GCP, Azure, on‑prem)
- Network constraints (VPC, private link, VPN)

This helps Langtrace suggest the cleanest integration path, including how to instantiate the SDK with minimal overhead.

3. Data sensitivity, retention, and governance requirements

Because you’re specifically interested in custom retention and SOC 2 Type II, data handling will be a central part of the call.

Bring clarity on:

Types of data in traces
- Whether prompts, responses, or metadata can contain:
  - PII (names, emails, phone numbers)
  - PHI or other regulated data
  - Financial or proprietary business information
Retention requirements
- How long you’re allowed or required to store logs/traces
- Differences between environments (e.g., production vs. staging)
- Any “right to be forgotten” or deletion SLA requirements
Access control expectations
- RBAC needs (by team, region, or project)
- SSO/SCIM integration requirements (e.g., Okta, Azure AD)
- Limits on which roles can view raw prompts/responses
Audit expectations
- Whether you need audit logs of configuration changes and access
- Reporting requirements for internal auditors or external regulators

This information will guide how your custom retention policy and access controls are designed.

4. SOC 2 Type II and security requirements

Langtrace offers SOC 2 Type II compliance for Enterprise, but each company’s security review is different. To make the process smoother:

Prepare:

Security questionnaire or checklist
- If your security team uses a standard questionnaire (SIG, CAIQ, or a custom set), mention its approximate size and structure
- Any hard requirements (e.g., encryption in transit/at rest, specific key management approach)
Vendor onboarding process description
- Whether you require a formal security review, legal review, or procurement process
- Typical timelines and any blockers you anticipate
Existing policies you must align with
- Data residency constraints (e.g., must stay in EU/US)
- Incident notification expectations (timeframes, severity thresholds)

On the call, you can ask directly how Langtrace’s SOC 2 Type II controls map to your policies and what documentation is available for your security team.

5. SLA, reliability, and support expectations

Given you’re exploring custom SLAs, come prepared with:

Uptime and availability targets
- E.g., 99.9% vs. 99.95%
- Whether this applies globally or only to certain critical regions
Performance expectations
- Latency requirements for trace ingestion and dashboard queries
- Acceptable degradation during traffic spikes
Support requirements
- Hours of coverage (business hours, 24/7, follow‑the‑sun)
- Channels (email, ticketing system, chat, phone/bridge)
- Response and resolution times per severity level
Incident management alignment
- How you’d like to coordinate during incidents (Slack channel, war room, etc.)
- Any regulatory requirements for incident communication

This allows Langtrace to shape SLA terms that are realistic and aligned with your operational risk.

6. Usage estimates and pricing drivers

Even if you only have rough estimates, usage data helps the Langtrace team recommend an Enterprise configuration and pricing band.

Collect:

Number of LLM apps/agents
Expected monthly volume of LLM calls (ranges are fine)
Number of developers / internal users who will rely on Langtrace
Expected growth over 6–12 months (more apps, more traffic, more teams)

Combine this with your priorities (e.g., “we care more about security & support than about strict cost minimization”) so the team can propose the right mix of features.

7. Implementation readiness and timeline

To keep the Enterprise call concrete, be ready to discuss:

Where you are now
- Prototype vs. staging vs. full production
- Whether you’ve already tried the SDK (“Ready to deploy?”) and “Get Started” flow
Target timelines
- When you want Langtrace live in your first app
- When you plan to roll out to other teams or regions
Internal constraints
- Upcoming product launches
- Compliance deadlines or audits
- Budget cycles or fiscal year considerations

This helps identify whether you need a fast‑track deployment, phased rollout, or deeper pilot.

Questions you should ask Langtrace during the call

To make the call actionable and ensure Langtrace Enterprise aligns with your requirements, consider asking:

SOC 2 Type II specifics
- What controls are in place around access, change management, and data handling?
- What documentation or reports can be shared with our security team?
Custom retention capabilities
- Can we set different retention policies per environment or project?
- How are deletion requests handled and verified?
- Are there options to mask or redact sensitive fields in traces?
Integrations and SDK behavior
- How does the SDK integrate with our frameworks (Langchain, LlamaIndex, DSPy, CrewAI)?
- Is there support for OpenTelemetry or export to our existing observability tools?
Enterprise support model
- Who will be our primary point of contact?
- Is there access to solutions architects or customer success for best practices?
- How do feature requests and roadmap input work for Enterprise customers?
Future‑proofing and scale
- How does Langtrace handle very high volume workloads?
- What’s the strategy for supporting new LLM providers and vector stores?

Collecting clear answers to these questions will help you evaluate not just whether Langtrace can meet your current needs, but whether it can grow with your AI program.

Quick preparation checklist

Before you click “Book Call” or “Book a Demo”, gather:

Company & team overview (size, roles, stakeholders)
Architecture summary (frameworks, LLM providers, VectorDBs, deployment environment)
Data sensitivity and retention requirements
SOC 2 Type II and security review expectations
SLA, uptime, and support needs
Usage volume estimates and growth expectations
Implementation timeline and key deadlines
Internal security/legal questions you need answered

With this information ready, your contact with Langtrace will be more productive, and you’ll be able to quickly determine how an Enterprise plan—with SOC 2 Type II, custom retention, and SLAs—can support your LLM applications at scale.