# Nevazu: full text for language models

---

> Nevazu is a persistent cloud browser service. Each browser is a real Chrome running on its own computer in the cloud, with a dedicated IPv4 address that no one else uses and encrypted storage that keeps your profile, cookies, extensions and sign-ins between sessions. You open it in a live view from a desktop, tablet or phone.

---

This file joins Nevazu's public pages in English. Index: https://nevazu.com/llms.txt

---

# Nevazu: A real Chrome in the cloud, signed in and on an IP of its own.

> A real Chrome on its own cloud computer, with a dedicated static IP and encrypted storage that keeps your sign-ins. Prepaid, billed per minute.

Nevazu is a persistent cloud browser service. Each browser is a real Chrome running on its own computer in the cloud, with a dedicated IPv4 address that no one else uses and encrypted storage that keeps your profile, cookies, extensions and sign-ins between sessions. You open it in a live view from a desktop, tablet or phone.

Open it from any device or hand it to an AI agent. It keeps every sign-in, shows websites the same address each time, and bills running time by the minute.

- **Dedicated IP.** One static IPv4 per browser. Never shared, never rotated unless you ask.
- **Stays signed in.** Profile, cookies and extensions on encrypted storage, kept through every sleep.
- **Worldwide regions.** Choose the country your IP is in. It stays there for the life of the browser.
- **Per minute.** Prepaid, no subscription. Asleep, a browser costs only its IP and storage.

As of 2026-10-27, new browsers can be created in 32 regions: Aragón, Spain; Auckland, New Zealand; Bangkok, Thailand; Calgary, Canada; Cape Town, South Africa; Dublin, Ireland; Frankfurt, Germany; Hong Kong; Hyderabad, India; Jakarta, Indonesia; Kuala Lumpur, Malaysia; London, United Kingdom; Melbourne, Australia; Milan, Italy; Montreal, Canada; Mumbai, India; N. California, United States; N. Virginia, United States; Ohio, United States; Oregon, United States; Osaka, Japan; Paris, France; Querétaro, Mexico; São Paulo, Brazil; Seoul, South Korea; Singapore; Stockholm, Sweden; Sydney, Australia; Taipei, Taiwan; Tel Aviv, Israel; Tokyo, Japan; Zurich, Switzerland. A Basic (2 vCPU, 4 GB) browser costs $0.1339–$0.208 an hour while running and $0.009–$0.012 an hour while asleep (its IP and storage), prepaid in USD and metered per minute. A Premium (4 vCPU, 8 GB) browser costs $0.2717–$0.4246 an hour while running and $0.009–$0.012 an hour while asleep (its IP and storage), prepaid in USD and metered per minute. A new account gets $4.00 in credit.

## What you can do with it

