Storage built for AI.
Object storage, retrieval and persistent agent memory in one engine. Applications connect through S3-compatible APIs; agents access knowledge and memory through native MCP. Your team builds the application. Origon operates the datastore service.


What did we decide about the launch?
Launch plan.pdf
Begin with a small pilot group. Expand access in phases after reviewing feedback.
Planning session
Keep the rollout phased. Review the pilot before opening access to the wider team.
Rollout notes.md
Start with the pilot team and use their feedback to guide the wider release.
Source material and work history, together.
Store application data alongside the artifacts agents produce, execution records and the history of where information came from.
Knowledge extraction makes that material available for retrieval and use.

rollout-plan.md
launch/artifacts/rollout-plan.md
Lineage
Release review
Revised in session · Release agent
Jan 8
Planning session
Created in session · Release agent
Sep 12
Launch plan.pdf
Source document
Sep 2
Pilot feedback.pdf
Source document
Dec 15
Find information by meaning, words and relationships.
Three illustrative matches for a question about when access opens to everyone. By meaning, a planning session passage about bringing the rest of the company in after the pilot review. By words, a release checklist line containing access and everyone. By relationships, company-wide access follows the pilot review, which the release team owns.
| Capability | What it retrieves |
|---|---|
| Vector search | Relevant information by meaning, using HNSW |
| Full-text search | Matching words and phrases, using BM25 |
| Knowledge graphs | Connections between information across your sources |
Memory beyond the current task.
Agents can retrieve earlier decisions, commitments and lessons across tasks and sessions, including work completed months earlier.
Memory supports correction, configured retention and authorized deletion.

Planning session · September
Keep the rollout phased. Open access to everyone after the pilot review.
New session · January
Can we open access to everyone this week?
Recalled from Memory
Not yet. Access opens after the pilot review, and that review is still in progress.
How it comes together.
A maintenance application stores approved procedures and equipment records. An agent retrieves relevant guidance, saves its work-order draft with the source history, and records the reviewer’s decision. A later task can retrieve that decision and its context through memory.

Connect applications and agents.
-
S3-compatible APIs. Give applications access to objects and artifacts.
-
Native MCP. Give agents access to memory, sessions and lineage.
-
Access and protection. Access controls, personal-information detection and redaction govern how information is used.

S3-compatible API
PUT /launch/artifacts/rollout-plan.md
200 OK
MCP
Search memory · launch rollout
Planning session
Expand access in phases after the pilot review. Send feedback to first.
Storage across the cluster.
Erasure coding adds storage redundancy, replication distributes data across the cluster, and nodes communicate over QUIC. The engine has no external database dependencies.
-
Objects
S3-compatible API for applications to store and read files and artifacts.
-
Vectors
HNSW index for finding relevant information by meaning.
-
Full text
BM25 index for matching exact words and phrases.
-
Graph
Knowledge graph that connects information across your sources.
-
Sessions
Session workspaces that keep each task’s work and its history together.
-
Memory
Persistent agent memory that carries decisions and context across tasks and sessions.
See it work with your data.
Explore storage, retrieval and memory using representative files and tasks. We’ll work through capacity, access, retention and migration requirements for your application.