When you're prototyping a workflow
Drop in a few documents, sketch your schema, and see results in real time before writing any integration code.
Studio
Build Document Pipelines Visually
Build, test, and deploy document pipelines without code. Ship to production with a Pipeline ID.
Helping everyone from startups to Fortune 10 enterprises unlock their data.
- Harvey
- Scale AI
- Newfront
- Medallion
- Vanta
- Legora
- Rogo
- Levelpath
- JLL
- Vise
- Laurel
- Toast
- Mercor
- Zip
- Anterior
- Supio
Studio
Design and test document pipelines
- Definition
- Studio is a visual environment for designing document pipelines: drag in documents, tune options, watch the output update inline, then deploy the same pipeline by ID from your application.
- Who it's for
- Engineers prototyping new document flows, ops leads tuning schemas as data changes, and PMs verifying output quality before launch.
- The problem it solves
- Document pipelines typically live as scripts, rebuilt every time a schema changes and validated only after deploy. Studio lets you see the output, adjust settings, re-run, and ship the same configuration to production with a Pipeline ID.
Studio in the platform
Using Studio with the API
Studio and the API work together. Configure in Studio, deploy with a Pipeline ID.
When non-engineers need to tune a pipeline
Ops teams, analysts, and domain experts can adjust chunking, OCR mode, or extraction fields directly in the UI without needing engineering support.
When you want to update production without changing code
Redeploy a pipeline in Studio and your application picks up the new version by the same Pipeline ID. Roll forward, roll back, or A/B test without touching your codebase.
Where AI teams ship in Studio
Pipelines that ship to production
Common workflows where Studio is faster than writing code.
Prototype new document workflows
Set up a document pipeline against real files in under an hour, then hand the Pipeline ID to engineering when the output looks right.
Let ops teams iterate on schemas
Let domain experts update schemas directly. Studio shows output side-by-side with the source.
QA pipeline output
Inspect citations, bounding boxes, and table reconstructions on the document itself.
Build multi-step pipelines
Chain multiple steps into a single pipeline. Each step gets its own preview and the whole thing ships under one ID.
Version pipelines for production
Every deploy creates a new version. The Pipeline ID stays the same, so your app picks up changes without a code change.
Compare pipeline configurations
Run the same document through two configs side-by-side to see where they differ, then keep the version that works best.
Build a pipeline on your own documents. Open Studio.
Why Studio
Why teams use Studio
- 01
Same engine as the API
Build a pipeline visually, then call the same configuration from your app via the Pipeline ID. Same engine, same results.
- 02
Visual feedback on every run
Citations, bounding boxes, and tables render on the source document so you can verify results visually.
- 03
Update without changing code
Redeploy in Studio and your app picks up the new version on the next call. Same Pipeline ID, full version history.
- 04
Usage-based pricing
Studio is included with every plan. You only pay for the processing your pipelines run, same credits as the API.
How Studio works
How Studio works in four steps
- STEP 01
Open Studio
Sign in at studio.reducto.ai. No setup, no install.
studio.reducto.ai - STEP 02
Create a pipeline
Pick the steps you need and name it. Every pipeline gets a stable ID at creation.
+ new pipeline - STEP 03
Upload & run
Drag in real documents, tune options, and watch the output update live. Save a version when it looks right.
▶ run · 12 docs - STEP 04
Deploy
Publish a new version with one click. Your app calls the API with the Pipeline ID and picks up changes automatically.
pipeline_id: k9798h9m…
Built for production
Built on the same infrastructure that runs the API
Studio runs on the same infrastructure that powers production AI teams. Every deployed pipeline is a versioned, production-grade artifact.
SOC 2 Type II & HIPAA
SOC 2 Type II covers the platform; HIPAA (with a BAA) on Growth + Enterprise. See the Trust Center and Enterprise readiness matrix.
Versioned pipelines & rollback
Each deploy creates a new version. Inspect or roll back from the Activity log. The Pipeline ID stays stable.
Role-based access & audit log
SSO/SAML, fine-grained roles, and audit logging are part of the Enterprise program. See plan matrix.
Same SLAs as the API
Pipeline runs share the same infrastructure as direct API calls. Uptime SLAs available on Enterprise.
Build a pipeline on your own documents. Open Studio.
The rest of the platform
The endpoints behind Studio
/parse
Parse
Turn any document into structured, citation-ready output. Tables, figures, OCR.
Read more/extractExtract
Pull defined fields and schemas out of documents with citations on every value.
Read more/splitSplit
Break long, multi-document files into logical units for downstream pipelines.
Read more/classifyClassify
Route or label files by document type before they hit a downstream pipeline, with per-criterion confidence.
Read more/editEdit
Fill PDF forms or update DOCX files with natural-language instructions via the Edit API.
Read moreFAQ
Common questions about Studio
Document work starts here
Try Studio on your own documents
Sign in, drop a PDF, see the results. No setup, no credit card.
