A developer-facing JavaScript SDK
Web applications describe the task they need rather than implementing model runtimes, downloads, and hardware integration themselves.
- Requests
- Events
- Artifacts
Local AI infrastructure · In development
Oryn is a browser and engine initiative designed to let ordinary websites request AI models running on the user's own device.
JavaScript SDK
Permissions · Sessions · Streaming
Compute · Cache · Artifacts
ORYN / QUICK FACTS
01 / ARCHITECTURE DIRECTION
Oryn explores the boundary between web applications and local compute: a small interface for developers, a visible runtime for users, and models running on the device.
Web applications describe the task they need rather than implementing model runtimes, downloads, and hardware integration themselves.
The Oryn architecture coordinates permissions, model sessions, compatibility, resource state, streaming, and cancellation.
Local compute becomes an explicit capability of the browsing environment, with model storage and execution kept visible to the user.
02 / RUNTIME RESPONSIBILITIES
The architecture is aimed at giving applications a consistent way to work with local models without hiding what is happening from the user.
Give users a clear boundary between a website and local model execution.
Match a request with models and formats that fit the available runtime.
Design for model acquisition, reusable local storage, and lifecycle visibility.
Surface device constraints so applications can adapt before starting work.
Support long-running local jobs without turning the browser into a black box.
Move beyond text with outputs such as audio, files, and other generated assets.
03 / INTENDED USE CASES
Oryn's design work considers transcription, chat, and music generation—different workloads that need the same clear lifecycle.
DESIGN TARGET / Transcription
A note-taking website requests a compatible local speech model and receives text while audio is processed on the device.
04 / PRODUCT PRINCIPLES
Local AI should feel like a capability of the web—not a pile of runtime decisions every site has to rebuild.
Permissions, downloads, active sessions, and resource use should be understandable rather than silently buried inside a page.
Applications should express the work they need while the runtime handles model and device integration.
Local model execution does not mean every website is entirely local. Each integration still needs a clear account of its data flow.
DEVELOPMENT STATUS
Oryn is development work and product architecture. This site describes the direction of the system—not a claim that every capability is publicly released today.
Explore OCNO05 / COMMON QUESTIONS
Not as a generally available product today. Oryn is an active infrastructure and product-architecture initiative.
No. The architecture targets local model execution. A website may still use remote services, so each product must describe its own data flow clearly.
Current design use cases include speech transcription, language model chat, and music generation, with model compatibility treated as a runtime concern.