Managed environment
Use a separately agreed managed deployment where project policy permits it. Define isolation, model access, retention and support responsibilities.
Fit KlugSpice around the agreed data, model and infrastructure requirements. Define the deployment with the people responsible for engineering and IT.
Use a separately agreed managed deployment where project policy permits it. Define isolation, model access, retention and support responsibilities.
Run within a customer cloud environment with the agreed network, identity and repository connections.
Connect internal repositories and approved model infrastructure within the customer environment.
Plan an isolated deployment with locally hosted models and components where external network access is not permitted.
Availability and configuration are agreed for the project. The public marketing website and customer engineering environments are separate systems.
Configure the LLM or enterprise AI model for the deployment. Agree model access, processing location and operating responsibilities alongside repository, role and project-level access controls.
See the shared platform capabilitiesDeployment options include managed cloud, customer VPC, on-premises and air-gapped environments. The project agreement defines the available deployment, infrastructure responsibilities, model access and operating requirements.
KlugSpice supports configurable LLM and enterprise model options. The selected deployment determines which model endpoints or locally hosted models can be used and where processing occurs. Model availability and data handling are agreed during scope definition.
Tell us which task takes too much time. See how KlugSpice can help engineers prepare the work and review the result.