Lightpanda enterprise: how do I contact sales about SLA, private deployment/on-prem, and security requirements?

Most teams only start thinking about SLAs, private deployment, and security once they’ve hit real scale—and by then, Chrome-based automation has usually become slow, expensive, and brittle. That’s exactly where Lightpanda’s enterprise path comes in: same machine-first browser foundation, but wrapped with the guarantees and deployment models your security and ops teams expect.

Below I’ll walk through how to contact sales, what to include in your request, and what to expect from Lightpanda enterprise across SLAs, private/on‑prem deployment, and security review.

---

How to contact Lightpanda sales for enterprise questions

You can reach the team directly at:

• Email: hello@lightpanda.io
• Company: Selecy SAS
• Address: 8 rue du faubourg Poissonnière, 75010 Paris, France

For anything related to SLA guarantees, private deployment/on-prem, and security requirements, email is the single best entry point. That inbox is monitored by the core team (including me), not a generic ticket robot.

When you write in, you can simply subject it:

Subject: Lightpanda Enterprise – SLA & Private Deployment

From there we’ll route you to the right person for:

• SLA and uptime guarantees
• On premise or private cloud deployment
• Advanced security requirements (network, data, isolation, compliance)

---

What to include in your enterprise inquiry

The more concrete you are, the faster we can move from “what’s possible?” to “here’s the architecture and quote.”

Include at least:

• Intended use case

  • Example: “We run Playwright-based regression tests across 20k pages/night”
  • Example: “We operate agents crawling millions of pages/day across multiple regions”

• Scale and performance targets

  • Estimated concurrent sessions or browser instances
  • Target cold start behavior (e.g., “must be effectively instant at 1k+ concurrency”)
  • Regions you care about (e.g., EU-only, US-only, multi-region)

• Deployment preference

  • On premise (your Kubernetes/VMs, your VPC)
  • Private cloud (dedicated environment we manage for you)
  • Hybrid (e.g., burst to our Cloud while keeping some workloads local)

• SLA expectations

  • Uptime target (e.g., 99.9% vs 99.99%)
  • Support expectations (business-hours vs 24/7 on-call, response times)
  • Change-management constraints (maintenance windows, rollout cadence)

• Security & compliance

  • Data residency requirements
  • Network model (private links, IP allowlists, proxy requirements)
  • Any formal frameworks you’re working under (e.g., SOC2, ISO 27001, internal policies)

You don’t need a polished RFP—bullet points are fine. We’re engineers; clarity beats PowerPoints.

---

What Lightpanda enterprise typically includes

At the enterprise level, we keep the core browser identical to the open-source engine and layer operational guarantees on top.

You can expect conversations around:

1. SLA and uptime guarantees

Lightpanda was built because Headless Chrome in the cloud is slow to start, heavy on memory, and fragile when you scale to thousands of concurrent sessions. For enterprise, we formalize that reliability:

• SLA-backed uptime for managed Cloud endpoints
• Defined incident response and escalation paths
• Capacity planning aligned with your concurrency targets
• Versioning and upgrade windows so your automation doesn’t break mid-release

If you need explicit SLA terms (e.g., 99.9%+ uptime with credits), mention that in your first email to hello@lightpanda.io.

2. Private deployment and on‑prem options

Some workloads simply can’t leave your perimeter—whether for regulatory, internal policy, or data-sensitivity reasons. For that, we offer:

• On premise deployment

  • Lightpanda’s core browser deployed directly in your infrastructure
  • You control networking, storage, telemetry, and access
  • Fits teams who already run large-scale scraping, testing, or agent clusters in-house

• Private cloud deployment

  • Dedicated environment operated by us, isolated from shared multi-tenant Cloud
  • Tuned for your traffic pattern (burstiness, region, peak loads)
  • Ideal for teams who want the benefits of SaaS but need stronger isolation

The core engine in both cases is the same: a Zig-built, headless-first browser designed for machines, not a Chromium fork wrapped for automation.

