Our purpose

Your web product is global.
Your browser lab shouldn't be limited.

Product companies ship one web app to customers on Windows, macOS, Linux, Android, and iOS — using Chrome, Edge, Safari, Firefox, Opera, and dozens of versions in the wild. Akash Web farm gives QA and engineering teams instant access to real browsers in the cloud, so you never ship blind to a segment of your audience.

Try a browser now Run with Docker

Code last updated on 15 February 2026 · Code created by Akash

The problem product teams face

You build one web product. Your users arrive from everywhere — and every combination hurts when you can't test it.

Limited local machines

Developers typically own one OS. A Mac team cannot natively run Edge on Windows 11. A Windows team cannot reproduce Safari on macOS. Buying every laptop is expensive and still incomplete.

Browser version fragmentation

Enterprise users stay on older Chrome. Consumer users auto-update weekly. One bug in Chrome 120 vs 145 can mean checkout failures for millions — but you only tested on your latest install.

Global audience, local QA

Users in India on Android Chrome, in Europe on Firefox, in the US on Edge — different locales, fonts, ad blockers, and network paths. A single-environment test pass misses real-world variance.

Slow device labs

Physical device farms need procurement, USB hubs, MDM, and maintenance. VMs with browsers consume disk and RAM. CI queues grow. Releases slip while coverage stays narrow.

How Akash Web farm solves it

One Dockerized platform. Real browser engines. On-demand sessions and parallel grids — no installer sprawl on every engineer's machine.

1

Launch any supported browser instantly

Open Chrome, Opera, or Edge on macOS or Windows targets from the Desktop Browser Studio. Pick from the latest five major versions per engine — match what your analytics say customers use.

2

Preview mobile viewports without devices

Mobile Preview Lab emulates iPhone and Android screen sizes with real browser rendering. Validate responsive layouts, touch targets, and checkout flows before users on small screens hit production bugs.

3

Scale parallel automation

Spin up isolated Selenium grids with multiple Chrome, Opera, and Edge nodes. Run TestNG, Selenium, or Playwright suites in CI against /wd/hub or /runner/<id>/wd/hub — matrix testing across engines in minutes, not days.

4

Share live sessions with reviewers

Hand teammates an interactive browser session — same build, same URL, different engine. Run UAT sign-offs without "works on my machine."

Coverage your global web product needs

Map real user segments to sessions you can run today on Akash Web farm.

User segment Typical stack How Akash Web farm covers it
Managed desktop user Windows · Edge or Chrome (locked-down) Desktop studio → Windows target · Edge/Chrome · older major version
macOS desktop user macOS · Chrome Desktop studio → macOS target · Chrome; mobile preview for narrow viewport
Mobile user (Android) Android · mobile Chrome Mobile Preview Lab → Android preset · Chrome engine
Mobile user (iOS class) Small-screen WebKit viewport Mobile Preview Lab → compact/large phone presets
Power user / privacy Windows/Linux · Opera Desktop studio → Opera on Windows · parallel runners for regression
CI regression suite Headless Chrome + cross-browser nightly Parallel Runners · WebDriver hub · multi-node grid per pipeline stage

Without cloud browsers

  • QA borrows one Windows laptop for Edge tests
  • Production bug reported from Opera — cannot reproduce
  • Mobile issues found only after release
  • CI runs Chrome-only; other engines tested manually before release
  • Device lab budget delayed; coverage spreadsheet is wishful thinking

With Akash Web farm

  • Any engineer opens Edge on Windows in under 60 seconds
  • Parallel grid runs Chrome + Opera + Edge on every PR
  • Mobile viewports validated before merge
  • Reviewers watch live sessions on the exact engine end-users rely on
  • Docker deploy on one VM — entire team shares the same browser farm

Dockerized — run the full stack in minutes

Akash Web farm ships as containers: PostgreSQL, Redis, and the platform with Docker-socket access to spawn Selenium browser nodes. No manual browser installs on the host.

Requirements

  • Docker Desktop or Colima (macOS)
  • 8 GB RAM recommended (Chrome grid nodes)
  • Port 4444 available

Start from WebFarm root

# Clone / open WebFarm, then:
bash docker-start.sh

# Open in browser:
#   http://localhost:4444/          — portal
#   http://localhost:4444/purpose.html — this page
#   http://localhost:4444/health      — health check

# Stop:
bash docker-start.sh --down

What Docker runs

  • awf-postgres — users, sessions, audit
  • awf-redis — cache
  • akash-webfarm — UI, API, WebDriver, auto grids

Full install & usage: docs/GUIDE.md — single unified guide.

Check health Launch browser studio

Built for global web products

If your app is used worldwide, browser and OS diversity is core coverage — not an edge case.

Cross-region teams

Validate checkout, auth, and dashboards on every major browser your traffic analytics highlight — before you ship.

Regulated workflows

Audit trails, session identity, and controlled browser environments for sign-off without unmanaged personal devices.

QA & platform teams

Demo builds on Chrome, Opera, and mobile viewports from one URL. Scale runner grids without shipping hardware to every tester.

Stop guessing. Start testing where your users are.

Docker up the farm, open a session, and cover the browsers your global product deserves.

Open browser studio