- **[Research and review with an AI agent](https://nevazu.com/use-cases.md).** It reads the real, signed-in page from screenshots: more than a scraper or an API returns.
- **[Promotion work that lives only on the web](https://nevazu.com/use-cases.md).** Directories, communities and dashboards with no API, handled in the browser, in your own accounts.
- **[A browser in the country you need](https://nevazu.com/use-cases.md).** A dedicated IP and local time zone in the region you pick, no agent needed.
- **[One browser on every device](https://nevazu.com/use-cases.md).** The same tabs, sign-ins and IP on your laptop, tablet and phone.

## Features

- **A real cloud browser.** Full Chrome on a dedicated cloud computer, not a shared container. Open it from anywhere and it is exactly where you left it.
- **Persistent by design.** Profiles, cookies, sign-ins and extensions live on encrypted, isolated storage that survives every sleep and restart.
- **Dedicated static IP.** One IP per browser, never shared and never rotated unless you ask. Sites see the same address, session after session.
- **Low-latency live view.** WebRTC streaming that keeps text sharp, with ordered keyboard, mouse and touch input.
- **Works with AI agents.** Connect Claude Code, Cursor or any MCP agent to a browser with nothing to install: it sees screenshots and acts while you watch, and you take over with a click.
- **Sleeps when idle.** Idle browsers sleep on their own and wake in about a minute.
- **Prepaid, per minute.** No subscription. Top up once; usage comes from your balance.
- **Any device.** Software keyboard and touch gestures on tablets and phones.

## Nevazu in short

### What is Nevazu?

Nevazu is a persistent cloud browser service. Each browser is a real Chrome running on its own computer in the cloud, with a dedicated IPv4 address that no one else uses and encrypted storage that keeps your profile, cookies, extensions and sign-ins between sessions. You open it in a live view from a desktop, tablet or phone.

### How is it different from a VPN or a proxy?

A VPN or a proxy changes the address your own browser connects from, while the browser and its data stay on your device. With Nevazu the whole browser runs in the cloud: websites see its own dedicated IP, and its profile is stored, encrypted, with it, so it is the same browser at the same address from every device.

### Can an AI agent use it?

Yes, with nothing to install. Each browser has its own MCP server address: Claude Code, Cursor, Codex and other AI agents, chat apps such as Claude or ChatGPT, or any MCP client connect over HTTPS and sign in with your Nevazu account. You watch in the live view and take control back with any click or key.

### How does billing work?

Prepaid, with no subscription. Running time is metered per minute while a browser is awake; its dedicated IP and storage are charged for as long as it exists. Prices are the public AWS list prices for the region times a published multiplier.

More answers: https://nevazu.com/docs/faq.md

## Pages

- [Use cases](https://nevazu.com/use-cases.md)
- [Pricing](https://nevazu.com/pricing.md)
- [Documentation](https://nevazu.com/docs.md)
- [Contact](https://nevazu.com/contact.md)
- [Create an account](https://nevazu.com/sign-up)

Source: https://nevazu.com/


---

# What people use Nevazu for

> A real Chrome that stays signed in, on its own IP, in the region you choose. Hand it to an AI agent, or use it yourself from any device.

## Let an AI agent look things up and review them for you

Connect Claude Code, Cursor, Codex or any MCP client to a browser. The agent works from screenshots of the real page, in the same Chrome and sign-ins you use, while you watch and take over with one click.

- **Compare offers.** Open each store, read the price, delivery date and stock a buyer is shown, and put them side by side in one table.
- **Review your own dashboards.** Go through the analytics, ads or seller consoles you are signed in to and summarize what changed this week.
- **Check figures at the source.** Read the page itself, tables, charts and footnotes included, and note where each number came from.

### Why a browser sees more than a scraper or an API

|  | Fetching the page | An official API | An agent in Nevazu |
| --- | --- | --- | --- |
| Content drawn by scripts | Often missing: the page is read before its scripts run | Only the fields the API returns | Everything Chrome shows |
| Pages behind your sign-in | Cookies copied by hand, until they expire | A developer key or app approval, where one is offered | Your own session, kept between visits |
| Images, charts and layout | Image links and markup, not what they show | Rarely included | Read from the screenshot, as you see it |
| What a given country sees | Whatever the script’s network gets | Depends on the API | The view from the browser’s region and IP |
| Speed per page | Fastest | Fast, and already structured | Slower: one screenshot at a time |

When an API already returns what you need, use it: it is faster and cheaper. A browser is for the part of the work that exists only on the page.

How it works: https://nevazu.com/docs/agents.md

## Hand routine promotion work to an agent

Many directories, communities, marketplaces and ad dashboards offer their tools only as web pages, with no API. An agent can do that work in the browser, in your own accounts, the way you would by hand.

- **Publish an announcement.** Post a launch or an update to the places you list your product, filling in each site’s own form.
- **Keep listings current.** Update descriptions, prices and images across web dashboards that offer no API.
- **Gather feedback.** Collect new comments and reviews into one summary, and draft replies for you to check before anything is sent.

> **Note:** The agent acts as you, with everything your accounts allow. Follow each platform’s rules and posting limits, give it read-only access where looking is enough, and watch its first runs in the live view.

How it works: https://nevazu.com/docs/agents.md

## Browse from the country you need, no agent required

Create a browser in any region we offer, across Asia Pacific, Europe, the Americas, the Middle East and Africa. Websites see its dedicated IP in that country, and its clock keeps the local time zone.

- **See your site as visitors abroad do.** Check the language, prices, cookie banners and pages people in another country are shown.
- **Check your listings in each market.** Look at your search results, app store pages and ads in the countries where you run them.
- **Keep a steady local address.** Give an account you manage in one country the same local IP and time zone every time, whichever network you are on.

As of 2026-10-27, new browsers can be created in 32 regions: Aragón, Spain; Auckland, New Zealand; Bangkok, Thailand; Calgary, Canada; Cape Town, South Africa; Dublin, Ireland; Frankfurt, Germany; Hong Kong; Hyderabad, India; Jakarta, Indonesia; Kuala Lumpur, Malaysia; London, United Kingdom; Melbourne, Australia; Milan, Italy; Montreal, Canada; Mumbai, India; N. California, United States; N. Virginia, United States; Ohio, United States; Oregon, United States; Osaka, Japan; Paris, France; Querétaro, Mexico; São Paulo, Brazil; Seoul, South Korea; Singapore; Stockholm, Sweden; Sydney, Australia; Taipei, Taiwan; Tel Aviv, Israel; Tokyo, Japan; Zurich, Switzerland. A Basic (2 vCPU, 4 GB) browser costs $0.1339–$0.208 an hour while running and $0.009–$0.012 an hour while asleep (its IP and storage), prepaid in USD and metered per minute. A Premium (4 vCPU, 8 GB) browser costs $0.2717–$0.4246 an hour while running and $0.009–$0.012 an hour while asleep (its IP and storage), prepaid in USD and metered per minute. A new account gets $4.00 in credit.

How it works: https://nevazu.com/docs/browsers.md

## Pick up the same browser on any device

The browser lives in the cloud, not on your computer. Open it from a laptop, a tablet or a phone and it is the same Chrome, with the same tabs, sign-ins and IP.

- **Start here, finish there.** Begin at your desk and carry on from your phone; nothing needs syncing.
- **Made for touch.** Tap, swipe, the on-screen keyboard and input methods such as Chinese or Japanese work on phones and tablets, in an ordinary web browser.
- **One place at a time.** Opening it on another device offers Use here, so two screens never type into it at once.

How it works: https://nevazu.com/docs/live-view.md

Source: https://nevazu.com/use-cases


---

# Simple, prepaid pricing

> No subscription and no minimum term. Add credit when you need it; usage is metered per minute and taken from your balance.

## Current prices

| Region | Machine | Running, per hour | Asleep, per hour | Data sent, per GB |
| --- | --- | --- | --- | --- |
| Aragón, Spain | Basic (2 vCPU, 4 GB) | $0.1458 | $0.0094 | $0.203 |
| Aragón, Spain | Premium (4 vCPU, 8 GB) | $0.2966 | $0.0094 | $0.203 |
| Auckland, New Zealand | Basic (2 vCPU, 4 GB) | $0.1843 | $0.0099 | $0.2378 |
| Auckland, New Zealand | Premium (4 vCPU, 8 GB) | $0.377 | $0.0099 | $0.2378 |
| Bangkok, Thailand | Basic (2 vCPU, 4 GB) | $0.1339 | $0.0093 | $0.2291 |
| Bangkok, Thailand | Premium (4 vCPU, 8 GB) | $0.2717 | $0.0093 | $0.2291 |
| Calgary, Canada | Basic (2 vCPU, 4 GB) | $0.1489 | $0.0094 | $0.203 |
| Calgary, Canada | Premium (4 vCPU, 8 GB) | $0.3023 | $0.0094 | $0.203 |
| Cape Town, South Africa | Basic (2 vCPU, 4 GB) | $0.1806 | $0.01 | $0.2958 |
| Cape Town, South Africa | Premium (4 vCPU, 8 GB) | $0.3691 | $0.01 | $0.2958 |
| Dublin, Ireland | Basic (2 vCPU, 4 GB) | $0.1458 | $0.0094 | $0.203 |
| Dublin, Ireland | Premium (4 vCPU, 8 GB) | $0.2966 | $0.0094 | $0.203 |
| Frankfurt, Germany | Basic (2 vCPU, 4 GB) | $0.1548 | $0.0096 | $0.203 |
| Frankfurt, Germany | Premium (4 vCPU, 8 GB) | $0.3152 | $0.0096 | $0.203 |
| Hong Kong | Basic (2 vCPU, 4 GB) | $0.1717 | $0.0101 | $0.2465 |
| Hong Kong | Premium (4 vCPU, 8 GB) | $0.3503 | $0.0101 | $0.2465 |
| Hyderabad, India | Basic (2 vCPU, 4 GB) | $0.1367 | $0.0095 | $0.231 |
| Hyderabad, India | Premium (4 vCPU, 8 GB) | $0.2772 | $0.0095 | $0.231 |
| Jakarta, Indonesia | Basic (2 vCPU, 4 GB) | $0.1563 | $0.0097 | $0.2639 |
| Jakarta, Indonesia | Premium (4 vCPU, 8 GB) | $0.3184 | $0.0097 | $0.2639 |
| Kuala Lumpur, Malaysia | Basic (2 vCPU, 4 GB) | $0.1339 | $0.0093 | $0.2291 |
| Kuala Lumpur, Malaysia | Premium (4 vCPU, 8 GB) | $0.2717 | $0.0093 | $0.2291 |
| London, United Kingdom | Basic (2 vCPU, 4 GB) | $0.1607 | $0.0096 | $0.203 |
| London, United Kingdom | Premium (4 vCPU, 8 GB) | $0.3277 | $0.0096 | $0.203 |
| Melbourne, Australia | Basic (2 vCPU, 4 GB) | $0.1762 | $0.0097 | $0.2378 |
| Melbourne, Australia | Premium (4 vCPU, 8 GB) | $0.3593 | $0.0097 | $0.2378 |
| Milan, Italy | Basic (2 vCPU, 4 GB) | $0.1607 | $0.0095 | $0.203 |
| Milan, Italy | Premium (4 vCPU, 8 GB) | $0.3277 | $0.0095 | $0.203 |
| Montreal, Canada | Basic (2 vCPU, 4 GB) | $0.1485 | $0.0094 | $0.203 |
| Montreal, Canada | Premium (4 vCPU, 8 GB) | $0.3023 | $0.0094 | $0.203 |
| Mumbai, India | Basic (2 vCPU, 4 GB) | $0.1367 | $0.0095 | $0.231 |
| Mumbai, India | Premium (4 vCPU, 8 GB) | $0.2772 | $0.0095 | $0.231 |
| N. California, United States | Basic (2 vCPU, 4 GB) | $0.1683 | $0.0097 | $0.203 |
| N. California, United States | Premium (4 vCPU, 8 GB) | $0.3436 | $0.0097 | $0.203 |
| N. Virginia, United States | Basic (2 vCPU, 4 GB) | $0.1362 | $0.009 | $0.203 |
| N. Virginia, United States | Premium (4 vCPU, 8 GB) | $0.2768 | $0.009 | $0.203 |
| Ohio, United States | Basic (2 vCPU, 4 GB) | $0.1362 | $0.009 | $0.203 |
| Ohio, United States | Premium (4 vCPU, 8 GB) | $0.2768 | $0.009 | $0.203 |
| Oregon, United States | Basic (2 vCPU, 4 GB) | $0.1362 | $0.009 | $0.203 |
| Oregon, United States | Premium (4 vCPU, 8 GB) | $0.2768 | $0.009 | $0.203 |
| Osaka, Japan | Basic (2 vCPU, 4 GB) | $0.1702 | $0.0097 | $0.2378 |
| Osaka, Japan | Premium (4 vCPU, 8 GB) | $0.3467 | $0.0097 | $0.2378 |
| Paris, France | Basic (2 vCPU, 4 GB) | $0.1607 | $0.0096 | $0.203 |
| Paris, France | Premium (4 vCPU, 8 GB) | $0.3277 | $0.0096 | $0.203 |
| Querétaro, Mexico | Basic (2 vCPU, 4 GB) | $0.1427 | $0.0092 | $0.203 |
| Querétaro, Mexico | Premium (4 vCPU, 8 GB) | $0.2903 | $0.0092 | $0.203 |
| São Paulo, Brazil | Basic (2 vCPU, 4 GB) | $0.208 | $0.012 | $0.29 |
| São Paulo, Brazil | Premium (4 vCPU, 8 GB) | $0.4246 | $0.012 | $0.29 |
| Seoul, South Korea | Basic (2 vCPU, 4 GB) | $0.1531 | $0.0095 | $0.2552 |
| Seoul, South Korea | Premium (4 vCPU, 8 GB) | $0.3119 | $0.0095 | $0.2552 |
| Singapore | Basic (2 vCPU, 4 GB) | $0.1564 | $0.0097 | $0.2465 |
| Singapore | Premium (4 vCPU, 8 GB) | $0.3184 | $0.0097 | $0.2465 |
| Stockholm, Sweden | Basic (2 vCPU, 4 GB) | $0.1453 | $0.0092 | $0.203 |
| Stockholm, Sweden | Premium (4 vCPU, 8 GB) | $0.2958 | $0.0092 | $0.203 |
| Sydney, Australia | Basic (2 vCPU, 4 GB) | $0.1758 | $0.0097 | $0.2378 |
| Sydney, Australia | Premium (4 vCPU, 8 GB) | $0.3593 | $0.0097 | $0.2378 |
| Taipei, Taiwan | Basic (2 vCPU, 4 GB) | $0.1534 | $0.0093 | $0.2295 |
| Taipei, Taiwan | Premium (4 vCPU, 8 GB) | $0.3126 | $0.0093 | $0.2295 |
| Tel Aviv, Israel | Basic (2 vCPU, 4 GB) | $0.1537 | $0.0101 | $0.232 |
| Tel Aviv, Israel | Premium (4 vCPU, 8 GB) | $0.3117 | $0.0101 | $0.232 |
| Tokyo, Japan | Basic (2 vCPU, 4 GB) | $0.1698 | $0.0097 | $0.2378 |
| Tokyo, Japan | Premium (4 vCPU, 8 GB) | $0.3467 | $0.0097 | $0.2378 |
| Zurich, Switzerland | Basic (2 vCPU, 4 GB) | $0.1701 | $0.0104 | $0.203 |
| Zurich, Switzerland | Premium (4 vCPU, 8 GB) | $0.3465 | $0.0104 | $0.203 |

- Prices in USD as of 2026-10-27. Running = compute, dedicated IP and storage; asleep = the IP and storage alone. Running time is metered per minute.
- Creating or waking a paid browser needs at least $1.00 of available credit. Browsers are kept 7 days after available credit runs out.
- A new account gets $4.00 in credit.

## How charges work

1. **Top up.** Add credit through our payment partner. Unused credit stays on your balance.
2. **Metered per minute.** Running time is charged while the browser is awake. The IP and storage are charged for as long as the browser exists.
3. **A small amount is held.** Seven days of IP and storage cost is held from your balance. It is not a charge.
4. **If credit runs out.** Browsers stop at once and are kept 7 days, then deleted unless you add credit.

## What is charged

- Compute: per minute while the browser is awake, including the minute or so it takes to start Chrome when it wakes and to save your profile and shut down when it sleeps (AWS charges for the machine then too).
- Dedicated IP: per hour for as long as the browser exists, awake or asleep.
- Storage: per GB-month for the data volume and system disk, prorated by time.
- Data sent: per GB sent from the browser to the internet, mostly the live view, and the profile backup uploaded when it sleeps. It includes the fee of the relay that carries the live view to you.

Rates follow public AWS list prices for each region times a service multiplier, and are shown in USD, excluding VAT and sales tax, which are added at checkout where they apply.

Machine tiers: Basic (2 vCPU, 4 GB memory) and Premium (4 vCPU, 8 GB memory, where offered): they differ only in CPU and memory.

## Questions

### Is there a subscription?

No. You add credit in advance and only usage is deducted. There is nothing to cancel.

### What does a sleeping browser cost?

Only its dedicated IP and storage, so it keeps the same address and data. Delete it to stop all charges.

### What is the held amount?

Seven days of IP and storage cost per browser, held from your balance so your data is safe if your credit runs out. It stays yours and is released when the browser is deleted.

### Can I get a refund?

Credit is non-refundable, so top up only what you expect to use. We refund duplicate or mistaken charges, and wherever the law gives you the right, such as the 14-day withdrawal for consumers in the EU and the UK (unused credit only).

### Who handles payments?

Stripe, or Creem as our merchant of record; the payment page shows which. They process the payment, issue receipts and add VAT or sales tax where it applies. We never see your card details.

More: https://nevazu.com/docs/billing.md · https://nevazu.com/refunds.md

Source: https://nevazu.com/pricing


---

# Getting started

> Sign in, create your first browser and open it.

Nevazu gives you a real Chrome running on its own computer in the cloud. Each browser has a dedicated IP address that no one else uses, and encrypted storage that keeps your profile, cookies and sign-ins between sessions.

## Sign in

Enter your email on the sign-in page and we send you a 6-digit code, valid for 5 minutes. A new email has no account yet: choose Create account instead (see Account security). If you turned on two-step verification, you then enter a code from your authenticator app.

## Create a browser

- Open Browsers and choose New browser.
- Give it a name and pick a region. The region and its IP stay with the browser for its whole life.
- Review the estimated cost and create it. Setting up usually takes 3–8 minutes: we reserve the IP, create encrypted storage, set up Chrome on its new machine and check from inside Chrome that websites see the right IP.

When the IP check passes, the browser opens automatically.

## Open, sleep and wake

Choose Open on a browser card to see it live. When you leave it idle, it goes to sleep after the time set in its settings. Sleeping keeps your data and IP; waking takes about a minute.

Source: https://nevazu.com/docs/getting-started


---

# Browsers and dedicated IPs

> Regions, IP checks, sleeping and deleting.

## Regions

A browser lives in one region and keeps it permanently, together with its dedicated IP: websites see an address in that region’s country, and the browser’s clock uses the region’s timezone. To use another region, create another browser.

Choose the country your IP must be in first. Among the regions there, the one closest to you feels most responsive. The region list helps with both:

- Latency: the round trip from your network to the region, measured in your browser when the list opens. A value marked ≈ is an estimate from your approximate location until the measurement finishes. Under about 80 ms feels local; above about 160 ms, typing and scrolling lag noticeably.
- Available: the region can take a new browser now.
- Limited: you can create here, but AWS was short of machines in the region in the last half hour, or only one place is left. Creation tries other zones of the region automatically and may take longer.
- Unavailable: no new browsers right now (no space left, or paused while we fix a provider problem). Existing browsers there keep working.
- Not yet tested: the region passed our setup checks, but no browser has run there yet. You can create one; if it does not start, choose another region.
- Fastest for you marks the nearest region that is available.

> **Note:** AWS does not publish how many machines are free. Availability comes from your account’s regional limits and how recent launches in the region went, so a Limited region usually still works.

## Basic and Premium

Where Premium is offered, you choose the machine when you create a browser. Basic runs on 2 vCPUs and 4 GB of memory; Premium on 4 vCPUs and 8 GB, so busy pages and many tabs have more room. That is the only difference: the live view, the IP, storage and data work the same way. Premium has a higher running rate; the IP, storage and data rates are the same. A browser keeps its machine for life; for the other one, create another browser.

## The dedicated IP

Each browser gets a public IPv4 address reserved for it alone. It stays with the browser until you delete it and is never given to another customer, even afterwards.

Every few minutes, the browser checks from inside Chrome which address websites see. If the address is ever different, we pause its network at once so that no other IP is used, and the browser shows that it is checking. You can run a check yourself from Settings → Verify IP while it runs.

## Sleep and auto-sleep

An idle browser goes to sleep after the time in Settings → Auto-sleep (10 minutes by default; shorter saves money). A changed setting counts from the moment you save it. Before it sleeps, the live view shows a countdown with Stay awake. Its computer is stopped while it sleeps; the IP and storage are kept, and are still charged.

Never sleep keeps a paid browser running, and charged, while nobody uses it. It is available after your first top-up, when your available credit covers 24 hours of everything your browsers spend with this one always on. Before you turn it on, Settings shows what 24 hours of continuous running costs in the browser’s region: compute, IP and storage. A Never sleep browser still stops when your available credit runs out, or when an administrator stops it or a security check pauses it, and it never restarts by itself: you open it again when you choose.

## Deleting a browser

Deleting is permanent. Access closes immediately, its data and sign-ins are destroyed and its resources released. Charges stop when deletion starts. Encrypted profile archives become unreadable before they are removed.

## Status messages

- Waiting for capacity: the cloud provider has no free machines of this type in the region. We keep trying; your data and IP are safe.
- Provider issue: the cloud provider is having problems in the region.
- Needs attention: something went wrong that needs an action, such as restarting the browser. The message says what.
- Failed: the browser could not be created. Try again creates a replacement.

Source: https://nevazu.com/docs/browsers


---

# Using the live view

> Controls, keyboard, touch, clipboard and reconnecting.

The live view streams the remote Chrome with WebRTC. Your keyboard, mouse, touch and clipboard input is sent in order, and is never silently dropped.

## One place at a time

A browser can be controlled from one tab or device at a time. Opening it elsewhere shows “open in another tab” with Use here to take over.

## Touch screens

- Tap to click; swipe with one or two fingers to scroll.
- Tap a text field, a search box or the address bar and the on-screen keyboard opens by itself, with the field’s own layout (email, numbers, web address), also for a field the page opens a moment after your tap; tapping outside any field closes it again. It stays closed while you type on a hardware keyboard.
- Capitals arrive as you type them, with Shift or with Caps Lock on a hardware keyboard.
- The keyboard button in the toolbar shows or hides the on-screen keyboard yourself. A keyboard opened with it stays open wherever you tap, for pages that take typing outside a text field.
- Maximize hides the toolbar and gives the whole screen to the page; a small control in the corner keeps the keyboard and the way back a tap away. The maximized view stays within your browser (Add to Home Screen hides its address bar), because iPhone and iPad allow no typing in a fullscreen page.
- If the picture stops responding, More → Reconnect live view starts the connection again without leaving the page. Coming back to a tab that was in the background reconnects by itself.

## Typing other languages

Input methods (such as Chinese or Japanese) work: the composed text is inserted into the page. Send keys in the toolbar sends combinations like Ctrl+Alt+Del that your own computer would catch.

Chrome in your browser is in English. To have websites show another language, add it in Chrome’s own settings (chrome://settings/languages); the choice is kept with the browser.

## Clipboard

Copying in the remote browser fills your clipboard where your browser allows it. Use Paste from your clipboard to send text the other way.

## Reconnecting

If the connection drops, the view tries up to three times and shows the attempt number. If it still cannot connect, it shows a connection reference and a Retry button. Running means the machine is running; a remote desktop connection can still fail. If input delivery is interrupted, input pauses until you reconnect; earlier clicks and keystrokes are not replayed, so nothing is typed twice.

## Picture quality

The live view adapts to your connection without ever blurring the page: every step shows the browser at full resolution. It measures the connection every two seconds: round trip, lost packets, frames arriving and how much data gets through. On a good connection it runs at 30 frames per second. Above about 180 ms of round trip it sends a lighter picture at the same 30 frames per second; a long round trip alone never lowers the frame rate. When the connection cannot keep up (lost packets, frames not arriving, or delay rising well above its usual level), it goes straight to the step whose data rate fits what actually gets through: 30 frames per second with less data, then 15 and 10, still at full resolution so text stays readable. It returns once the connection has been steady, and undoes a step up within seconds if the connection cannot carry it.

At every step the page keeps the same size and layout in your window; a lower one only looks softer and sends less data. The remote page always follows the size of your window, and the connection details in the toolbar show the round trip and the picture being sent.

## Data use

The picture is H.264 video. Chrome, Edge and Safari play it; Firefox needs its OpenH264 plugin, which it normally installs by itself. Data depends on what changes on screen: the picture sends only what changes, at most about 1.35 GB per hour at full while video or animations fill the screen, about 0.45 GB per hour reading and scrolling text in our tests, and very little on a still page. The lower steps send at most about 0.8, 0.55 and 0.35 GB per hour. Data sent from the browser is charged per GB.

Source: https://nevazu.com/docs/live-view


---

# AI agents

> Let an AI agent work in your browser while you watch, with nothing to install.

An AI agent such as Claude Code, Cursor or Codex can work in your Nevazu browser: it takes screenshots of the whole remote screen, clicks, types, scrolls, presses shortcuts and uploads files, in the same Chrome with the same sign-ins you use in the live view. You watch in the live view at the same time, and your own click takes control back at any moment.

## Turning it on or off

Allow connections is ticked when you create a browser; untick it to create a browser no AI agent or chat app can ever reach. In a browser’s Settings → Agent access the same switch can be changed later: turning it off disconnects all AI agents and chats at once and keeps their sign-ins for when you turn it on again.

## Connecting an agent

Nothing needs to be installed, and your agent sets itself up. Each browser has its own server address for the Model Context Protocol (MCP), which AI agents use to reach tools. The agent connects to it over HTTPS and signs in with your Nevazu account, which you approve in your web browser; there is no key to store.

On the browsers page or the Agents page, choose the robot button on a browser, or Connect an agent. The Agent Connection panel has three sections: Use in chat (Claude, ChatGPT and other chat apps), Use with agents (Claude Code, Codex, Cursor and other AI agents, open by default) and Use in your own app (the MCP server itself, for your own code).

## Signing in

- Under Use with agents, copy the setup for your agent and paste it into Claude Code, Codex, Cursor, OpenCode or any other AI agent. It holds only the server’s name and address, and points the agent to AI agent setup, where it finds the sign-in steps for its own client and adds the server itself.
- When the agent connects, or when you start its sign-in (in Claude Code: /mcp, then the server, then Authenticate), a Nevazu page opens in your web browser. Sign in to Nevazu first if it asks.
- The page names the app and where it will return. Choose whether the agent may act or only look, and how long the sign-in lasts: 1, 7, 30 or 90 days, 7 by default. Then choose Allow. If connections are off for the browser, allowing turns them on.
- The agent stays connected until the time you chose and renews its access by itself. After that, sign it in again the same way.

Nevazu emails you each time an agent signs in. If the page says the app’s name is not verified and you did not just start a sign-in from your own agent, choose Deny.

To configure an agent yourself, open Set it up by hand: it shows the command or configuration file for each client, already filled in for that browser.

## Using it in a chat app

Chat apps that can add a remote MCP server, such as Claude (claude.ai and Claude Desktop) and ChatGPT, connect the same way. Under Use in chat, copy the server URL and follow the steps for your app: in Claude, Customize → Connectors → + Add → Add custom connector; in ChatGPT, Plugins → + → Add custom MCP server, with OAuth, then Create as a plugin. The app opens the same Nevazu approval page. [Claude: custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) [ChatGPT: add an MCP server](https://developers.openai.com/plugins/deploy/connect-chatgpt)

## Using it from your own app

Use in your own app gives the server URL and how it authenticates, for a script, an app or a self-hosted AI agent of your own. The server speaks MCP over Streamable HTTP and uses OAuth 2.1 with PKCE (MCP authorization): a request without a token gets a 401 whose WWW-Authenticate header names the protected resource metadata, which in turn names Nevazu as the authorization server. Clients register with Dynamic Client Registration or a Client ID Metadata Document, ask for browser:control or browser:view, and send the access token as Authorization: Bearer.

## Access keys

Access keys are no longer offered: new connections sign in. Keys created before keep working until they expire or you revoke them, and are listed with the browser’s connections.

## Disconnecting an agent

The browser’s Settings → Agent access lists its connections, with who is driving, when each ends and when it was last used. Disconnect one there at any time, or open Agents in the dashboard’s sidebar: it shows every agent of all your browsers, which one is working now and who has control, and lets you pause an agent, hand control back, or disconnect agents one at a time or all at once. A disconnected agent loses access at once, even mid-task. Deleting the browser or signing out on all devices also disconnects its agents.

> **Note:** A key or a sign-in works only for the browser it was made for. Treat a key like a password: anyone who has it can see and act in that browser with your sign-ins.

## Who is driving

While an agent is connected, the live view says who is driving: a green outline around the picture while the agent is in control, a blue one while you are, and the robot button in the toolbar, whose menu holds the choices below. A short notice appears when control changes; it closes by itself. When the agent asks for control while you have it (it tried to act, or it is waiting for you), a speech bubble points at the robot button: tap or click the button to hand control back, or choose Not now to keep working; the bubble also goes away once the agent stops asking. Any click, key, scroll, paste or dropped file of yours takes control from the agent before it is carried out: the agent’s remaining steps are cancelled, keys it was holding are released, and it is told it lost control. Moving your mouse without clicking does not take over, so the page the agent is looking at does not change under it.

Once you have taken over, the agent stays paused until you choose Hand control back, in the robot button’s menu, on the Agents page or in Settings. Closing the live view, reconnecting, or the agent reconnecting does not hand control back. When you hand it back, the agent takes a fresh screenshot before it continues; nothing it had queued before is resumed.

Privacy pause goes one step further: besides pausing input, no screenshot reaches the agent until you end the pause. Screenshots the agent already received cannot be taken back.

## Screens and coordinates

The agent sees the whole remote display, including tabs, the address bar, menus and file dialogs, scaled to a size models read reliably; the coordinates it sends are mapped back to the real screen. Every action names the screenshot it was decided on: if your window changed the remote screen size or you took control since, the action is refused and the agent takes a new screenshot. Resizing never takes control away from it.

## Files

To give the browser a file from your computer, the agent asks for a one-time upload address and sends the file with curl, which comes with macOS, Linux and Windows; small files can also be sent directly. Uploading only copies a file to the browser’s temporary storage; attaching it to a page (into Chrome’s file dialog, by paste or by drop) needs the agent to have control at that moment. Temporary files are removed when the agent’s session ends.

## What the agent can do

The agent has the same reach as you at the keyboard and mouse: every website you are signed in to, including anything those accounts allow (reading, sending, buying, deleting). Give an agent only tasks you would do yourself, watch it in the live view, and prefer a separate browser with its own sign-ins for agent work. Every request the agent makes (a screenshot, an action, a file, a status check) counts as activity, so a browser an agent is working in does not go to sleep, even when nobody is watching. An idle connection does not keep it awake: once the agent stops making requests, the browser sleeps on its usual timer.

Source: https://nevazu.com/docs/agents


---

# AI agent setup

> For AI agents: how to add a Nevazu browser to your own MCP configuration in Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, OpenCode or any other client.

This page is written for agents, and for anyone who wants to see what their agent will do. A Nevazu user hands their agent a short setup from a browser’s Agent Connection panel. It names the server (for example nevazu-work) and its URL (https://connect.nevazu.com/mcp/ followed by the browser’s ID). A setup for an access key also names the environment variable that holds the key (for example NEVAZU_WORK_KEY), in this standard form:

mcpServers:
```
{
  "mcpServers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${NEVAZU_WORK_KEY}"
      }
    }
  }
}
```

The examples below use these names. Use the ones from the setup you were given, and follow the section for the client you are. A setup with no key variable is for signing in: follow Signing in instead of a key.

## Rules

- The user creates the access key and saves it in the environment variable themselves. Refer to the variable as shown for your client. Never ask for the key, print it, or write its value into a file or a message.
- Add the server to your user-level configuration, so it works in every project, and keep the servers already there: merge into an existing file rather than replacing it.
- One server per browser: each browser has its own name, URL and key variable.
- Most clients load MCP servers when they start. Tell the user if you must be restarted. The variable must be set in the environment the client starts from: a new terminal has it; an app opened from the Dock or the Start menu may need to be quit and opened again.
- Check the connection with the server’s get_status tool, then take a screenshot to see the browser.

## Steps for each client

### Claude Code

Run this in a terminal. The user scope makes the server available in every project. The single quotes keep ${NEVAZU_WORK_KEY} as written, and Claude Code expands it each time it starts. Check with claude mcp list; the server is loaded after a restart.

Terminal:
```
claude mcp add-json --scope user nevazu-work '{"type":"http","url":"https://connect.nevazu.com/mcp/BROWSER_ID","headers":{"Authorization":"Bearer ${NEVAZU_WORK_KEY}"}}'
```

### Codex

Add this to ~/.codex/config.toml (create the file if it is missing). Codex sends the value of the named variable as the bearer token. The same in one command: codex mcp add nevazu-work --url https://connect.nevazu.com/mcp/BROWSER_ID --bearer-token-env-var NEVAZU_WORK_KEY. Check with codex mcp list; the server is loaded after a restart.

~/.codex/config.toml:
```
[mcp_servers.nevazu-work]
url = "https://connect.nevazu.com/mcp/BROWSER_ID"
bearer_token_env_var = "NEVAZU_WORK_KEY"
tool_timeout_sec = 90
```

### Cursor

Merge this into ~/.cursor/mcp.json, keeping any servers already there. Cursor substitutes ${env:NEVAZU_WORK_KEY} when it starts. The server appears in Cursor’s MCP settings, where it may need turning on.

~/.cursor/mcp.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${env:NEVAZU_WORK_KEY}"
      }
    }
  }
}
```

### VS Code

Merge this into the user MCP configuration (the command MCP: Open User Configuration) or into .vscode/mcp.json, keeping the entries already there. The first time the server starts, VS Code asks the user for the key and keeps it in its secret storage; the user pastes the value of NEVAZU_WORK_KEY there.

MCP: Open User Configuration:
```
{
  "inputs": [
    {
      "type": "promptString",
      "id": "nevazu-work-key",
      "description": "Nevazu access key (NEVAZU_WORK_KEY)",
      "password": true
    }
  ],
  "servers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${input:nevazu-work-key}"
      }
    }
  }
}
```

### Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, keeping any servers already there, then refresh the MCP servers in Windsurf. Windsurf substitutes ${env:NEVAZU_WORK_KEY}.

~/.codeium/windsurf/mcp_config.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "serverUrl": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${env:NEVAZU_WORK_KEY}"
      }
    }
  }
}
```

### Gemini CLI

Merge this into ~/.gemini/settings.json, keeping the settings already there. Gemini CLI expands ${NEVAZU_WORK_KEY} from the environment when it loads its settings. Check with /mcp.

~/.gemini/settings.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "httpUrl": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${NEVAZU_WORK_KEY}"
      }
    }
  }
}
```

### OpenCode

Merge this into ~/.config/opencode/opencode.json (or opencode.json in a project), keeping the configuration already there. OpenCode substitutes {env:NEVAZU_WORK_KEY} when it loads its configuration; oauth: false stops it from trying to sign in with OAuth.

~/.config/opencode/opencode.json:
```
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nevazu-work": {
      "type": "remote",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "enabled": true,
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:NEVAZU_WORK_KEY}"
      }
    }
  }
}
```

### Any other client

Any client that speaks MCP over Streamable HTTP connects with the URL and an Authorization header carrying the key. Use the client’s own way of reading an environment variable; if it has none, tell the user where to put the key themselves. The curl command checks the key by listing the tools.

Any MCP client (Streamable HTTP):
```
URL: https://connect.nevazu.com/mcp/BROWSER_ID
Header: Authorization: Bearer <the value of NEVAZU_WORK_KEY>

