Design Partners
Help shape the on-prem offering with us
InvarLock OSS is public and usable now. This page is for teams that want to work with us on the private on-prem review/control-plane layer and the support model around it before pricing and final packaging are locked down.
Best fit right now
Best fit right now
- You already review model edits before release and need stronger evidence around those decisions.
- Private or on-prem constraints will materially affect how the broader review workflow should be built.
- You are comfortable shaping the commercial path before pricing and packaging are finalized.
Engagement
How a design-partner engagement works
The goal is not to slot you into a finished package. It is to learn from real deployment and review constraints while keeping the OSS path available the whole time.
What to expect
- An iterative engagement, not a fixed SKU sheet.
- Direct conversations around workflow, deployment, and evidence review.
- Honest fit checks when the OSS path is the better answer for now.
Confirm fit
We start with your current review process, deployment constraints, and whether a design-partner conversation is the right path.
Map the workflow
We walk through how reports, verification, proof packs, and release gates map onto the review and evidence handoff process you already run.
Refine the on-prem path
Your feedback shapes the private layer and the support model around the OSS engine instead of being forced into a finished SKU sheet.
Current state
What exists today
- The public OSS engine, docs, GitHub repo, reports, verification flow, and proof-pack workflows.
- A direct path to evaluate model changes now without a pricing gate or sales process.
- A stable codebase that design partners can pressure-test against real deployment and review constraints.
Refinement
What design partners help refine
- The private on-prem review/control-plane layer that sits around the OSS engine.
- How deployment, upgrades, evidence review, and handoff should work in practice.
- What support and consulting should look like around the likely core on-prem offering.
Fit
Best fit
This path is for teams that already have a real review problem and want to shape the on-prem workflow around it, rather than waiting for a finished package list.
- Teams already reviewing quantization, merges, pruning, fine-tuning, or other model edits before release.
- Organizations with real private or on-prem infrastructure constraints.
- Groups willing to validate a stable codebase while the commercial shape is still being defined.
- Teams that want evidence for model changes, not just benchmark dashboards.
Not a fit
If one of these is true, the public OSS path or a later commercial conversation is probably the better route.
- You only want a public OSS quickstart with no partner discussion.
- You need a fully packaged commercial offer immediately.
- You are evaluating vendors only through finalized pricing and SKU comparisons.
Next step
Next step
If this sounds like the right fit, start with a direct conversation. If not, the OSS engine, docs, and evidence examples are already available now.