Orage combines execution, state, authority, and distribution in one deployable instance.
The model is replaceable. The product around it remains coherent.
Runtime
Node 24 and Hono
State
Durable tape, files, encrypted stores
Models
Provider-neutral agent loop
Surface
Public site, web head, channels, API
Inside the runtime
Each layer has one job.
01 Creator control
Instructions, skills, tool policy, model policy, voice, and product rules.
02 Agent execution
Streaming runs, tool calls, memory recall, files, usage, and recovery.
03 Product authority
Identity, permissions, secrets, budgets, confirmations, and isolation.
04 Product surfaces
A replaceable public site, signed-in web head, external channels, and stable APIs.
05 Durable history
An append-only event tape that makes runs, effects, and state inspectable.
Why the instance matters
The product owns its context.
Orage does not treat identity, memory, tools, or channels as loose integrations around a
chat window.
Isolated
One product keeps its identity, data, files, secrets, and resource limits apart.
Observable
Agent runs, tool calls, and delivery events produce durable records that can be
inspected and used to rebuild state.
Replaceable
Models, providers, heads, and channels can change behind explicit contracts.
Deployable
The runtime and its reference heads build into one Node box with durable data paths.
Current proof
Three completed paths.
Last reviewed
01
Shape behavior in the browser
A creator saved agent settings and a skill file. The next reply followed the chosen
plan, effort range, and ending.
What ran
Creator edit, durable save, then a matching agent reply.
Test scope
Signed-in creator flow, not public onboarding.
02
Complete a controlled WhatsApp path
Two signed inbound messages reached a creator-configured agent. Both replies were
sent, delivered, and read. The records survived restart and reload.
What ran
Inbound, agent run, outbound, delivery, read, and recovery.
Test scope
Provider test environment, not production messaging.
03
Constrain a specialist tool set
Ama's owner enabled 12 reviewed tools from a catalog of 111. In one live turn,
the agent used four approved tools and returned chart-specific details.
What ran
Hosted owner session, tool policy, four calls, and one reply.
Test scope
Owner-only pilot, not public audience access.
Replaceable heads
The website belongs to the instance.
The reference public site and signed-in web head ship beside the runtime. A custom site
can target the same static output boundary without changing the agent core.
Today
Static HTML built by Vite and served by the Orage box.
Contract
A site directory with an index, routes, and immutable assets.
Next
Agent editing needs preview, creator approval, publication, and rollback.
Next product boundaries
What still needs a supported path.
Public onboardingFrom an idea to a running product.
Production channelsProvider setup, billing, and offboarding.
Creator-controlled hostingSetup, recovery, and live migration.
Site publicationSafe agent edits with approval and rollback.
See the product built on top.
The runtime matters because people should receive a coherent product, not a harness.