Can the cloud see my accounts' logins?

No. The login is encrypted on the computer with AES-256-GCM, and the key stays in the system keychain. Supabase stores only ciphertext and Vercel never receives it.

How does it pick the next account?

By the rule you choose: only at the limit, by threshold (warn and switch) or rotating through the day. Preference order, the backup account (only when nothing else is left), the hourly schedule and the weekly cap all apply.

What if I lose internet?

The computer keeps the current account and does not switch until the connection is back. The cloud is what decides the switch.

Can I use the same account on two computers?

An account stays with one computer at a time. The login is renewed on every use, and two copies at once would knock each other out. Reveza hands the account from one computer to another by returning the newest login to the vault first.

What if I lose all my computers?

The vault cannot be recovered: that is the price of a cloud that cannot read it. The accounts connect again through the official sign-in.

Does it work without a cloud?

It does. With --sem-nuvem the agent decides by itself on that computer, with no dashboard. You can add the cloud later.

Can I look before installing?

Yes. Demo mode (--demo) opens the dashboard with sample data generated in the browser, with no cloud and no account at all.

Who is responsible for how the accounts are used?

Each person is responsible for the use of their own accounts and for the terms of the AI service they use. Reveza AI is an open tool, not affiliated with any AI provider.

Open source (MIT) · in your own cloud

The account hit its limit.The session keeps going.

Reveza AI looks after several AI coding assistant accounts: it switches the account on your computer when the limit arrives (or earlier, if you prefer), keeps the logins in an encrypted vault and shows what each account delivered.

npx github:dantaspaulo/reveza

View on GitHub How it works

At a glance

macOS, Linux and Windows
Dashboard on Vercel, data on Supabase
English and Portuguese
Demo mode

The dashboard

Everything in a dashboard you own.

The account in use on each computer, burn rate, when each one runs out and what needs attention. The dashboard lives on your Vercel and the data on your Supabase.

Which account each computer is using, how much of the 5-hour window and of the week is gone, and the warnings that need action.

Dashboard in demo mode, with sample data.

painel.seu-dominio.com

Dashboard in demo mode, with sample data.

How it works

The login never leaves the computer in the clear.

The cloud stores only ciphertext and decides who uses what. The computer itself does the switch.

01 · Store

1
Official sign-in on the computer
You sign in to each account through the tool's official login, on your computer. Reveza never asks for an account password.
2
Encrypted right there
Each login is encrypted with AES-256-GCM under a key that lives only in the system keychain.
3
Vault in your cloud
Supabase receives only ciphertext. Neither it, nor Vercel, nor the project's author can read it.

02 · Switch

4
The cloud decides
Every minute, and the moment a limit warning arrives, it picks each computer's account by the rule you set.
5
The computer switches
The agent polls for the decision every 5 seconds (no open port), decrypts the login and swaps the local credential.
6
The session keeps going
The session that hit the limit resumes where it stopped, already on the new account. An alert can tell you what happened.

Features

What comes with it.

Everything you need to rotate accounts without thinking about it.

100%at the limit

Preference orderBackup account

Auto switch

Only at the limit, by threshold (warn and switch, for example at 90% and 95%) or rotating through the day. With preference order and a backup account.

1# Read the state
2BASE=seu-projeto.supabase.co/functions/v1/api
3
4curl -s $BASE/estado \
5  -H "Authorization: Bearer $REVEZA_CHAVE"

Responseexample

{
  "ok": true,
  "computadores": [{
    "nome": "Notebook",
    "conta": "trabalho@exemplo.com",
    "cinco_horas": 64
  }]
}

Webhooks

troca200
limite200
login_vence200
precisa_login200
sem_livre200
computador_parado200
resumo_dia200

API and webhooks

Personal keys with scopes (read, switch), revocable, and outgoing webhooks for n8n, scripts and whatever else you use.

Laptop switched accounts

now

work → personal · hit the limit

Account near the limit

now

work reached 90% of the 5 h window

Sign-in about to expire

now

client-a · no computer renewed it

Alerts where you are

Telegram, ntfy, email, webhook and phone push. Each channel picks the events it wants.

9:41

Reveza AI

Search accounts

Nownewest

Laptop · work → personal
hit the limit
work · 90% of the window
warning sent
Desktop · session resumed
on the new account
client-a · sign-in renewed
by the Server
Daily summary
today's usage and cost
personal · 58% of the week
on pace
Server · online
up to date

In your pocket

The dashboard installs on your phone's home screen (PWA), with accounts, usage and alerts at hand.

5 commandsRun

Command line

reveza status, trocar, uso --csv and doctor in the terminal. Inside the session, /reveza sums up the accounts and the status line shows the one in use.

Polls every 5 sOwn identity

Several computers

Laptop, desktop, server. Each one with its own identity, revocable on its own, and an account stays with one computer at a time.

English and Portuguese
Demo mode
Weekly plan
Team with roles and audit log
Spreadsheet export
Health of each computer

Security

The cloud stores it, but cannot read it.

Each account's login is encrypted on the computer. Whoever stores the vault does not hold the key, and the dashboard keeps no secrets.

AES-256-GCMTwo-factorRLS

Encrypted vault

AES-256-GCM with a fresh nonce on every write and the account bound to the ciphertext: one account's entry cannot be swapped for another's.