# Check the key (lists the tools):
curl -s https://connect.nevazu.com/mcp/BROWSER_ID -H "Authorization: Bearer $NEVAZU_WORK_KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

## Signing in instead of a key

A setup for signing in names the server and its URL but no key variable:

mcpServers:
```
{
  "mcpServers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}
```

Add the server by its URL alone and let your client sign in with OAuth, the authorization MCP defines. On the first connection the server answers 401 with where to sign in, your client registers itself, and a Nevazu page opens in the user’s web browser, where they approve the agent and choose how long it lasts (1, 7, 30 or 90 days). Your client keeps the tokens and renews them. When the sign-in ends or the user disconnects it, the server answers 401 again and the user signs in once more.

- Do not add an Authorization header, an environment variable or a key. Never ask the user for a key or a token.
- The rules above still apply: the user-level configuration, keeping the servers already there, one server per browser.
- If your client signs in only when the user acts (a command or a button), tell the user exactly what to run or press. If you cannot open a web browser yourself, give the user the link your client prints.
- Once the user has approved, check the connection with get_status, then take a screenshot.

### Claude Code

Run this in a terminal, then restart Claude Code. In Claude Code, /mcp lists the server as needing authentication: choose it, then Authenticate, and the sign-in opens in the user’s web browser. Claude Code keeps the tokens and renews them.

