Keep your test data in your own AWS
BYOC means Bring Your Own Cloud. Tests run inside your AWS account — traces, screenshots, and logs never leave your VPC. Full compliance control with zero vendor access.
Cut 45-minute suites to under 5 minutes — without sending your data off-premises.
TraceLoom distributes your Playwright tests across EC2 Spot instances inside your own AWS account. Full execution traces for every test. No vendor access to your data, ever.
$ traceloom run --workers 50
✓ Run #42 created (runId: r_8xq...)
⠋ Running... 847/847 passed, 16 failed
Results
──────────────────────────────────────────────────
863 total 847 passed 16 failed
Duration: 4m 12s
View traces: https://app.traceloom.io/runs/r_8xq Accepting design partners
Early-access teams get direct access to the engineering team, priority feature requests, and locked-in pricing.
TraceLoom is a BYOC (Bring Your Own Cloud) distributed Playwright testing platform.
It shards your end-to-end test suite across up to 50+ parallel EC2 Spot workers inside
your own AWS account, captures a full .trace.zip
for every test, and typically costs $0.20–$2.00 per run — 70–80% less than managed platforms.
BYOC (Bring Your Own Cloud) testing means your tests run entirely inside your own AWS account. Your source code, test artifacts, and execution traces never leave your infrastructure — there is no shared tenancy and no third-party data access. This matters for teams with data residency requirements, compliance obligations, or a preference for full infrastructure control.
Everything you need to run 1,000+ Playwright tests a day — without sending data off-premises.
BYOC means Bring Your Own Cloud. Tests run inside your AWS account — traces, screenshots, and logs never leave your VPC. Full compliance control with zero vendor access.
Distribute tests across EC2 Spot instances in parallel. Pay only for compute used — typically $0.20–$2.00 per run. Your AWS pricing, your EDP discounts.
Every test generates a full Playwright trace — DOM snapshots, network requests, console logs, screenshots. When a test fails, you debug with the complete execution record.
Smart sharding distributes tests using timing data from previous runs. Equal wall-clock time per worker, not equal test count. No manual configuration required.
Real-time fleet cost tracking to 4-decimal precision. Watch test progress live. Full cost transparency — no surprises on your AWS bill.
Connect a GitHub repo or upload a zip archive. TraceLoom auto-detects your playwright.config.ts, installs dependencies, and validates your test suite.
How it works
No agents to manage, no shared cloud to trust. Your tests run inside infrastructure you already own.
Deploy a CloudFormation stack into your own AWS account. Your VPC, your S3 bucket, your DynamoDB — no shared tenancy, no vendor access to your data.
One CloudFormation template. Works with any existing AWS account.
Connect a GitHub repo or upload a zip. TraceLoom auto-detects your playwright.config.ts, installs dependencies, and validates your test suite.
Supports GitHub, GitLab, Jenkins, CircleCI, and direct S3 upload.
TraceLoom shards your suite across EC2 Spot workers, captures a full execution trace for every test, and stores results in your S3 bucket. Open any failure in the Playwright trace viewer.
DOM snapshots, network logs, console output — every test, every run.
Why TraceLoom
GitHub Actions works for small suites. BrowserStack scales but your data leaves your network. TraceLoom gives you both — scale and data sovereignty on AWS Spot.
| GitHub Actions | BrowserStack | TraceLoom | |
|---|---|---|---|
| Setup time | Hours to days (YAML matrix config) | 30–60 min (vendor onboarding) | < 15 minutes (one CloudFormation stack) |
| Data ownership | GitHub's servers | BrowserStack's servers | Your AWS account |
| Cost at 1,000 tests/day | ~$300–600/mo (runner minutes) | ~$500–1,500/mo (parallel session pricing) | ~$50–300/mo (AWS Spot + from $79/mo platform) |
| Parallel workers | 20 jobs max (matrix strategy) | ✓ managed | ✓ 50+ workers |
| Full execution traces | ✗ | Partial | ✓ every test |
| Data residency | GitHub's infra only | ✗ data leaves your network | ✓ stays in your VPC |
| CI/CD integration | Native | ✓ | GitHub, GitLab, Jenkins, CircleCI |
Cost estimates based on publicly available pricing as of April 2026. Your actual costs will vary.
Estimated monthly spend based on publicly available pricing, April 2026.
Midpoint estimates shown. Actual costs depend on test volume, parallelism, and instance types.
Who it's for
These are the problems teams bring to TraceLoom. If you're running Playwright at scale, you've probably hit at least one.
CI is the bottleneck
"Our CI takes forever. Engineers stopped running the full suite because it takes 40 minutes. PRs queue up and regressions slip through."
TraceLoom shards your suite across 50+ Spot workers. A 500-test run finishes in under 5 minutes at $0.20–$2.00 per run — 70–80% less than managed platforms.
Security won't approve hosted testing
"Security won't let us use a hosted testing platform. Test traces contain URLs, credentials, and DOM snapshots — that data can't leave our network."
TraceLoom runs inside your AWS VPC. Traces stay in your S3 bucket. Revoke the IAM role and the connection is severed — no vendor data access, ever.
Testing platform costs too much
"We're paying BrowserStack way too much. $5,000+/month for parallel sessions and we still don't get full Playwright traces."
TraceLoom runs on your own EC2 Spot instances — no per-session pricing. Typical cost: ~$1.65 per 1,000 tests. Full .trace.zip for every run.
Pricing
All plans include BYOC — your tests run in your AWS account, not ours.
Free
$0
+ your AWS costs
Pro
$79/mo
+ your AWS costs
Scale
$299/mo
+ your AWS costs
Need more? Enterprise plans with custom infrastructure and SLA available. See all plans →
Example: 847 tests across 50 workers = $0.23 in AWS costs. See full pricing →
Get started
Deploy one CloudFormation stack, run your first suite in 15 minutes, and see every trace in your own S3 bucket.