Partner Program

Grow a practice on infrastructure that needs you.

Origami runs the platform. Certified firms implement it, because that's how the product ships. For your firm it means every deployment is an engagement, every account grows without a new sale, and the people who invented the core pick up the phone.

What partnering gets you.

Revenue that recurs on both sides.

Implementation, custom connectors, hardware installation, and Proof of Value work land once, then licensing and resources recur against a deployment that keeps growing.

Work that's required, not requested.

The endpoints are APIs and SDKs, so writing code against them is the product. Your firm is how the platform lands, by design.

Deals scoped as deployments.

Engagements come out scoped and defensible instead of open-hours estimates. That's the kind of work that runs for quarters.

Accounts that grow themselves.

The ecosystem loop means every product feeds SDO back and makes the others smarter, so the second product doesn't need a new sale. It's already sitting in the deployment you built.

Credibility in the hard rooms.

Four deployment modes, from full cloud to air-gapped, and compliance built as architecture. Your team walks into security reviews with answers.

Six products, one deployment. Every one is an engagement.

SDO goes onto the customer's data residency host and everything else connects back to it. Customers buy the deployment, not the products, which is why every rollout starts with a team that can build.

1 · Foundation

SDO

Ingests from any source, learns the structure, builds its own tooling, and runs an always-on data scientist agent behind the command & control dashboard and the API everything else connects through.

2 · Included

Personal Assistant

A 24/7 assistant at no licensing fee. Every user makes the customer's intelligence layer richer, and everything it sees flows into their SDO instance.

3 · Orchestration

Virtual Executive

An AI manager for each department that sets goals, plans work, assigns, tracks, and hires and trains agents for the roles itself.

4 · Build

Vision Builder

Five agents (Architect, Engineer, QA, Reviewer, DevOps) with code review enforced, and the Reviewer clicks through the feature like a person before anything ships.

5 · Research

Research Platform

Lab management with structured data, provenance, and compliance for research-intensive organizations. Licensed per lab.

6 · Capture

Ambient Conversational Intelligence

Phone, messaging, and ambient voice sealed into signed, tamper-evident vCon containers with consent records, then fed into SDO. Installed hardware, enterprise only.

The ecosystem loop: SDO creates intelligence, the products act on it, and every product feeds SDO back. Every product makes the others smarter.

Mode 1

Cloud

The full stack lives in Origami colocation. Fastest way to start.

Mode 2

Hybrid

A full copy of the platform minus GPU at the customer site; inference stays with Origami. On-prem hardware is leased from Origami.

Mode 3

Tethered

Customer site with a controlled connection back. The middle path for regulated data that still wants platform updates.

Mode 4

Air-gapped

No connection at all. The hardest deployment to build and the easiest one to defend in a security review.

Compliance here is architecture, not badges. PHI is physically isolated on dedicated erasure sets; that's how the system is built, not a policy someone agreed to. The architecture is public-key-only and no human holds data keys. Our facility has SOC 2, and we'll show you the report.

How partnering works.

It follows the AWS model: toolbox, certification, directory. We're building it deliberately, and the first names in the directory are the ones buyers find first.

Certify

Certification covers the whole stack: deployment modes, APIs and SDKs, the data residency host, the ecosystem loop. The first outside firms are in training now.

Get listed

Certified firms appear in the public integration directory, where customers come looking for implementation capacity. It's how a firm gets found by buyers who need hands.

Co-market

We tell the deployment story together, through the directory and joint materials. The proof points on this page are available to certified partners building their own case studies.

Sell and implement

Certified partners sell and implement Origami products without an ownership stake. Deal structure and partner economics get confirmed in the certification conversation itself.

Recurring on both sides. Enterprise pricing has two parts. Licensing is the right to use the software, billed along each product's real value axis: per data domain, per manager, per lab, per device. Resources is the customer's dedicated intelligence compute and storage, floored at one person-month of compute and calibrated through a Proof of Value engagement.

Inference never shows up in licensing. All AI usage draws from the customer's own resources pool. Both parts recur, so your revenue does too.

Three engagements where the data was the problem.

The client names are under embargo. The work does the talking, and every one of these started as an implementation project rather than a signup.

Blind, then proven


Problem
2.3 billion rows of flattened, partially orphaned transaction data, with no document boundaries and no foreign keys.
Data
Transaction data across three silos: purchase orders, invoices, remittances, disputes, claims, contracts, and X12 EDI.
Stack
SDO
Time to live
10 business days from deal signed to data flowing.
Outcome
1.5 million candidates scored blind on the firm's own operating definitions (one silo, measured end to end). Parity against the firm's claim history: $209M agreed, $206M identified that was never claimed, $4M the firm claimed that our rules do not raise today. The proof of value became a complete backend replacement, and the firm is proceeding with a full platform build.
Partner read
When a client's data looks unfixable, that's an implementation project, not a subscription.
Case study

Thirty years of German, made queryable


Problem
A German medical equipment manufacturer changed hands across the Atlantic. Thirty years of institutional memory had to survive the move.
Data
Thirty years of German-language business and technical documents.
Stack
SDO
Outcome
The documents went into SDO and came out as a queryable corpus for the American successor.
Partner read
Cross-lingual legacy ingestion, scoped as a deployment instead of a consulting estimate with open hours.

Heard it coming


Problem
Needed to know when physical assets were about to fail, and to keep configuration management honest to what was really happening in the field.
Data
BMS telemetry, ambient conversation, phone calls, emails, and other communications, fused together in SDO.
Deployment
Cloud
Stack
SDO, Vision Builder, and ACI (hardware).
Outcome
Rebuilt the client's proprietary stack in 7 days to include real time conversational analytics and pattern recognition across the fused signals. Functionality proven and demonstrated; awaiting client readiness for implementation.
Partner read
Multi-source fusion across OT data. The kind of engagement that runs for quarters.
Case study
Three sectors, same shape each time. What looked like unusable data turned into a scoped deployment, and now it runs. That's most of what an Origami practice will look like.

The people who built the core are still in the room.

Cody Launius and Jared Dyson invented SDO and hold the patent themselves, personally, so when a client asks who stands behind the platform you give them a name that answers. Jared built the core technology that now powers Walmart Connect and Sam's Club Connect. Cody built the platform from 2020 and sole-authored the IETF vCon use-cases draft. The model lineage grew from research work done together with collaborators from Google DeepMind, Stability AI, Runway ML, and Black Forest Labs, plus a partnership with IBM: fourteen models trained, three serving production today. The compute is ours (bare metal, single-tenant, in colocation facilities we own and run), and no human at Origami holds keys to customer data.

The Karpathy convergence. The SDO data model is a latent-space vector graph. Karpathy published the same structural principle realized in interlinked markdown. Two independent discoveries, different mediums, same structure. That's how you tell a fundamental shape from proprietary luck. Our founders hold the patent; he published the structure independently. If you're going to build a practice on a data model, this is the one the industry has converged on twice.

Who this is for.

We're keeping the program small on purpose.

Talk to our engineers first.

Tell us what you integrate and who you've shipped for. Certification starts when your technical leads talk to ours.