Open Research Factory Is Live
Synth's Open Research Factory now has production proof: public research work can be published with a receipt, bundle, and private-work firewall.
Archived: Open Research and its public proof routes were retired on July 25, 2026. This post remains as a historical launch record.
What Shipped
Open Research Factory is the public-release lane for research work that should be inspectable by customers, collaborators, and the broader research community.
The production proof covers three launch-critical properties:
- a public factory can create a completed research run
- the run can publish a reviewable receipt and artifact bundle
- a private factory created in the same proof remains blocked from public experiment, bundle, and project routes
The public proof run is available here:
The production proof run was retired with the Open Research product.
What You Can Inspect
This is a release-readiness proof, not a benchmark-performance claim. It proves the public/private publishing path and the shape of the artifact a reviewer gets after a factory run completes.
Why It Matters
Most research automation demos stop at a transcript. The Open Research Factory leaves a public review object: a run page, a receipt, and a downloadable bundle.
That matters when a team needs to answer practical questions:
- What work was requested?
- What artifact was produced?
- Which route is public?
- Which related work stayed private?
- Can a reviewer download the proof instead of relying on a screenshot?
For launch, those questions matter more than a louder claim. The first public promise is that Open Research work can be published with provenance and privacy controls.
How This Fits Managed Research
Managed Research remains the hosted control plane for directed research runs, private customer work, and operator-reviewed workflows.
Open Research Factory is the outward-facing publication layer for work that should be visible. The same production system can keep private work private while publishing selected research outputs for public inspection.
Use Open Research when the result should be shared. Use private Managed Research when the work, repo, or artifact should stay inside your organization.
Launch Boundary
The current public claim is intentionally narrow:
That boundary is the product: publish only the work you mean to publish, and make the published work easy to inspect.
Try It
Apply for Managed Research access if you want Synth to run a private workflow against your own repo.