Element34
Deployment · Managed Private Cloud

Single-tenant. Operated for you.

Element34 operates a private, isolated environment dedicated to you. Single-tenant deployment, region-pinned, dedicated VPC, 24x7 SLA. Your team focuses on tests. Element34 keeps the platform running.

  • Region-pinned
  • 24x7 SLA
Operated by
Element34
Hands-off
For your team
Selenium Box · Managed Private Cloud
Operations dashboard
🔒 grid.private.yourcorp Element34-operated
Customer · single-tenant instance
eu-central-1 · region-pinned
Uptime
99.95%
Patch SLA
On track
Incidents
0 open
Capacity
62% used
Element34 operations · live activity
Patch applied · CVE-2026-40175 fix to v5.2.2 2h ago
Backup verified · session metadata + config 6h ago
Capacity scaled · +10 Executors (peak window) 12h ago
Upgrade scheduled · v5.2.3 next maintenance window 3d
Monitoring · 24x7 on-call engineer assigned live
Hands-off for your team Audit-logged access Region-pinned
Element34 operations activity Customer-visible audit log
Mid-market financial services
Predictable cost, predictable scale

Annual subscription, single-tenant infrastructure, no per-execution metering. Mid-market financial services buyers see exactly what they pay every year.

Predictable spend
MedTech & Healthcare SaaS
Run HIPAA-aligned without a platform team

Mid-market healthcare and MedTech get HIPAA-aligned single-tenant infrastructure without standing up a platform team to operate it.

HIPAA-aligned
Regional & Municipal Government
Run in your sovereign region, we operate it

Region-pinned to customer-mandated jurisdiction. EU, Switzerland, UK, US regions on request. Element34 operates inside the boundary the customer specifies.

Region-pinned
Existing SBOX customers
Drop the operations burden

Customers currently running self-hosted SBOX can transition to Managed for the operational tier-up. Migration handled by Element34 customer success.

Migration supported
The operations burden

Enterprise infrastructure without an enterprise infrastructure team.

Self-hosted SBOX gives the customer total control. It also gives the customer total operations. Patches. Upgrades. Capacity. Incident response. Backups. Monitoring. Mid-market teams want enterprise-grade testing infrastructure and do not want to staff a platform-engineering team to operate it. Managed Private Cloud is the answer.

Pain pattern 01

Operations crowd out the QA team

Symptom. The customer wants enterprise infrastructure but has no platform team. Patches slip. Upgrades stall. Sessions hang. The QA team becomes the unwilling on-call rotation.

Managed response Element34 operations team handles patches, upgrades, capacity scaling, backups, monitoring, and incident response. Customer QA team focuses on tests.
Pain pattern 02

SaaS blocked, self-hosting impossible

Symptom. Security review blocked public SaaS testing. Customer cannot stand up a self-hosted platform either. Stuck between two no-options.

Managed response Single-tenant, customer-isolated environment operated by Element34. Same compliance posture as Private Cloud, with Element34 doing the operations work.
Pain pattern 03

Critical CVE consumes the weekend

Symptom. A critical CVE drops Friday afternoon. The customer team has to triage, test, patch, and deploy before Monday. Nobody has the bandwidth.

Managed response Element34 publishes the patch, tests it across the Managed fleet, and applies it during the SLA maintenance window. Customer team gets a notification, not a fire drill.
What Element34 operates

Element34 owns the operations work end to end.

Managed Private Cloud is single-tenant infrastructure operated by Element34. Six operational responsibilities are included in the annual subscription. Customer team focuses on writing and running tests.

Responsibility 01

Platform patching

Security patches, browser updates, OS updates, dependency updates. Applied during SLA maintenance windows. Customer notified, customer does not action.

Responsibility 02

Version upgrades

SBOX major and minor version upgrades. Element34 tests each release in a staging environment that matches customer production, then applies to customer.

Responsibility 03

Capacity scaling

Executor count, Hub count, and storage scale with customer usage. Element34 monitors capacity headroom and adjusts ahead of demand. Customer notified, customer does not action.

Responsibility 04

Backup and restore

Session metadata, configuration, and customer data backed up to customer-region-pinned storage. Restore SLA documented in contract.

Responsibility 05

Monitoring and incident response

24x7 monitoring against the SLA. On-call Element34 engineer responds within contracted time targets. Customer gets a status page, not a pager.

Responsibility 06

Customer success & engineering

