Product · Core

For the side of the desk that wants technical empowerment.

Orchid Code puts the same private model on your laptop. It works with the files, code and data you already have, runs where you work, and keeps everything on your machines.

What it is used for

Build applications and visualizers

Turn internal data into dashboards, tools and visualizers your team can actually use. The model reads your sources and builds the interface around them.

Write research code, strategies and signals

Pull data, test an idea, generate a signal and chart the result — all in the repository your researchers already work in, not a separate window they copy out of.

Work with files locally on your computer

It can read the spreadsheets, decks, PDFs and code sitting on your machine, so your own documents become part of the analysis without being uploaded anywhere.

Run it where your work already lives

The terminal, notebooks, editors and scheduled jobs you already use. Nothing is copied to an outside service, and nothing changes about the way you work.

Getting started

Two minutes, start to finish.

Everything a normal setup asks for — an endpoint, a provider, a model name — is already in place. Your team installs it and gets to work.

Keys are issued per person and checked before anything is written to disk, so leaving the firm removes the access.

First run

01$ orchid
02 
03 paste your key from Settings → API Keys
04 ▸ •••••••••••••••••••••••• validated ✓
05 
06 model orchid01
07 ready.
08 
09> value this target off the last three 10-Qs

Integrates into

Integrates into the way your team already works.

It meets your technical team where they already are, so nothing about the way they work has to change.

The terminal

Runs where your team runs everything else, on macOS and Linux.

Your editors

Works alongside the editors and coding assistants your team already pays for.

Notebooks

Available from the notebooks your researchers use day to day.

Existing pipelines

Called from scheduled jobs the same way any other internal service is.

Your repositories

Reads the code in place. Nothing is copied to an outside service.

The same model as Studio

Analysts and technical users work against one model, so results do not diverge by team.

Put it in front of your technical team.

We will install it live on the call and let them push it at a real workflow.