Private browser infrastructure for code, no-code & AI.

The same Chromium runtime powers every bot, whether you built it visually, wrote it in Playwright, or had Claude generate it.

Create account

Where bots run

One product, two ways to run.

Same automations, same builder, same step library. Pick where they run based on scale, scheduling, or how private you want your data.

Run in our infrastructure

Hands-off, headless, always on. Scheduled runs, concurrent execution, proxies, and monitoring built in.

Up to 20 parallel runs
Trigger from API, webhook, or schedule
Isolated sessions, never reused
Bring your own proxies or use ours

Run on your machine

Local, private, unlimited. Run as many bots as your hardware allows, with no data ever leaving your computer.

Unlimited parallel runs
Local scheduling
Used in data-sensitive industries
No data sent or stored externally

Real Chromium, on demand.

Production-grade browser infrastructure for every kind of bot you build.

Chromium at scale

Run as many as you need. Unlimited on desktop, up to 20 concurrent runs on cloud. Custom packages available for higher cloud throughput.

Unlimited concurrent runs on desktop
Up to 20 concurrent cloud runs on Ultimate
Custom enterprise packages on request
Same Chromium runtime everywhere

Fully configurable

Tune the browser per run. Same settings on cloud and desktop in no-code. Code parity coming soon.

Schedule runs hourly, daily, or on a trigger
Block resources and run headless
Set profiles, store cookies, persist sessions
Configure timezone

Stealth built in

Anti-bot detection and countermeasures, built into every no-code run. Code support coming soon.

Anti-bot detection countermeasures
Set proxies
Mimics user behaviour
Built into no-code, no setup required

Private by default

Your data is yours. Isolated on cloud, local on desktop, never used to train AI.

Never used for AI training
Never shared with third parties
Stays in the run container unless you send it somewhere
Or run desktop and keep everything local

How it works

Three steps to your first run.

Same flow whether you're connecting from code, the extension, or your AI.

Step 1

Get api key

Create an account and get a key instantly. No card required to start.

Step 2

Pick no-code, code, or AI

Build visually with the Chrome extension, write a script in Puppeteer or Playwright, or describe it to Claude. Whichever path, the same runtime executes

Run on cloud or desktop

Run, manage, edit

Execute, schedule, trigger. Monitor live, debug failures, scale with your plan.

The API

Three layers, Chrome, step & Orchestrate.

Drive a raw browser, call high-level steps, or trigger a pre-built automation. Mix layers, or stick to one.

Chrome API

A long-lived WebSocket to a cloud browser. Drive it from Puppeteer, Playwright, or any CDP-speaking client.

Connect from Puppeteer or Playwright
Any CDP-compatible library works
Full Chrome DevTools Protocol access
Existing scripts run as-is

Read Chrome API docs

Step API

Skip the CDP boilerplate. Our step library wraps browser actions as high-level functions in Node.

High-level browser actions in Node
Available via the axiom-api package
Same steps as the no-code builder
Mix with raw Chrome API calls

Read Step API docs

Orchestrate API

Trigger any pre-built automation, code or no-code, and manage its runs over REST.

Trigger bots from any HTTP client
Manage runs, retries, schedules
Works for code and no-code bots
Webhook callbacks on completion

Read Orchestrate API docs

Which one?

Pick by what you're doing.

There's no wrong answer. You can of course use both!

Sign up for free runtime

Use cloud when

Full API access
You need to schedule runs
You trigger bots from your stack or AI
Triggering bots using webhooks
You don't want to keep a machine on

Use desktop when

Data privacy is non-negotiable
You need access to local files
You're behind a VPN
You want unlimited concurrency
If you are Hippa compliant

Your data stays where you put it.

Every run draws a clear boundary. Nothing crosses it unless you explicitly send it somewhere.

See privacy

Desktop runtime

Your network

Your machine

Input

→

Chromium

→

Website

→

Output

Data never leaves your network

Cookies, logins, history stay local

axiom servers are not in the loop

Cloud runtime

HTTPS

Isolated container

API in

→

Chromium

→

Website

→

API out

Session isolated, never reused

Container destroyed after run

You decide where output goes

Never used for AI training.

No matter where you run.

Encrypted in transit.

TLS on every connection.

We don't read it.

Containers stay private.

FAQ

What our customers ask.

Common things people ask about no-code, code, AI, and running automations on our infrastructure.

See FAQ

Yes. Automations built with the no-code tool can run on desktop or in the cloud, freely. Code automations calling the API currently run in the cloud only. A desktop API is on the roadmap. Contact us if you'd like beta access when it's ready.

Any data passed to axiom by webhook or integration is encrypted in transit, on cloud or desktop. Automations themselves run in isolated containers. The data processed in those containers is private. We don't access it, record it, or share it with an AI. When a run completes, the container and everything in it are destroyed.

Yes. Both the Chrome API (drive a cloud browser from your code) and the Orchestrate API (trigger saved bots over REST) work from any stack.

No. Your data is never shared with AI or used for training. However, if you add an AI step to your automation, that AI provider processes your data under their own terms. We have no control over that and we take no responsibility. AI steps are optional and never added by default. Check with your AI provider for how they handle data.

20 is the cap on our Ultimate tier. Enterprise plans go higher, or we can build a custom plan. Contact support to discuss your needs.

Yes. In the no-code tool, set a proxy per bot in the runtime settings. In code, pass proxy details as a connection parameter when opening a session. Both residential and datacenter proxies are supported. See the proxy docs for the full reference.

No. axiom is not HIPAA compliant and we don't sign BAAs because we don't need to. HIPAA-regulated workflows should not run in the cloud. Use the desktop app on your own HIPAA-compliant infrastructure instead, so no healthcare data ever reaches us. Many regulated teams use axiom this way.

Try a cloud run, free for 2 hours.

Free to install. No card required. Switch between cloud and desktop whenever you like.