Research Platform

Run the entire research operation
— grants to compliance — in one platform.

Research Platform manages proposals, papers, experiments, data, supplies, and compliance for research-intensive institutions. The PI manages the lab through their personal assistant. The team works through the web interface. Every project gets its own specialist agent.

Interactive UI demo — mock data, no login, nothing you enter is saved.

Your lab runs on spreadsheets and institutional memory.

Grants are tracked in someone's head. Papers are versioned by filename. Data lives on three different hard drives. Protocols go stale the day they're printed. And when a researcher leaves, the knowledge walks out the door.

Deadline tracking in spreadsheets Fragmented manuscripts Data without provenance Institutional memory that leaves with people

Two ways in. One platform.

Different users, different needs — same platform. The PI gets the high-level view. The team gets the operational detail.

For the PI

Manage the lab through your personal assistant

The assistant handles scheduling, tasks, communications, and oversight. The PI focuses on the science.

  • "What's the status of Project Alpha?"
  • "Schedule the IRB review."
  • "Draft a proposal for the NIH R01."
For the team

Work through the web interface

Structured data and operations live here — the day-to-day of running the lab.

  • Experiment logging for protocols, procedures, and results
  • Standardized data collection with provenance tracking
  • Supply management: inventory, ordering, vendors
  • IRB forms, safety protocols, approval workflows
  • Dashboards for status, budgets, timelines, and milestones

See the platform.

Nine views of the research web interface — from lab-wide status down to a single project's workspace.

Screenshot pending
DashboardLab-wide status at a glance
Screenshot pending
GrantsActive portfolio and deadlines
Screenshot pending
Project workspaceOverview, scoped to one project
Screenshot pending
Project dataProvenance-tracked results
Screenshot pending
Reports & complianceAudit-ready records
Screenshot pending
Equipment & inventoryAvailability and maintenance
Screenshot pending
PapersThe manuscript pipeline
Screenshot pending
Lab chatAssistant scoped to the lab
Screenshot pending
Project chatSpecialist scoped to the project

Want to click around yourself?

Open the live UI demo

Interactive UI demo — mock data, no login, nothing you enter is saved. It shows the interface; it is not a working sandbox.

Grants to compliance. One platform.

Six domains that usually live in five different tools, a shared knowledge base, and a specialist for every project.

Proposals

A proposal writer that understands the requirements, structures the proposal, and produces submission-ready documents. Grants, RFPs, funding applications.

Papers

Drafts, co-author collaboration, review cycles, submission tracking, publication status. The assistant manages the timeline; the platform manages the content.

Experiments

Protocols, logging, results. Structured records linked to the data they produced, the supplies they consumed, and the compliance they followed.

Data

Structured storage with provenance. Where it came from, how it was collected, what produced it, who touched it. Shared within and across teams with access controls.

Supplies

Inventory tracking, ordering, vendor management, cost tracking. Know what you have, know what you need, know what it costs.

Compliance

IRB approvals, safety protocols, audit trails, regulatory requirements. The compliance record stays with the project from start to finish.

Every project gets a dedicated specialist.

Not a general-purpose chatbot that helps with whatever you ask. A specialist — exclusively assigned to that one project, with intense domain knowledge of its protocols, data, literature, compliance requirements, timeline, and milestones.

It helps with data analysis within the project, literature review, protocol drafting, results interpretation, and progress tracking. It's the project's resident expert — available to the research team through the web interface and to the PI through their assistant.

The specialist and the PI's assistant talk to each other. The assistant manages the lab. The specialist manages the project. The PI gets the benefit of both without having to coordinate between them.

Lab scope

The assistant answers for the whole lab: schedules, tasks, inventory, oversight.

Project scope

The specialist answers for its project only: protocols, data, literature, milestones.

They talk to each other

One conversation for the PI — the two agents coordinate behind it.

When the project closes, the knowledge stays.

When a research project is closed out and shut down, the Research Library stays behind. Everything the project produced — papers, data, experiments, proposals, findings, compliance records — gets archived in the library.

Searchable. Discoverable. Accessible to future researchers and future projects. Institutional knowledge doesn't walk out the door when a researcher leaves, and it doesn't get forgotten when the lab moves on to the next project.

The library grows with every project. The more research you do, the more valuable it becomes — patterns from old projects inform new ones.

Archived at closeout

Papers, data, experiments, proposals, findings, compliance records.

Searchable and discoverable