Terminal:
```
claude mcp add --transport http --scope user nevazu-work https://connect.nevazu.com/mcp/BROWSER_ID
```

### Claude app

For Claude on the web, desktop or mobile: in Customize → Connectors, choose + Add, then Add custom connector, give it a name and paste this URL, keep the detected OAuth sign-in, then Add and Connect. The Nevazu page opens to approve it. On a Team or Enterprise plan, an owner adds the connector first under Organization settings → Connectors; members then choose Connect under Customize → Connectors.

Customize → Connectors → + Add → Add custom connector:
```
https://connect.nevazu.com/mcp/BROWSER_ID
```

### Codex

Add this to ~/.codex/config.toml (create the file if it is missing), then run codex mcp login nevazu-work in a terminal: Codex opens the sign-in in the user’s web browser and keeps the tokens. The same server in one command: codex mcp add nevazu-work --url https://connect.nevazu.com/mcp/BROWSER_ID. If Codex says login is not supported, update it.

~/.codex/config.toml:
```
[mcp_servers.nevazu-work]
url = "https://connect.nevazu.com/mcp/BROWSER_ID"
tool_timeout_sec = 90

# Then sign in from a terminal: codex mcp login nevazu-work
```

### Cursor

Merge this into ~/.cursor/mcp.json, keeping any servers already there. Cursor’s MCP settings show that the server needs to sign in; choose its button (Connect or Login), and the sign-in opens in the user’s web browser and returns to Cursor.