Customer-facing engineer assigned. Quarterly review of test infrastructure health. Roadmap input session. Migration support if the customer changes deployment model.

SLA structure

SLA targets sized to your deployment, monitored 24x7.

SLA targets are documented in the customer contract. The categories below show how the SLA is structured. Specific time targets and uptime numbers are scoped per customer and not published publicly.

SLA · Uptime

Customer instance availability over the contractual reporting period.

SLA · Incident response

Time from incident detection to Element34 engineer acknowledging.

SLA · Incident resolution

Time from acknowledgement to platform recovered, by severity class.

SLA · Patch SLA

Time from CVE publication to patch applied to customer Managed instance.

SLA · Maintenance window

Customer-region-aligned timing for platform changes that require downtime.

Specific SLA numbers are negotiated per customer based on scope. Talk to sales for the SLA terms that apply to your deployment.

Three deployment models

Pick the deployment model that matches your operating model.

Same SBOX product runs across all three. Managed Private Cloud is the model where Element34 operates the platform for you.

Dimension
Private Cloud
VPC
Managed
(this page)
Where it runs
Customer-owned infrastructure
Customer cloud account
Element34-operated, customer-isolated environment
Who operates it
Customer operates everything
Customer cloud team operates, Element34 provides templates
Element34 operates with 24x7 SLA
Best fit
Hard data residency, in-house mandate, air-gap
Cloud-first mandate, single-tenant, sovereign-cloud regions
Want enterprise testing infrastructure without operating it

See the full compare deployments page →

Security and isolation

Same security posture as self-hosted. We take the operations.

Managed Private Cloud inherits the SBOX security architecture. The deployment is single-tenant, customer-isolated, region-pinned. The difference from Private Cloud is who operates it, not what gets protected.

Single-tenant per customer

No shared infrastructure between customers. No multi-tenant control plane. Element34 isolates each customer in a dedicated environment.

Region-pinned to mandate

Customer specifies the region. Element34 operates inside it. Data, processing, and backups stay region-pinned.

Optional VPN or PrivateLink

Customer can require PrivateLink, VPN, or IP allowlist for SBOX access. Element34 operations work happens through Element34's own secure-jump path, audit-logged.

Customer-controlled retention

Video, screenshots, and session metadata retention follow customer-defined policies. Backups follow customer-defined schedule.

Audit-visible Element34 access

Every Element34 operations action against the customer instance is audit-logged. Customer can review the operations log at any time.

Managed Private Cloud FAQ

Managed Private Cloud, answered.

What is Managed Private Cloud for Element34 SBOX?
Managed Private Cloud is the deployment model where Element34 operates a single-tenant, customer-isolated SBOX environment dedicated to one customer. Customer team writes and runs tests. Element34 handles platform patching, version upgrades, capacity scaling, backups, monitoring, incident response, and customer success.
Is Managed Private Cloud single-tenant?
Yes. Every Managed Private Cloud deployment is single-tenant per customer. No shared infrastructure between customers. No multi-tenant control plane. Element34 isolates each customer in a dedicated environment.
Where does Element34 operate the Managed environment?
Region-pinned to customer mandate. Element34 operates inside the region the customer specifies. EU, Switzerland, UK, US, and other regions on request. Sovereign-cloud regions supported where Element34 has authorization.
How does the SLA work?
SLA categories include uptime, incident response, incident resolution, patch SLA, and maintenance windows. Specific time targets and uptime numbers are negotiated per customer based on scope. Talk to sales for the SLA terms that apply to your deployment.
Can Element34 access customer test data?
Element34 operations work happens through a secure-jump path that is audit-logged. Every Element34 action against the customer instance is logged and visible to the customer. Customer can review the operations log at any time.
What is included in the annual subscription?
Single-tenant infrastructure, all licensed SBOX modules, 24x7 monitoring, incident response per SLA, platform patching, version upgrades, capacity scaling, backups, restore capability, and customer-success engineer support.
Can a customer migrate from Private Cloud or VPC to Managed Private Cloud?
Yes. Customer success engages on the migration. Test scripts, session history, configuration, and user identity migrate with the customer. Element34 handles the operational handoff. Same SBOX product, different operational tier.

We run the platform. You ship the tests.

Send us the region, the SLA targets you need, and the team size. We scope the Managed Private Cloud subscription, stand it up, and operate it. Annual subscription, predictable across the contract term.