Real access,on your terms.

Aldo needs real access to finish real work: your apps, your accounts, your files. It gets that on computers of its own, and you choose how each login and key reaches them, down to a stand-in it can use but never read.

  1. Your browser

    Signed in. Preview links open only for you.

    your session

  2. Aldo

    Keeps your sign-ins and vault, encrypted.

    tokens signed by the thread’s key

  3. The thread’s computer

    Agent, code, app and browser. Stand-ins for injected keys.

    the firewall adds the real key

  4. Your services

    GitHub, Stripe, your cloud: they see the real key.

It asks before anything that matters.

Paying, booking, cancelling and applying: asked every time, with the total and the terms. This is the card from Aldo’s Home screen, and its buttons work.

Q3 sales tax8 min

File the Q3 sales and use tax return

Needs your yesFrom Q3 sales tax· 8 min

File the Q3 sales and use tax return?

Where
CDTFA online services
Total
$18,412.07
Terms
Paid by ACH from the account on file on Oct 30. Once it's filed, a change takes an amended return.

Taxable sales of $201,402 after resale and out-of-state exemptions, from the Q3 sales export. The return is filled in on the portal and stopped at Review and submit.

A computer for each thread.

Agents need a real shell to do real work. Each one gets it on a computer of its own, and nowhere else.

Its own virtual machine
Every thread runs in its own Sailbox, with its own disk, processes and network. Threads never share a computer.
Saved when it sleeps
A thread that stops keeps its whole disk as a snapshot, restored when it wakes.
Signed both ways
Aldo reaches a thread’s computer only with short-lived tokens signed by that thread’s own key. The computer reaches Aldo only through an API of its own, with its own token.
You can take the wheel
The browser an agent drives runs on its own computer. While you’ve taken control, the agent’s input is refused.

Your accounts, connected once.

Aldo signs in with each provider’s own tools and keeps the result encrypted, never in the conversation.

Official logins
GitHub, Claude, Codex, Grok and Muse Code connect through each provider’s CLI login, run on a throwaway computer. GitLab, Bitbucket and Azure DevOps use an access token you create.
Stand-ins on the computer
Your GitHub and Claude sign-ins are added to requests by the computer’s firewall. The computer itself holds only stand-ins.
One refresh token, one place
Codex refreshes through Aldo, so its single-use refresh token is never copied onto more than one computer.
Aldo’s models, no key on the computer
Aldo’s own models go through Aldo with a credential made for that computer alone, which only spends your plan’s credits. Like your sign-ins, the firewall adds it to the computer’s requests, so the computer holds only a stand-in. They reach only providers that keep nothing you send and don’t train on it.

Secrets that stay sealed.

API keys, files and website logins, each sealed on its own. You choose how each one reaches a thread.

Sealed, and never shown again
Each item is sealed on its own with envelope encryption. Once saved, a value can’t be read back in Aldo’s app or API; you save a new one instead.
Three ways in
A variable in the agent’s shell and services, or a file at a path: the agent can read these. Or injected into HTTPS requests to the sites you list: the computer holds only a stand-in, so the agent can use the key but never read it.
Kept out of the record
Vault values never go into Aldo’s logs, events or responses to the browser. Service logs on the thread’s computer hide them.
Refused on the way out
A push, pull request, comment or caption that contains a vault value is refused before it leaves the computer.
Logins filled, not handed over
Aldo types a saved password into the page after checking the page’s origin. The agent asks for the fill; it never handles the password.
Asked for, not pasted in
An agent that needs a secret sends you a link to the Vault form. The value goes to the vault, never into the conversation.

Private unless you open it.

Everything a thread runs is yours alone by default. What’s public is public on purpose, and says so.

Owner-only previews
A preview link checks that you own the thread, then hands off with a single-use token. Dev server ports are never exposed.
Only the paths named
For webhooks, an agent makes just the path prefixes it names public. Responses can’t run as a page or set cookies, and callers’ cookies aren’t passed on.
Demos for reviewers
Recordings an agent attaches to a pull request are public at unguessable links, so reviewers can watch them.

Agents act within your policy.

What an agent may do on its own is learned from you, one question at a time, and Aldo holds it to that where Aldo is the one acting.

Merges on your terms
Aldo merges a pull request only when the workspace’s policy says to, once it’s been green for 10 minutes and the agent is idle.
Purchases wait in Link
Asked to buy something, an agent goes as far as the payment step. You approve the total in Link, and the card it gets works once, for that amount, at that store.
Asked every time
Paying, booking, cancelling a subscription or submitting an application: each comes to you first, with the total and the terms.
Money needs a yes
Above the threshold you set, an agent asks before it spends, and every spend is recorded. Usage-billed services get their own spending limit.
A ceiling on Aldo, too
Past a plan’s credits, extra usage stops at the limit you choose; past it, agents go on one at a time, free.

Each person’s work stays their own.

In a company, each person keeps their own account. Admins see what work costs and where it runs, and act on the record.

Aldo for companies
What admins see
Each person’s credits by thread and by day, and the titles, state and computers of threads started in the company. Never conversations, files or vault values.
What admins can do
Stop a thread’s computers, pause someone’s work or set their usage limit. Each action goes into the company’s Activity first, and the person is told.
Closed ways in
A domain proved by DNS, a short-lived invite link or a request an admin approves. Each ends in an invite to one address, so nobody gets past the seats.
When someone leaves
Their threads stay with the company: paused, then copied for a colleague with their own secrets taken out, or kept 30 days, then deleted.
Two people swimming in calm evening water

Work less. Do more.