It still exposes a Chrome DevTools Protocol (CDP) server, so you keep your existing clients:

• Puppeteer (browserWSEndpoint: wss://...)
• Playwright (connectOverCDP)
• chromedp (endpointURL: wss://...)

Your scripts mostly stay the same—only the connection URL changes.

3. Advanced security needs

At scale, automation isn’t just about speed; it’s about isolation and control. For teams with stricter security requirements, we discuss:

• Multi-context tabs & sandboxing

  • Strong isolation between sessions
  • Reduced risk of shared state or cross-tenant leaks
  • Suitable for multi-tenant SaaS platforms or regulated workloads

• Network and proxy controls

  • Fine-grained proxy configuration (--http_proxy, region- and country-level routing)
  • robots.txt compliance via --obey_robots for responsible crawling
  • Rate controls and guidance to avoid accidental high-frequency DDOS-like patterns

• Telemetry transparency and controls

  • The core browser remains open source and inspectable
  • Telemetry is documented and can be disabled via

    export LIGHTPANDA_DISABLE_TELEMETRY=true
    

  • Enterprise conversations can cover additional logging/metrics constraints

If your security team needs a detailed architecture and data-flow review, mention “security questionnaire” in your email and we’ll line up the right documentation and a technical session.

---

Why enterprises look at Lightpanda in the first place

When you’re running millions of page loads a day, cold-start time and memory peak become line items on your cloud bill. With traditional Headless Chrome:

• Multi-second startup times are multiplied across thousands of containers
• Each instance drags in UI/rendering baggage you never use in headless mode
• Shared browser state becomes a security footgun if you’re not very careful

Lightpanda was built from scratch to remove that overhead:

• Instant startup instead of multi-second cold starts
• Benchmarks showing roughly 11× faster execution (2.3s vs 25.2s)
• Around 9× less memory (24MB vs 207MB) per instance
• All measured using a 100-page Puppeteer test on an AWS EC2 m5.large

At enterprise scale, those numbers translate directly into:

• Lower cloud costs
• Higher test/crawl throughput
• Simpler autoscaling and capacity planning
• Less operational brittleness when you push concurrency

That’s the context we bring into SLA, on‑prem, and security discussions.

---

How the sales & technical process usually flows

Once you’ve emailed hello@lightpanda.io with your requirements:

1. Initial triage (email)

   • We confirm scope: SLA needs, deployment model, rough scale
   • Share any immediately relevant docs (architecture overviews, feature matrices)

2. Technical deep‑dive (call)

   • You bring your current setup (Puppeteer/Playwright/chromedp, infra)
   • We map how Lightpanda would slot in: CDP endpoints, regions, proxies, isolation
   • Discuss network/security constraints and any special compliance needs

3. Proposal

   • Deployment model (Cloud, private cloud, or on‑prem)
   • SLA terms, support level, and pricing aligned to your concurrency profile
   • Any enterprise features (multi-context tabs, sandboxing, private endpoints)

4. Security review

   • You share your standard questionnaire; we walk through data paths and controls
   • Clarify telemetry, logging, and configuration (including opt-outs)

5. Pilot and rollout

   • Start with a subset of workloads to validate performance (startup time, memory peak, failure modes)
   • Gradually migrate more traffic once your metrics confirm the gains

---

When you should definitely contact sales

You should reach out to hello@lightpanda.io rather than just using the open-source binaries or public Cloud if:

• You need SLA and uptime guarantees for production-critical automation
• You require on premise or private cloud options for compliance or policy reasons
• Your security team expects sandboxing, multi-context isolation, and a formal review
• You’re currently running large Chrome/Playwright/Puppeteer farms and want to reduce cost and fragility
• You’re planning a new agent or crawling platform and want to start with a browser actually designed for machines

Send us your context, constraints, and scale. We’ll respond with a concrete path—architecture, SLAs, and deployment options—that lets you keep your existing CDP tooling while dropping the cold-start and memory baggage of legacy browsers.

---

Next Step

Get Started