FAQ
Questions enterprise teams ask before putting AI near robots.
Clear answers on Kilnara’s platform, private deployment, training workflow, safety validation, security posture, pricing model, and onboarding process.
Where to start
Use the FAQ as a deployment checklist.
Enterprise robotics projects usually move through fit, integration, safety, commercial review, security review, and onboarding. The sections below follow that path so each stakeholder can find the answers they need.
For automation teams
Start with Platform, Deployment, and Training & safety to understand how Kilnara fits into existing cells.
For IT and security
Review Security & data, deployment choices, identity controls, and compliance status before procurement.
For business owners
Read Pricing and Support to scope pilots, expansion paths, and production response expectations.
FAQ
Platform
Kilnara creates a physics-aware digital twin of a robotic line, uses that twin to generate synthetic operating scenarios, retrains robot policies, validates them against safety and performance limits, and then supports controlled deployment to edge runtime.
It is a closed-loop platform rather than a replacement controller. The twin, training, validation, and operations layers connect to existing robots, controllers, cameras, PLCs, and plant systems through supported integrations.
Kilnara is strongest where change breaks automation: high-mix picking, assembly, machine tending, induction, bin handling, and cells affected by new SKUs, shifted fixtures, lighting changes, or gripper wear.
No. CAD helps accelerate twin authoring, but calibration can combine scans, robot geometry, camera data, process constraints, and observed telemetry to align the model with production behavior.
Telemetry from the cell is streamed back to compare expected and observed behavior. Drift signals, failed attempts, cycle-time changes, and operator interventions can trigger twin updates or new training scenarios.
Yes. Robotics and automation teams configure objectives, limits, and approvals while Kilnara handles the repeatable training and validation workflow. Advanced teams can review deeper metrics and artifacts when needed.
FAQ
Deployment & integration
Kilnara can be discussed as managed SaaS, single-tenant VPC, on-prem, or restricted-network deployment depending on data sensitivity, IT policy, and pilot scope.
Typical integrations include robot controllers, ROS 2 nodes, cameras, PLCs, OPC-UA, MES events, artifact stores, and enterprise identity providers. The exact plan is confirmed during technical discovery.
Most engagements start with offline discovery, historical data, scans, and a bounded pilot cell. Any live-line connection or deployment is scheduled with your operations team and change-control process.
Yes. Enterprises can manage plant-specific twins and policy releases while keeping governance, identity, and audit practices consistent across facilities.
Validated policies are packaged for approved edge environments and released through controlled workflows. The deployment agent reports health, version, and rollback state to Kilnara or your private control plane.
FAQ
Training & safety
It is a required pre-deployment check where candidate policies are tested in the twin against success criteria, cycle-time constraints, force limits, collision checks, forbidden zones, and customer-defined acceptance thresholds.
Kilnara is designed for human-controlled production releases. Automation can prepare a candidate policy, but customers can require designated engineer sign-off before any robot-facing deployment.
The policy is blocked from release, the failure reason is recorded, and teams can inspect scenarios that triggered the failure. The system can retrain with additional constraints or roll back to a previous validated policy.
Synthetic scenes let teams test rare, unsafe, or expensive edge cases in simulation before attempting them on hardware. This reduces the need to collect dangerous failure examples on a live line.
No. Kilnara complements existing robot safety systems, guarding, PLC interlocks, procedures, and risk assessments. Physical safety infrastructure remains authoritative.
Yes. Limits can be scoped by robot, tool, fixture, workspace, product family, and customer workflow so validation reflects the actual cell rather than a generic benchmark.
FAQ
Pricing & plans
Pricing usually depends on the number of cells, robots, deployment model, integrations, support level, and whether the engagement is a pilot or enterprise rollout.
Yes. Pilots are scoped around a specific cell, measurable success criteria, data access, integration requirements, and deployment boundaries.
They can, because private deployments require additional infrastructure planning, release operations, support coordination, and sometimes customer-specific security controls.
Compute treatment depends on deployment model. Managed plans may include defined usage bands, while private deployments may use customer cloud or on-prem compute.
Yes. Kilnara is designed to grow from a pilot cell to multiple lines and facilities while preserving policy lineage, access control, and operational reporting.
FAQ
Security & data
You do. Customer line telemetry, twin assets, synthetic datasets, validation reports, and trained policies remain customer assets under the agreed contract.
No customer production data is used for another customer without explicit written approval. Deployments are designed around customer data separation and agreed data-use terms.
Kilnara supports enterprise identity discussions including SSO/SAML, SCIM provisioning, role-based access control, MFA through identity providers, and scoped service accounts.
SOC 2 Type II is in progress, ISO 27001 is on the roadmap, and GDPR support is available through privacy controls and contractual documentation. Current status is shared during procurement.
Air-gapped operation is on the roadmap and can be discussed for restricted manufacturing environments. Requirements, update process, and support model need to be scoped carefully.
FAQ
Support & onboarding
Onboarding starts with a technical discovery workshop, data and integration review, pilot cell selection, twin authoring plan, success metrics, and security requirements.
Typical stakeholders include automation engineering, robotics engineering, manufacturing operations, IT/security, and an executive or plant sponsor who owns business outcomes.
Timing depends on cell complexity, data availability, integration readiness, and security approval. A narrow pilot moves faster than a multi-site production rollout.
Support can include shared channels, scheduled engineering sessions, ticketing, severity-based escalation, and enterprise response commitments defined in the order form.
Yes. We provide enablement for twin review, validation interpretation, approval workflows, rollback procedures, and operational handoff so plant teams can own the loop confidently.
Still have questions?
Talk to a robotics deployment specialist.
If your constraints involve a specific robot fleet, network environment, safety process, or production target, we can walk through it with your team.
Best next step
Share your line type, robot family, integration stack, and target outcome. We’ll route the conversation to sales, support, security, or partnerships.
Contact KilnaraGet answers
See Kilnara on a cell like yours.
Book a demo and review the platform, validation gate, deployment model, and security posture with our team.