Loading…
ORAVON IM
LIMITED ACCESS
Built around presence, context and governed execution — one adaptive intelligence, with expert control when you want it.
OIM works from the context you choose to bring, keeps the thread of the work, and does nothing you have not approved. Access is granted individually while the product is proven in real use.
Explore the engine
Tap a node to see what it does.
THE PROBLEM
Your memory, your knowledge, your work and your context are split across notes, apps, calendars and devices. Each tool is capable, and each one starts from zero — so you spend your day explaining yourself to software instead of using it.
THE SOLUTION
The workspace is being built around context you explicitly provide and structured artifacts. Typed conversation will join once the interactive path is production-verified. Durable memory, governed actions, voice, multimodal work, and native distribution remain clearly labelled as preview, in development, or future until their acceptance is complete.
ONE NAME, TWO PARTS
OIM is the manager you work in and the model families it draws on. Coordinating the work and carrying it out happens on ORAVON's own internal platform, which is not part of what you use.
The part you work in.
Context you choose to bring, the thread of the work kept between sessions, memory, presence, the workspace itself, and the tools and governed actions it can run. Each of those carries its own state on the capability map further down this page — none of them is finished, and the map says which is which.
The model families it draws on.
ORAVON's own model families. Today a family is a name and a lifecycle: all six are in preview, and not one of them carries a published measurement — no benchmark, no size, no cost, no capability score. Naming them is a commitment to build them in the open, not a claim that any of them has been measured.
Six families, all in preview. Not one of them carries a published measurement, so none is claimed here.
Not the product.
Coordinating the work and carrying it out happens on ORAVON's own internal platform. It is not sold, it is not what you sign in to, and it is drawn here only so the boundary is clear: OIM is the manager and the models; the platform beneath them belongs to the company, not to the product.
HOW IT WORKS
The intended experience is context in, and a response or structured artifact out. The interactive path is not available today, so this sequence shows the workspace grammar, not a live round-trip.
Write a question, a half-formed plan, or a decision you are considering. It is not sent today — the interactive path is not available.
The workspace is designed to use the context you provide to identify the kind of help requested.
If something important is genuinely missing, it is designed to ask — briefly, and at most a few questions. Never a form. Never as a habit.
The workspace path is built to support reasoning, drafting, analysis, and comparison. Other capabilities retain their maturity labels.
A quick answer is designed to stay in the conversation. Substantial work is designed to become a piece of work beside it — something you can open, copy, and keep.
Within the current workspace, the conversation is designed to continue while you refine or redirect the structured work beside it.
SEE IT WORK
A scripted replay of the workspace interface grammar. No request is answered in production today — the interactive path is not available.
Compare the two launch plans and recommend one.
Understood asDecide
Recommendation: the staged launch.
It reaches the same audience four weeks later but carries materially less risk — the full comparison is on the work surface.
Launch plan comparisonArtifact
Decision
Launch plan comparison
Recommendation
Next steps
Produced in this scripted replay — open, copy, download, refine.
CAPABILITY MATURITY
The capability map preserves the long-term direction while naming today’s workspace boundary.
What it takes in
Chosen context is available in preview. Durable memory foundations and explicit controls are in development; live recall acceptance remains open.
Long-term continuity across sessions and devices is a product direction, not a claim of current availability. Access is granted individually, and the experience is a private workspace.
WHO IT SERVES
Each entry below carries its current state. The capability map above carries the same truth per capability; this section is the reading of it a person actually needs.
OIM expands to ORAVON Intelligence Manager.
A private workspace in a Founder-only alpha. The guest workspace opens without an account; conversation inside it is not available today, so what a guest sees is the shell, the capability panel and honest state — not a working assistant.
Enterprise use is a direction, not a live offering. Specialist capability packs for real tenants are specified and being built; none serves an organization today, and there is no enterprise plan to buy.
Workspace state is persisted. Memory that carries across sessions is in development and is not claimed today — OIM does not say it remembers you, because it has never been measured doing so.
A presence renders in the workspace, in preview. It does not yet carry across the product's dimensions, and it is kept separate from inference so that being present never costs a model call.
Not available on this deployment. The workspace shows an honest unavailable state rather than a control that pretends to listen.
Actions are designed to be previewed and approved before they run — that path is built into the workspace. Hosted execution remains in development.
The design is one relationship drawing on bounded specialists, packaged as capability packs with declared permissions and verifiers — the SAP specialist is the reference build. No pack serves a real tenant today.
The capability map on this page and the panel inside the workspace are read from one measurement, not from two hand-written lists. The page publishes what holds for any reader; the panel publishes what this deployment measures for you, which is sometimes more. Neither is allowed to claim more than the measurement does. That reporting is real today.
Execution fingerprints exist in the pipeline but are not yet kept or shown to you, and answers carrying their sources depend on a research capability that is not built. Stated as direction, not as a feature.
Product Proof
Recreated the way the workspace itself draws them, not as generic illustrations. Every sequence below states its own current state, and none of the examples is a real person, a real result, or a measured outcome.
Continuity
Previous work
What you left open, each with when it was last touched (example).
Resumed state
Reopening carries the context that was already there — nothing re-entered.
Next action
You continue from exactly where the thread stopped.
Scripted preview — LIMITED. Earlier turns travel with each request, and threads are kept where this workspace can keep them. Sync to your ORAVON account and other devices is still being built.
Research
Question
“Compare two options and note the trade-offs.” (example)
Sources
Every claim would carry the source it came from.
Comparison
Options set side by side on the points that matter.
Artifact
The comparison becomes something you can open and keep.
Scripted preview — NOT AVAILABLE. Web search and reading are unavailable; answers can use only what you provide in the workspace.
Execution
Objective
“Send the update to the team.” (example)
Plan
Prepared as a concrete step, not run yet.
Preview & confirm
Shown in full, and armed only on a second, deliberate press.
Result
Recorded once you approve it — never before, and never on its own.
Scripted preview — LIMITED. Action previews and approvals are built into the workspace path; useful hosted execution remains in development.
Voice & Presence
You speak
The microphone opens only when you choose it (example).
Visible state
One state, always visible — present, working, or waiting on you.
Result
An answer or a piece of work, not a transcript alone.
Presence and 3D experience: Scripted preview — LIMITED. The integrated presence experience includes an accessible, low-power fallback and remains in development. Hosted voice: Scripted preview — COMING. Connected speech recognition and synthesis are planned; browser speech remains the fallback while they are developed.
Artifact
Intent
“Draft a one-page brief.” (example)
Work
The environment works while presence shows that it is.
Artifact
Substantial work becomes an object beside the conversation.
Refinement
Open it, copy it, and ask for changes.
Scripted preview — LIMITED. Safety-checked TXT and Markdown files can support reasoning; image, PDF, and DOCX understanding is planned.
WHERE IT IS TODAY
Access is granted individually while the product is proven in real use. Typed conversation and clarification are not available today; structured artifacts and honest capability reporting are what an approved person sees. Durable continuity foundations and explicit memory controls are in development and testing; live recall acceptance is still underway. Governed actions, voice, file workflows, desktop, and mobile remain in development. Web research, vision, and screen understanding are future directions. Request access to be considered; an ORAVON identity is required to enter, and permission is required before consequential execution.
ORAVON IM is in a Founder-only alpha and is not a commercial product — there is no public account, no trial, and no pricing.