fleet ▸ agents online 0

Run it on your own machine, free

Install a lightweight agent and workflows run on your hardware: no compute charge, data never leaves, reaching intranet and localhost the cloud can't. Or hand it to the managed cloud.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Connected machines2 online

studio-mbp · local agent

Speed class: fast · Local hardware

$0 compute

ops-server · BYO agent

Speed class: throughput · On-prem

$0 compute

Managed cloud fleet

Metered by running time · Nothing to install

$0.12/browser-hour
cost ▸ your hardware, free 4
01
no compute charge

Run on your own hardware, no compute charge

Workflows that run on your local or BYO agent are never billed for compute and consume no cloud time allotment; you provide the machine.

That holds on every plan, including Free: local and BYO runs are free and unlimited: never metered, never billed, never counted against any quota. Paid plans buy cloud capacity, not local permission.

Where it runsLocal / BYO agentManaged cloud
Compute chargeNone on any tier~$0.12/browser-hour after allotment
HardwareYoursWrit-managed
Cloud time allotmentNot consumedMetered by running time
Always-on / runs while offlinenoyes
Intranet & on-prem reachyesno

Local and BYO runs cost $0 in compute on every plan. The cloud is the metered, managed convenience layer. · Every plan, including Free: unlimited local and BYO runs. Paid plans add included cloud running time, faster monitor cadence, and bigger fleets. See the pricing page for what each plan includes.

gate ▸ cloud agents per plan 8
02
honest gating

A true cloud fleet starts at Growth

Local agents are unlimited on every plan; you bring the machines. Cloud agents are plan-gated. On Free and Starter your one "cloud agent" is your own device acting as the cloud agent; a genuine multi-agent fleet begins at Growth.

PlanCloud agents
Free1 (your own device)
Starter1 (your own device)
Growth5 (real fleet)
Scale20 (real fleet)

What "1 agent" means. On Free and Starter, the single cloud agent is your own connected machine registered as a cloud executor, not a hosted worker you can leave running with the lid closed. Growth and Scale add managed, always-on cloud agents you never install.

Local and BYO agents are never counted against this. See the pricing page for the full fleet limits.

net ▸ reach what cloud can't 12
03
on your network

Reach what the cloud can't

Because it runs on your machine, a BYO agent reaches systems no cloud browser can: internal and intranet sites, localhost apps, LAN devices, VPN-only and on-prem systems.

Intranet & on-premAutomate internal-only web apps and admin consoles that never touch the public internet.
localhost & LANDrive apps on localhost and devices on your local network: printers, routers, internal dashboards.
VPN-only systemsReach systems gated behind a VPN or private network the cloud structurally cannot see.

The agent runs where your systems live. Build a workflow that automates an internal-only web app, then call it over REST or expose it as an MCP tool while the agent stays inside your network.

key ▸ byo ai keys 16
04
your keys, your bill

Bring your own AI keys: stored locally, never sent to Writ

Configure your own AI provider keys (Anthropic, OpenAI, Ollama, or any OpenAI-compatible endpoint) directly in the agent.

Those keys live in the agent's local config on your own machine; the agent calls the provider directly, so your keys are never sent to or stored on Writ's servers. AI that runs on your own keys through your own agent is unbilled by Writ: you pay your provider directly, or run Ollama locally for zero per-token cost.

# Lives on YOUR machine. Never sent to Writ.
ai:
  provider: anthropic        # anthropic | openai | ollama | openai-compatible
  api_key: "sk-ant-•••••••••" # your key, your bill
  model: claude-opus-4

# Or run entirely on local hardware:
# ai:
#   provider: ollama
#   base_url: http://localhost:11434
#   model: llama3.1

Scope. This applies to local and BYO agents. Managed cloud AI is the metered, token-billed path: billed by tokens used, shown before you run.

priv ▸ ollama / private ai 20
05
Private AI

Private, no-per-token AI with Ollama

Point the agent at a local Ollama model and your workflow's AI steps run entirely on your hardware: no data leaves your machine, no per-token cost. Use it for fully private automation where the page content never touches a third party.

Your machine,your model,$0 per token.
cloud ▸ hand it to the fleet 24
06
managed, metered

Or hand it to the cloud fleet

When you'd rather not run hardware (always-on schedules, runs while your laptop is closed, scale across many sites), the managed cloud fleet runs the same workflows with nothing to install.

