Design-partner path

Build a tool your team can make its own.

We’re developing tools for running models, training and reviewing releases. Tell us what your team needs to do and where its current tools fall short.

Three ways to contribute

Choose the work closest to yours.

Each candidate names what works today, what remains to be demonstrated, and the evidence required before delivery.

ERAIS Gateway

Could your team run a local model behind a controlled endpoint?

Duration: 6–10 weeks after gate
Availability: Gated design-partner candidate

Scope and terms

Can one approved workload use a controlled local endpoint with the required operational controls?

Test one approved local-model workload behind a controlled endpoint with explicit identity, capacity, audit, restore, and rollback behavior.

One approved workload and supported configuration. No OpenAI-wide compatibility, general availability, production SLA, or customer-operability claim before the gate passes.

See what’s included Register gateway design-partner interest

Training Workbench

Can someone else repeat the training and check the result?

Duration: 8–16 weeks after gate
Availability: Gated co-development candidate

Scope and terms

Can a second operator reproduce one bounded data-to-evidence workflow?

Make one local AI training workflow reproducible from approved data to a versioned checkpoint, evaluation, and evidence pack—then prove a second operator can run it.

One registered data-to-evidence workflow, environment, operator cohort, model/profile, rights set, and acceptance protocol. Not a general training platform.

See what’s included Discuss a workbench proof

Evidence Control

Can your next reviewer follow the work?

Duration: 6–10 weeks after gate
Availability: Gated design-partner candidate

Scope and terms

Can a repeated release-evidence process become a reviewer-operable workflow?

Turn one repeated AI release-evidence process into a controlled path from claim to artifact to test to approval—then prove a second reviewer can follow it.

One repeated release-evidence process, one minimum schema, file or bounded API-export integration, and one second-reviewer workflow. Not a generic governance or accreditation platform.

See what’s included Discuss evidence workflow discovery

What partnership means today

Make the next decision together.

First we check whether it fits your job. Then we look at whether your team can run it reliably, repeat the work and what support would cost.

General availability and service-level commitments require further reliability, operator and support testing. The individual product pages name the remaining work and conditions for a first engagement.

Catalogue source and review date

Discuss a project

Where would this help your team?

Describe the task, the people doing it and the result you would need to see. We can then work out whether a joint test makes sense.