AI Launch Profile
BrowserAct
BrowserAct launched a browser-automation platform spanning an agent CLI and hosted workflow product, with isolated browser sessions, reusable profiles, proxy options, network evidence and human takeover for compatible AI agents and automation teams.
At a glance
Launch Snapshot
- Company
- BrowserAct
- Launch date
- June 25, 2026
- Launch type
- Not classified
- Pricing
- BrowserAct uses credits and resource-based metering for workflow steps, browser modes and proxy traffic. Current allowances and unit prices are published on the live pricing page and should be checked for the chosen mode.
- Free plan
- Yes
- API
- Yes
- Open weights/source
- Yes
Launch Context
Use these links to move from this record into the broader Launch Intelligence database.
Verification & Sources
- Evidence state
- Source-verified
- Source links
- 6
- Freshness
- Checked July 28, 2026
- Last verified
- July 28, 2026
- Last updated
- July 28, 2026
What this evidence state means
- Definition
- The stated claim was checked against a named primary or authoritative source. This does not mean Kingy tested the product.
- Required provenance
- At least one public, named primary or authoritative source that directly supports the claim.
- Owner
- Kingy editorial reviewer
- Freshness rule
- Recheck within 30 days and after a material product, price, access, or source change.
- Disputes and corrections
- Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.
Key source checks
Suggest a correction
Kingy AI Take
BrowserAct’s launch combines useful session isolation, agent commands and human takeover, but stealth browsers, proxies and reusable profiles increase both capability and misuse risk. The terms require lawful, authorized use and respect for target-site rules. Kingy did not run the service, so teams should validate action confirmation, cross-session isolation, retention, deletion, trace quality and cost before production access.
Who it is for
Developers, AI agent builders, automation teams and operators running authorized web research, QA or workflow tasks with explicit credential and approval boundaries.
What feels promising
A single workflow can combine isolated browser execution, reusable profiles, network evidence and a human handoff instead of hiding those controls behind an opaque agent loop.
What feels unproven
Kingy did not validate anti-blocking claims, login reliability, prompt-injection resistance, credential isolation, profile deletion, regional processing, proxy quality or cost under real workloads.
Source-backed record