Cloud runs are metered by running time from your plan’s included usage, at roughly $0.12/browser-hour standard. Residential bandwidth comes out of that same pool, at 7 credits per megabyte ($7/GB) — there is no separate egress allowance to forecast. The cloud sells convenience and scale, not features. Every workflow runs the same on local or cloud.

Nothingto install
Always-onruns while you sleep
$0.12/browser-hourmetered by time

Add funds to your wallet from $5 - $1,000. See pricing.

venue ▸ per-run choice 28
07
where each run lands

Choose the venue per run

For each workflow you choose where it runs: your local agent, the shared cloud pool, or a gVisor-isolated cloud venue for sensitive runs that touch credentials or secrets.

Recommended for private

Local (your hardware)

Runs on your own agent. Free of compute, full network reach, data never leaves your machine.

Default cloud

Cloud: shared pool

Managed fleet for non-sensitive runs. Always-on, metered by running time, nothing to install.

Sensitive runs

Cloud: gVisor-isolated

A sandboxed cloud venue for runs that touch credentials or secrets. Never routed to a foreign machine.

Isolation is a choice, not an afterthought. How isolation works.

spd ▸ speed classes 32
08
routing

Speed classes

Agents advertise a speed class (fast, throughput, or balanced) and a performance score. Writ routes latency-sensitive work to fast machines and bulk runs to throughput machines, automatically.

fast: streaming & live recordingthroughput: bulk runsbalanced: mixed workloads
cmp ▸ free-local vs paid-cloud 36
09
plainly

The free-local vs paid-cloud model, stated plainly

Local and BYO agents are free of compute on every plan; you bring the hardware. The cloud is the metered, managed convenience layer on top.

CapabilityLocal / BYOCloud fleet
Compute chargeNone on any tier~$0.12/browser-hour after allotment
Run-count capsNone on any planNone on any plan
Run volumeUnlimited, free on every planMetered by running time
Always-on / runs while offlinenoyes
Intranet & on-prem reachyesno
Bring-your-own AI keysyespartial
Isolation venuesYour machineShared + gVisor-isolated

Local and BYO runs are free and unlimited on every plan, including Free: never metered, never billed. Cloud runs are metered by running time. · Want to run the whole stack yourself? See self-hosting.

ok ▸ authorized by design 40
10
legitimacy

Authorized by design

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

Your accountsRuns on your own credentials, on sites you are authorized to use.
Keys never leaveWith a BYO agent, your data and AI keys never leave your machine.
Encrypted secretsSecrets live in an encrypted vault; runs are logged and attributable.
You own your dataExport or delete it at any time; it is yours.
faq ▸ common questions 44
11
Questions

Common questions about agents

Are local runs really free of compute?
Yes. Workflows that run on your local or BYO agent are never billed for compute and consume no cloud time allotment; you provide the machine. That holds on every plan, including Free: local and BYO runs are free and unlimited, never metered and never counted against any quota.
Can a BYO agent reach intranet and localhost sites?
Yes. Because the agent runs on your own machine, it reaches internal and intranet sites, localhost apps, LAN devices, and VPN-only or on-prem systems that no cloud browser can structurally see. The agent runs where your systems live.
How many cloud agents does each plan include?
Cloud agents are 1 on Free, 1 on Starter, 5 on Growth, and 20 on Scale. On Free and Starter, that one cloud agent is your own connected device acting as the cloud executor. A true multi-agent fleet of managed, always-on workers begins at Growth. Local and BYO agents are unlimited on every plan and never count against this.
Where do my AI keys live with a BYO agent?
Your AI provider keys live in the agent's local config on your own machine. The agent calls the provider directly, so your keys are never sent to or stored on Writ's servers. AI that runs on your own keys through your own agent is unbilled by Writ.
Is there a cap on local runs on the Free plan?
No. Local and BYO runs are free and unlimited on every plan, including Free: never metered, never billed, never counted. Paid plans add included cloud running time, faster monitor cadence, and bigger fleets; the pricing page has the details.
When should I use the cloud fleet instead?
Use the managed cloud fleet when you want always-on schedules, runs while your laptop is closed, or scale across many sites with nothing to install. Cloud runs are metered by running time at roughly $0.12 per browser-hour, from your plan’s included usage.
Want to self-host the whole stack? See /self-hosting.