No Teamcenter? No TrackWise? No problem. Caliber supports the current connector set plus scoped custom API or export paths, and can be planned for customer-controlled deployment in your private cloud or local environment.
Choose your deployment model
The core product is the same. Deployment scope changes based on the environment and integration path.
Recommended
Caliber Cloud
Fastest path to value
Managed SaaS for uploads, search, and workflow evaluation. Best fit for early pilots before private deployment scoping.
Caliber runs in customer-controlled cloud infrastructure with scoped access to internal systems. Current focus is secure pilot rollout for the Teamcenter + TrackWise wedge.
For private-cloud and on-prem deployments, this is the rollout path we use to validate the wedge before expanding scope.
1
Discovery call
We map your PLM/QMS landscape, document sources, and security requirements. Current wedge focus is Teamcenter + TrackWise, with file-based sources alongside it.
2
Connector configuration
We configure the connectors available today: Teamcenter, TrackWise, Windchill, Veeva Vault Quality, SharePoint, object storage, folders, or a scoped custom API path.
3
Pilot validation
We validate source access, run health checks, and test sample uploads and wedge workflows against your pilot dataset before broader rollout.
4
Expansion plan
Once the pilot is working, we sequence additional sources, workflow automation, and broader deployment controls with your team.
On-premise architecture
Illustrative private deployment layout for customer-controlled environments.
Validates access and moves pilot data through approved connector paths
Caliber stack (on-prem)
Core API
Orchestration, agents, query engine
Inference Engine
Extraction and reasoning services sized to the deployment scope
Retrieval + Graph Layer
Search, evidence retrieval, and graph context for engineering queries
Your engineers
Web UI
Chat, workflows, review packages
REST API
Integrate into CI/CD, PLM plugins
Audit Log
API request and decision records stored for audit review
Components are containerized; final network boundaries and controls are defined during deployment scoping.
Supported connectors
Current connector scope for pilot deployments. Teamcenter + TrackWise is the primary integration wedge today.
P
Teamcenter
PLM
Q
TrackWise
QMS
P
Windchill
PLM
Q
Veeva Vault Quality
QMS
F
SharePoint
File Store
F
S3-compatible object storage
File Store
F
Local / network folder
File Store
C
Custom REST API
Custom
Don’t see your system? We can scope a custom integration path after reviewing the API, export model, and pilot requirements. Get in touch.
Frequently asked questions
Do we need Teamcenter or TrackWise?
No. The current product supports direct uploads plus connectors for Teamcenter, TrackWise, Windchill, Veeva Vault Quality, SharePoint, object storage, folders, and custom APIs. Teamcenter + TrackWise is the primary wedge today.
Can Caliber run without internet access?
Private-cloud and on-prem deployments are scoped case by case. The current architecture supports customer-controlled deployments and connector gateway patterns, but a fully air-gapped package is not presented as a self-serve default.
How does Caliber handle sensitive / ITAR-controlled data?
For sensitive or export-controlled data, deployment scope is reviewed case by case. Current posture is customer-controlled deployment plus scoped connector paths; any data-handling controls are agreed during deployment scoping.
What if our PLM system isn't listed?
We support a scoped custom integration path when a source system exposes an API or a controlled export path. We size that work after reviewing the source system and pilot requirements.
How long does on-premise deployment take?
Deployment timing depends on the customer environment, security review, and source-system access. We normally start with a pilot plan and connector validation before committing broader rollout dates.
Request a private deployment plan
Tell us about your infrastructure and current systems and we’ll scope the right pilot deployment path.