Axiom Review

Six years in market, three ways to build a bot, and a Chrome DevTools API for developers who want full control. That's a real product, not a demo.

Two things worth flagging. One: the runtime caps are stingy — Pro at $50/month gives you 30 hours and a 2-hour single-run limit, which is thin for anything production-grade. Two: this competes with UiPath, Zapier, and Make, none of whom struggle for credibility with a board.

The Claude skill and MCP server are the actual differentiator — describe a bot in English, get a working automation. That's ahead of most RPA tools I've seen. But the core scraping and form-filling has been commodity since 2019. Pilot it for a scraping-heavy team of five, don't roadmap around it yet.

Operationally, Axiom is buildable across three skill levels — Builder, Step API, plain-English via Claude skill — which matters when the person maintaining a bot isn't the person who built it. That's real continuity insurance versus tools like UiPath that assume a dedicated RPA team.

The constraint I flag for planning: pricing is metered in monthly runtime hours (30 hrs at $50, 100 at $150, 250 at $250) with cloud single-run caps up to 12 hours. That's fine at pilot scale. At real production volume across multiple departments, hours become a procurement conversation every quarter, not a settled budget line.

Desktop runs are unmetered and unlimited concurrency, which is a smart release valve for privacy-sensitive or high-frequency jobs. But that pushes reliability onto whichever employee's machine is running the bot — a single point of failure I'd want solved before scaling past pilot teams. 2Captcha and Zapier/Make integrations extend reach without new engineering.

$15/month Starter, 5 hours runtime. Pro at $50 gets 30 hours, Zapier, webhooks. Pro Max at $150 triples to 100 hours but only doubles concurrency to 2 bots. That's the tier to watch — teams outgrow 30 hours quickly once scheduling goes daily.

Year 1 for a small team: $50 × 12 = $600. Add overage risk once runtime caps hit — no published per-hour overage rate, so a busy month forces an upgrade, not a bill. Year 3 at Pro Max: $150 × 36 = $5,400, likely more once concurrency needs grow.

Desktop runs are unlimited concurrency, no time cap — real cost lever if cloud hours get expensive. Compare to Zapier's task-based pricing: different unit, similar trap. No stated contract term or auto-renewal language that I could find — month-to-month looks likely, but confirm before signing.

Day-to-day, the Chrome extension Builder plus scheduling covers 80% of what an ops person actually automates: form fills, scraping into a Google Sheet, looping a CSV of vendor logins. Login/session handling with 2FA and 1Password support means fewer 2am re-auth failures, which is where most no-code scrapers quietly break.

The friction shows up in the pricing math, not the UI. Pro at $50/month buys 30 hours of runtime with a 2-hour single-run cap and daily-only cloud scheduling — if you're running hourly jobs across multiple sites, you're either upgrading to Pro Max ($150, 100 hours, 2 concurrent) or pushing work to the desktop runner, which is unlimited but ties up a machine. That's a real tradeoff versus something like UiPath's attended/unattended split, where concurrency isn't gated by a monthly hour meter.

Power-user path is genuinely there: Chrome DevTools Protocol access for Puppeteer/Playwright, a Step API, Orchestrate API, and now a Claude skill for describing bots in English. Docs cover all three layers, which suggests engineers wrote them, not just marketing.

Point-and-click bot builders are usually toys once you leave the demo. Axiom's Chrome extension Builder looks like the usual suspects, but then it also gives you a Step API, a raw Chrome DevTools/Puppeteer endpoint, and a Claude skill that writes the bot from a plain-English description. That's three doors into the same house, which is rare — most tools like this (think Zapier, but for the browser) pick one lane and stay there.

The catch shows up in the pricing page. Free gets you 2 hours total, one-time, no renewal. Pro is $50/month for 30 hours with a 2-hour single-run cap. If your scrape runs long, you're watching a clock, not a spinner — that's a different kind of anxiety than most SaaS dashboards give you.

Desktop runs are unlimited time and concurrency, which is the smart escape hatch. Three months in, you'll live on desktop and treat cloud hours like a rationed resource. Login handling with 1Password and 2FA support is a nice daily-use touch most competitors skip.

Three layers of API, a Claude skill, an MCP server. That's more surface area than UI-Vision or most no-code scrapers had five years ago. Founded 2019 — old enough to have survived a category that's eaten plenty of scrapers whole.

The pricing is metered runtime, not seats. Free tier is 2 hours, one-time, doesn't renew. Pro is $50/month for 30 hours. That's a usage-based model, same playbook as Browse.ai and Octoparse, and it can get expensive fast if a bot runs long — note the 2-hour single-run cap on Pro.

Exit portability is fine on paper: Step API is just a Node package, Chrome API is standard CDP, so Puppeteer/Playwright scripts aren't fully locked in. No-code Builder flows are the real lock-in — those don't export anywhere. Competing against Zapier and Make for orchestration, but scraping-first positioning is the actual differentiator.