Future projects can find and build on prior work.

Outlasts the team

Knowledge stays when researchers leave.

Built for everyone in the research organization.

Four roles, one platform — each gets the part of it they actually need.

PIs

Your assistant gains a Grant Writer, a Protocol Writer, and an Academic Researcher. Your research data becomes a knowledge base it can access.

Lab managers

Inventory, procurement, compliance, scheduling — all in one platform. Budget tracking per grant.

Researchers

Each project gets its own workspace. Persistent chat. Specialized tools. Context-scoped to just your project.

Research administration

Audit trails, compliance monitoring, budget tracking — connected to the intelligence layer your researchers already use.

Deployed like an institution expects.

Origami Enterprise customers don't buy products — they buy a deployment. Every product connects to the customer's SDO instance, on the infrastructure where their data lives.

Data Residency host

SDO installs on your Data Residency host — the infrastructure where your data lives. Every product, Research Platform included, connects back to that instance.

Dedicated model inference

Not shared compute. Not multi-tenant. Your models, running on your infrastructure, processing your own data — one compute pool across all products.

Data domains

Logical barriers between datasets at your request — same platform, same deployment, strict boundaries between groups, programs, or sponsors.

Governance at the product level

Role-based access and approval workflows, audit trails and versioning, IRB and IACUC protocol workflows, compliance monitoring.

Licensed per lab — each research project workspace is a licensing unit, with one shared compute pool covering all products. Most institutions start with a Proof of Value engagement: a structured evaluation on real infrastructure with real data, before committing to a deployment.

Your research data is part of your institutional intelligence.

Each project specialist implements small-scale SDO within the project — its own mini-tesseract: structured data, intelligence, analysis. The specialist works inside the project without needing to go to central SDO.

Nothing flows up automatically. The PI decides what's ready to share — what findings, what data, what results are mature enough to contribute to the organization's intelligence layer.

When the PI shares, the data enters the full instance and cross-project, cross-domain patterns become possible across labs and departments. Control stays with the PI: sensitive research stays in the project until the PI is ready.

In the project by default

Each project runs its own intelligence internally.

The PI approves sharing

Findings move up when the PI says they're mature.

Cross-project patterns

Shared intelligence across labs — when you're ready.

Built with real researchers, for real researchers.

Developed with an independent panel of elite scientists across medicine, data science, and theoretical physics — including four principal investigators.

Chancellor's Professor Endowed Showalter Professor Medical journal Editor-in-Chief Fellow, American Association for Anatomy
$1.1B
A single grant approved on a proposal written by the platform's proposal writer.

One platform instead of five point tools.

Most labs assemble a stack out of pieces that were never designed to talk to each other.

ToolWhat it coversWhat it misses
BenchlingELN + LIMSExperiments only — not grants, papers, or supplies
ZoteroCitation managementCitations only — not the paper workflow
REDCapData captureData only — not lab management
Spreadsheets + institutional memoryEverythingSlow, error-prone, not searchable
Research PlatformAll six domainsConnects to your assistant, adds a specialist per project, gives every project a workspace

Questions institutions ask.

What does it replace?
The spreadsheet, document, and notebook stack across six domains: grants and proposals, papers, experiments, data, supplies, and compliance — plus the institutional memory that currently holds the rest together.
How do the PI and the team use it differently?
Two ways in, one platform. The PI manages the lab through their personal assistant — asking for status, scheduling, drafts. The research team works through the web interface, where structured data and operations live: experiment logging, data collection, supplies, compliance, dashboards.
Does research data leave the project?
No. Each project runs its own intelligence internally, and nothing flows up automatically. The PI approves what reaches central SDO — what's mature enough to contribute to the organization's intelligence layer. Sensitive research stays in the project until the PI is ready.
Does it work with tools we already use?
Yes. Citation managers, electronic lab notebooks, instrument data feeds, and grant portals connect to the platform, so existing workflows keep working while the record centralizes.
What happens to data when a project ends?
It's archived to the Research Library — papers, data, experiments, proposals, findings, and compliance records, searchable and discoverable by future researchers and future projects. Institutional knowledge stays after closeout.
How is it licensed?
Per lab: each research project workspace is a licensing unit. Deployment is sized to your vision — the data you want to connect, the capabilities you want to start with, the headroom you need. Contact us and we'll scope it with you.

Ready to see it on your research?

Tell us about your institution. We'll get back to you within one business day.