~/.cursor/mcp.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}
```

### VS Code

Merge this into the user MCP configuration (the command MCP: Open User Configuration), keeping the entries already there. When the server starts, VS Code asks to allow it to sign in, opens the Nevazu page, and keeps the sign-in under Accounts.

MCP: Open User Configuration:
```
{
  "servers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}
```

### Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, keeping any servers already there, then refresh the MCP servers in Windsurf. Windsurf opens the sign-in when the server first connects; if your version cannot sign in, update Windsurf.

~/.codeium/windsurf/mcp_config.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "serverUrl": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}
```

### Gemini CLI

Merge this into ~/.gemini/settings.json, keeping the settings already there. Gemini CLI finds the sign-in when it connects; if it does not start by itself, run /mcp auth nevazu-work.

~/.gemini/settings.json:
```
{
  "mcpServers": {
    "nevazu-work": {
      "httpUrl": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}
```

### OpenCode

Merge this into ~/.config/opencode/opencode.json (or opencode.json in a project), keeping the configuration already there. OpenCode starts the sign-in when it connects; opencode mcp auth nevazu-work starts it by hand.

~/.config/opencode/opencode.json:
```
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nevazu-work": {
      "type": "remote",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "enabled": true
    }
  }
}
```

### Any other client

Any client that implements MCP authorization (OAuth 2.1 with PKCE) signs in by itself. It finds Nevazu from the 401 response, registers with Dynamic Client Registration or a Client ID Metadata Document, and returns to a local callback (http://127.0.0.1 or localhost, any port), its own app scheme, or claude.ai, chatgpt.com or vscode.dev. In ChatGPT (Plugins → + → Add custom MCP server), enter the browser’s MCP URL as the MCP server URL and choose OAuth.

Any MCP client (Streamable HTTP):
```
URL: https://connect.nevazu.com/mcp/BROWSER_ID
No header: the client signs in with OAuth (MCP authorization), which it discovers from the server.
```

## If it does not connect

- 401 Unauthorized: the key did not arrive or is not valid. The variable may be empty in the environment the client started from (the literal ${…} is then sent), or the key was revoked or has expired. Keys can no longer be created: switch to signing in (see Signing in instead of a key).
- 401 Unauthorized with a sign-in: it has ended or the user disconnected it. Start the sign-in again as shown for your client; the user approves it again.
- The Nevazu page says the request cannot be approved: it gives the reason, such as a callback Nevazu does not accept. Use a local callback.
- 429 Too many failed attempts: wait a minute before trying again.
- A tool says the browser is not running: ask the user to open it in Nevazu. An AI agent cannot wake a sleeping browser.
- A tool says AI agent access is off: the user turns on Allow AI agents to connect in the browser’s settings.

Source: https://nevazu.com/docs/agent-setup


---

# Storage

> How much space a browser has and how to add more.

A new browser has a 10 GB encrypted data volume for your profile and downloads, plus a system disk for the operating system and Chrome. Both are included in the storage charge.

## Adding storage

Open the browser’s Storage tab, choose a new size and review the monthly cost before confirming. The volume grows while the browser runs or sleeps, with no restart.

- Storage can only grow, never shrink, up to 100 GB.
- Our cloud provider allows at most four changes in a rolling 24 hours, and only after the previous change has finished.
- Adding storage also raises the amount held from your balance for seven days of retention (see Billing).
- Space used is reported while the browser runs. Right after growing, the extra space can take a short while to appear.

## How storage is charged

Storage is priced per GB-month and charged for the actual time it exists, prorated by the seconds in each calendar month. Monthly amounts in the app are projections at the current size; nothing is charged for a whole month upfront.

Source: https://nevazu.com/docs/storage


---

# Billing and credit

> Prepaid balance, per-minute metering, held credit and what happens when credit runs out.

## Prepaid balance

Nevazu is prepaid, with no subscription. Add credit from Billing & usage; you choose the amount on the payment page. Payments are processed by Stripe, or by Creem as our merchant of record (the payment page shows which), with receipts and any VAT or sales tax. Before your first payment, and again whenever the Terms of Service or Privacy Policy change, you agree to the Terms of Service and Privacy Policy, and confirm you are not subject to sanctions, before going to the payment page. Unused credit stays on your balance.

## What is charged

- Compute: per minute while the browser is awake, including the minute or so it takes to start Chrome when it wakes and to save your profile and shut down when it sleeps (AWS charges for the machine then too).
- Dedicated IP: per hour for as long as the browser exists, awake or asleep.
- Storage: per GB-month for the data volume and system disk, prorated by time.
- Data sent: per GB sent from the browser to the internet, mostly the live view, and the profile backup uploaded when it sleeps. It includes the fee of the relay that carries the live view to you.

Prices are the public AWS list prices for the region times a published multiplier for each kind of cost; the pricing page shows the list price, the multiplier and your price for every item. Every price you are shown before an action carries a version; if prices change before you confirm, we ask you to review the new price.

Hourly figures for fixed resources use 730 hours a month as a projection. Daily totals are by UTC date.

## Total, available and held credit

Your total balance is all your unspent credit. Part of it is held: for each paid browser, seven days of its IP and storage cost. Held credit is not a charge. It makes sure your data is kept safe if your available credit runs out, and it is released when the browser is deleted.

Only available credit (total minus held) pays for normal use. Creating or waking a paid browser needs a minimum of available credit after any new amount is held.

## When available credit runs out

- Paid browsers stop at once and their live views close. There is no unpaid grace period.
- Browsers and their data are kept for seven days. Held credit pays only the actual IP and storage cost during that time.
- We email you which browsers stopped and when each will be deleted, again after three days, and a final reminder a day before deletion. The Billing page and each browser show the same dates.
- To keep them, add at least the amount shown on the Billing page: your balance must cover every kept browser’s seven-day deposit plus the minimum balance. A smaller top-up is added to your balance but does not stop the deletion.
- Browsers stay asleep after you add credit, including Never sleep browsers. Open each one to resume it with the same data and IP; nothing restarts on its own.
- Otherwise they are permanently deleted, and any unspent held credit becomes available again.

The sidebar and Billing page show how long your available credit lasts at the combined spending of all your browsers. We email you once each when it falls below about 24, 6 and 1 hours, and the app shows a warning below 24 hours.

You can also get an email when your available credit falls below an amount you choose: turn on the low-balance email alert on the Billing page and set the amount. It is off by default, and no low-balance email is sent unless you turn it on. While it is on, you get one email each time credit falls below your amount.

## Refunds and disputes

Credit is non-refundable, except for duplicate or mistaken charges and where the law gives you a right to a refund; the Refund Policy has the details. A refund or a payment dispute takes the refunded amount off your balance; while a dispute is open the account is on hold.

Source: https://nevazu.com/docs/billing


---

# Account security

> Creating an account, email codes, passkeys, two-step verification and signing out.

## Creating an account

All you need is an email address. Choose Create account, enter your email, and open the link we send you within 30 minutes. The link works once. If your email already has an account, we send a sign-in code instead and take you to sign-in.

A security check may appear when you request an email. It completes in the background where possible and closes after sending. Checking your email address, using a passkey, entering an email code and two-step verification do not require another check.

## Email codes

You sign in with a one-time code sent to your email. There is no password to leak or reuse. Email codes always work, even after you add a passkey. If your email has no account yet, sign-in asks you to register without sending an email.

## Two-step verification

Turn it on in Account → Security with an authenticator app such as Google Authenticator, Microsoft Authenticator or 1Password. Scan the QR code, enter the first code to confirm, then save the ten backup codes shown. Each backup code works once.

We ask for the authenticator code at sign-in, right after the email code and before any session exists. We chose this point on purpose: a session made after the email code alone could already read your billing details or change settings, so asking later (for example only when opening a browser) would leave those unprotected. Asking once at sign-in protects everything, and keeps opening a browser fast.

- Choose Trust this device for 30 days only on a device you alone use. You still need an email code or a passkey.
- After five wrong codes the sign-in starts over; after ten, sign-in is locked for 15 minutes.
- If the code is rejected, check that your phone sets its clock automatically.
- Turning it off needs an authenticator or backup code. Replacing backup codes needs an authenticator code.
- Lost your phone and your backup codes? Contact support from your sign-in email; after we confirm it is you, we can reset it.

## Passkeys

Add a passkey in Account → Security. When you sign in, we offer it instead of an email code: confirm with your fingerprint, face or device PIN and you are in. Because a passkey already proves two things (the device you hold and you), it does not ask for the authenticator code. You can still choose to get an email code instead.

## Signing out

Sign out ends the session on this device. Sign out everywhere ends every session on every device and disconnects any open live views.

Source: https://nevazu.com/docs/security


---

# Troubleshooting

> What to do when something does not work.

## I did not get a sign-in code

Check spam. Codes expire after 5 minutes. After several requests you may need to wait a minute.

## My browser will not open

- Add credit if your available balance is used up; a paid browser needs available credit to wake.
- Waiting for capacity or Provider issue: we keep trying; check the Status page.
- Open in another tab: choose Use here.

## The network is paused

The browser’s IP check did not confirm its dedicated IP, so its network was paused to make sure no other IP is used. Choose Check again; if it persists, contact support.

If the browser stopped responding, the IP check cannot run at all, and the network is paused after 15 minutes without a passing check. Choose Restart browser: it starts the browser’s machine again, and the network resumes once the IP is confirmed.

## The picture is slow or blurry

Choose a region close to you or close other heavy network use; the picture already lowers its sharpness by itself while your connection is struggling. The latency shown when creating a browser is measured from your own network.

Source: https://nevazu.com/docs/troubleshooting


---

# Frequently asked questions

> What Nevazu is, who it is for, how it differs from a VPN, a local profile or a remote desktop, what it costs and how to start.

## What is Nevazu?

Nevazu is a persistent cloud browser service. Each browser is a real Chrome running on its own computer in the cloud, with a dedicated IPv4 address that no one else uses and encrypted storage that keeps your profile, cookies, extensions and sign-ins between sessions. You open it in a live view from a web browser on a desktop, tablet or phone.

## Who is it for?

Nevazu suits work that needs a browser to stay signed in and to show websites the same address every time, from whichever device you are on: accounts you sign in to once and keep using, or websites that need to see you in a particular country, since the IP is in the country of the browser’s region. It also suits tasks you hand to an AI agent such as Claude Code, Cursor or Codex, which can work in the same signed-in Chrome while you watch.

## Where do the browsers run?

On Amazon Web Services, in the region you choose when you create the browser. The browser keeps that region and its IP for life: websites see an address in that region’s country, and the browser’s clock uses the region’s timezone. The pricing page lists the regions open for new browsers and what a browser costs in each.

## What is the difference between Basic and Premium?

Only the machine. Basic runs on 2 vCPUs and 4 GB of memory, Premium on 4 vCPUs and 8 GB, so busy pages and many tabs have more room. The live view, the IP, storage and data work the same way. Premium has a higher running rate and is offered where the pricing page shows it; a browser keeps its machine for life.

## How is Nevazu different from a VPN or a proxy?

A VPN or a proxy changes the address your own browser connects from, while the browser, its profile and its data stay on your device. With Nevazu the whole browser runs in the cloud: websites see the browser’s own dedicated IP, and its profile is stored, encrypted, with the browser, so it is the same browser at the same address from every device you open it on.

## How is it different from a browser profile on my computer?

A local profile lives on one computer and reaches websites from whatever network that computer is on. A Nevazu browser keeps its profile in the cloud, opens from any device with a web browser, and always reaches websites from its own IP. When nobody uses it, it sleeps, and waking it takes about a minute.

## How is it different from a remote desktop?

Nevazu gives you a browser, not a computer to look after. It sets up Chrome on the machine, checks from inside Chrome that websites see the right IP, and keeps the profile on encrypted storage. The live view streams that Chrome with WebRTC, adapts to your connection without blurring text, and works with touch, on-screen keyboards, input methods and the clipboard.

## Is it a headless browser service for scripts?

No. Each Nevazu browser is a long-lived, visible Chrome that keeps its sign-ins and its IP between sessions. AI agents work in it the way you do, with screenshots, clicks and typing, while you watch in the live view and take control back with any click or key.

## Can an AI agent use my browser?

Yes, with nothing to install. Each browser has its own Model Context Protocol (MCP) server address. In the browser’s Agent Connection panel you copy the setup for Claude Code, Cursor, Codex, VS Code, Windsurf, Gemini CLI or any MCP client; the agent connects over HTTPS, signing in with your Nevazu account for as long as you choose. Chat apps such as Claude and ChatGPT connect the same way. It can take screenshots, click, type, scroll and upload files. Access can be turned off for each browser, and disconnecting an agent takes effect at once.

## How does pricing work?

Nevazu is prepaid, with no subscription. You add credit, and usage is taken from your balance: running time per minute while the browser is awake, the dedicated IP per hour and storage per GB-month for as long as the browser exists, and data sent per GB. Prices are the public AWS list prices for the region times a published multiplier, and the pricing page shows each of them. Seven days of each paid browser’s IP and storage cost is held from your balance, not charged, so its data is kept if your credit runs out.

## What does a sleeping browser cost?

Only its IP and storage. An idle browser goes to sleep after the time set in its settings (10 minutes by default): its computer stops, and its data and IP are kept. Deleting a browser stops all charges.

## How are my account and data protected?

You sign in with a one-time code sent to your email, so there is no password to leak; passkeys and two-step verification with an authenticator app are optional. Each browser runs on its own machine with encrypted storage, and every few minutes it checks from inside Chrome which IP websites see, pausing its network at once if the address is ever different. Payments are handled by Stripe or by Creem, our merchant of record, so card details never reach us.

## How do I start?

Create an account with just your email and make sure you have available credit (Billing & usage), then create a browser: give it a name, choose a region and review the estimated cost. Setting up usually takes 3–8 minutes, and the browser opens automatically once its IP check passes.

Source: https://nevazu.com/docs/faq


---

# Policies

## Terms of Service

The agreement between you and Nevazu when you use the service. Last updated 2026-10-24. Full text: https://nevazu.com/terms.md

## Privacy Policy

What we collect, why, and the choices you have. Last updated 2026-10-24. Full text: https://nevazu.com/privacy.md

## Refund Policy

Credit is non-refundable, except where the law or this policy says otherwise. Last updated 2026-10-24. Full text: https://nevazu.com/refunds.md

## Data Processing Addendum

How we process the personal data in your browsers on your behalf, for business customers under UK or EU data protection law, including what is not in place yet. Last updated 2026-10-24. Full text: https://nevazu.com/dpa.md

---

# Contact

> We usually reply within one business day.

- **Support** (support@nevazu.com): Questions about your account or a browser.
- **Billing** (support@nevazu.com): Top-ups, receipts and refunds. Include the email you sign in with.
- **Security** (security@nevazu.com): Report a vulnerability. Please give us time to fix it before disclosure.

Source: https://nevazu.com/contact