Telemetry
Off by defaultProduct telemetry is disabled by default. Customer-controlled operational monitoring and policy-required audit evidence are separate responsibilities.
BatonX / Deployment
Your environment. Your data boundary. Your approved models.
The first BatonX product is designed for customer-managed deployment rather than a multi-tenant hosted service.
Customer-controlled environment
Core services + retained evidence
Policy-approved model routeThe platform runs within your controlled environment.
Core services and retained evidence stay within the customer-controlled deployment. Model-bound context follows the approved endpoint.
Customer-managed deployment boundary
The BatonX administrative, gateway, runtime and data components run within the customer environment and connect only to approved model endpoints.
Customer environment
Admin Console
LLM Gateway
Isolated runtime
Customer data
Approved model endpoint
Cloud, private or internal
The infrastructure decisions remain yours.
Customers choose their infrastructure, network routes, backup approach, retention settings, model destinations and enterprise integrations.
- Infrastructure and network
- Database and storage
- Secrets and identity
- Backup and retention
- Monitoring and event destinations
- Models and enterprise integrations
A focused starting point. A clear deployment direction.
Initial deployments target a straightforward container-based installation. More advanced orchestration options can follow as product maturity and customer needs require.
On-premises and private-cloud environments are the initial model, with one customer organisation per deployment. Offline or restricted-network installation and signed offline updates are target capabilities; confirm readiness for your environment during pilot scoping.
Operational privacy starts with the defaults.
Telemetry is off by default. Remote support is off by default. Support material is created and shared by the customer through an explicit, auditable process.
Remote support
Off by defaultRemote support is disabled by default. The customer explicitly creates and shares support material through an auditable process.
Model location is explicit.
A customer-managed BatonX installation does not automatically make the selected LLM local. Admins can approve an external cloud endpoint, a private regional endpoint or a compatible internally hosted model.
External cloud
Required context may be sent to an organisation-approved external model endpoint.
An approved external destination
Private endpoint
Select an approved private or regional endpoint. Its location and data-processing terms still need review.
Location is explicitly configured
Internal model
Use an organisation-controlled model endpoint where the model and adapter capabilities have been validated.
Compatibility is individually validated
External-provider data handling depends on your provider agreement and configuration. “Customer-managed” is not a promise that every model request or integration remains internal.
Plan a pilot around your environment.
Agree the deployment boundary, approved model route and operational responsibilities before evaluating the developer workflow.
Discuss your deployment