Skip to content
tomato

Tomato OS × Envelop

Message the machine.

Tomato is not a mascot in a chat list. It is the computer at the other end: Envelop runs inside Tomato OS, receives your message, and returns a reply labeled with the machine that answered.

Text Tomato in EnvelopSee what happens after Send
Animated Envelop browser demo showing a hello sent to Tomato and Tomato’s multi-message reply
Hello from EnvelopBrowser demo · a hello goes out and Tomato’s reply comes back

01 / After you press Send

Your browser does not pretend to be the computer.

Envelop keeps the message queued until a nearby verified bridge can reach the Envelop app inside Tomato OS. The Tomato CPU receives it there. A reply comes back with its origin attached.

If physical Tomato is away, your message waits. You may start a separate Virtual Tomato preview, but Envelop never converts an uncertain hardware attempt into a simulated success.

  1. 01YouWrite in Envelop
  2. 02QueueWait safely
  3. 03BridgeVerify Tomato
  4. 04Tomato OSOpen Envelop
  5. 05Tomato CPUReply with provenance

02 / Separation of powers

Each side does one honest job.

Tomato explains the machine. Envelop handles the conversation. The label on the reply tells you where those worlds met.

TOMATO

The computer

A custom 32-bit CPU, its assembly-written OS, and the Envelop endpoint that runs on it.

Inside Tomato OS
ENVELOP

The messenger

The public chat, identity, queue, unread state, typing feedback, and nearby bridge that carry the conversation.

Meet Envelop
THE REPLY

The evidence

Physical Tomato means completed hardware execution. Virtual Tomato means an explicit browser preview. A timeout means unknown.

Read the evidence boundary

03 / More than chat

Ask it to compute.

Supported language can become a bounded Tomato program. Envelop shows the interpreted request, program, bytecode, target, and result instead of hiding the work behind an answer.