Two-factor sign-in
Required for admins. Public sign-up is off: only invited people get in, through a single-use link.
RLS on every table
Every action that changes something goes through a function that checks the role, validates the input and writes the audit log.
No secrets in the browser
The dashboard uses only the public key and the signed-in user's token, under a strict CSP. The server key stays in Supabase.
One identity per computer
Its own user, a long password in the keychain, revocable without touching the others. It only calls the cloud; no open port.

Who can see what

Can
Partly
Cannot

What

Your computer

where the account is used

Your cloud

Supabase and Vercel, in your name

Project author

whoever wrote Reveza

Account logins

Read an account's login

That is where it is used

Stores only ciphertext

Nothing goes through them

Vault key

In the system keychain

Never gets there

No copy exists

Link a new computer

6-word phrase

Key wrapped for 10 min, unreadable without the phrase

Nothing goes through them

Usage and control

Usage, accounts and decisions

What it reports itself

Only members of your team (RLS)

Nothing goes through them

Switch the account in use

Only it touches the credential

Decides and asks; the computer switches

No access

Per the architecture published in the repository (docs/ARQUITETURA.md). Swipe sideways to see every column.

Usage and cost

What each account delivered.

The agent reads each computer's transcripts and adds up tokens, replies, sessions, agents and equivalent cost, per hour, account, model, project and computer.

Equivalent cost, 30 days

Example

US$1,200

What the usage would cost at the API price list. Not a bill.

Tokens, 30 days

Example

480M

Input, output and cache, per account and per model.

Sessions, 30 days

Example

210

With the agents each one spawned and what each one cost.

Sample numbers. On your dashboard they come from your computers' transcripts, aggregated by the hour.

Install

One command. It asks and sets everything up.

Agent, accounts, cloud, dashboard, domain and alerts. You can start by just looking, in demo mode.

reveza · install

$ npx github:dantaspaulo/reveza

1/6checks the system: Node, keychain and the coding tool
2/6installs the agent and the session module
3/6connects the accounts through each one's official sign-in
4/6creates your cloud on Supabase: database, functions and vault
5/6deploys the dashboard to Vercel, with a domain if you want
6/6sets up alerts and runs the final check
→done: the dashboard opens and the computer answers

open source, MITmacOS / Linux / Windowsen and pt

Every installer option on GitHub

Requirements

Node 18 or newer

On macOS, Linux or Windows. The agent uses only Node's built-in modules.

Works with Claude Code

It must be installed on each computer that will rotate accounts.

Supabase and Vercel

Free accounts are enough to start. The installer creates the project and deploys the dashboard.

A domain, if you want

Optional, with a step-by-step guide on Cloudflare. Without it, the dashboard stays on the Vercel address.

Step by step

From zero to a live dashboard.

The installer walks you through it with questions, in the order below. Auto switch starts off: you turn it on when you want.

View on GitHub

Want to look first? Run it with --demo.

1
Run the command
It checks the system and installs the agent and the session module on the computer.
2
Connect the accounts
Official sign-in for each one, right there. Each account gets a color, a priority and, if you like, a backup role.
3
Create your cloud
With a Supabase token it creates the project, applies the database and functions and creates the admin with two-factor.
4
Deploy the dashboard
Sign in to Vercel and the dashboard goes live with security headers. Your own domain is optional.
5
Pick the alerts
Telegram, ntfy, email, webhook or phone, with a test message to confirm.
6
Final check
reveza doctor runs and a command from the dashboard reaches the computer. If it arrived, you are set.

FAQ

Frequently asked questions.

What usually comes up before installing. The rest is in the repository.

Reveza AI is open source and free, under the MIT license. Supabase and Vercel have free plans, and the installer works with them. Your AI service accounts stay yours, as they already are.

Get started

Your accounts, taking turns on their own.

One command, a few questions and the dashboard live in your own cloud. Nobody else's server in the middle.

View on GitHub See the dashboard

$npx github:dantaspaulo/reveza

The account hit its limit.The session keeps going.

Everything in a dashboard you own.

01Overview

02Auto switch

03Usage and cost

04Accounts

05Computers

The login never leaves the computer in the clear.

Official sign-in on the computer

Encrypted right there

Vault in your cloud

The cloud decides

The computer switches

The session keeps going

What comes with it.

Auto switch

API and webhooks

Alerts where you are

In your pocket

Command line

Several computers

The cloud stores it, but cannot read it.

Encrypted vault

Two-factor sign-in

RLS on every table

No secrets in the browser

One identity per computer

Who can see what

Account logins

Usage and control

What each account delivered.

Equivalent cost, 30 days

Tokens, 30 days

Sessions, 30 days

One command. It asks and sets everything up.

Requirements

Node 18 or newer

Works with Claude Code

Supabase and Vercel

A domain, if you want

From zero to a live dashboard.

Run the command

Connect the accounts

Create your cloud

Deploy the dashboard

Pick the alerts

Final check

Frequently asked questions.

01How much does it cost?

02Can the cloud see my accounts' logins?

03How does it pick the next account?

04What if I lose internet?

05Can I use the same account on two computers?

06What if I lose all my computers?

07Does it work without a cloud?

08Can I look before installing?

09Who is responsible for how the accounts are used?

Your accounts, taking turns on their own.