Questions, answered.

Kllyroo is an on-premise AI observability platform that monitors servers, containers, Kubernetes, network devices, databases, cloud accounts, virtual machines, websites and applications from one portal. It installs on your own server, runs fully offline, and includes alerting, on-call, runbooks, secure remote access and a built-in offline AI model.

No. Kllyroo is self-hosted only. You install one signed package on your own Linux server (or a cloud VM you control), and all monitoring data stays inside your network. There is no Kllyroo cloud that receives your telemetry.

Yes. Installation, updates, licensing and the built-in AI all work without internet access. Optional features such as cloud-account monitoring, Slack/Teams, WhatsApp or voice alerts need outbound access only if you choose to use them.

Kllyroo is built by Kirshi Technologies & Consulting Pvt. Ltd., an ISO 27001 and ISO 9001 certified product engineering company based in Chennai, India, with 14 years in business and 400+ projects delivered across 12 countries.

One Kllyroo server with 4 vCPU, 8 GB RAM and 150 GB SSD is sized for up to 250 monitored servers. For larger estates, Kllyroo reviews your plan and can split monitoring across multiple installations or use remote probes for distant sites.

Yes. The multi-tenant MSP mode gives each customer its own tenant with white-label branding, per-tenant licence limits and usage metering, all managed from one MSP console.

No. Kllyroo installs, updates and runs offline. Only optional features such as Let’s Encrypt certificates, cloud monitoring, cloud AI providers, WhatsApp and voice alerts, Slack or Teams need internet.

No. The licence is checked on your server, agents only talk to your own portal, and the built-in AI runs on your server too.

You get reminders from 30 days before. After expiry there is a grace period (normally 14 days). After that the portal locks, but monitoring, alerts and notifications keep running and no data is lost. Upload a renewed licence to unlock immediately.

Yes. Kllyroo runs on any Linux server you control — in your data centre or on a VM in AWS, Azure, GCP or DigitalOcean. It is still self-hosted: you own the server and the data.

Yes. Ask for the arm64 package.

Kllyroo has 21 licensable modules: servers, network, databases, logs, cloud, virtualization, CMDB, websites, synthetics, checks, RUM, mobile, APM, LLM, business journeys, alerting, automation, Kllyroo Access, AI logs, AI assistant and AI root-cause analysis. Dashboards, reports, status pages, maintenance windows, dependency maps, change tracking, users/roles/audit and high availability are always included.

Yes. APM ingests OpenTelemetry traces, and the metrics store accepts Prometheus remote_write and scrape jobs and supports PromQL queries.

Kllyroo is sold as an annual on-premise licence. Pricing is based on node tiers (a node is any monitored server, network device or other counted asset) and the modules you choose. Licences renew yearly and include updates and support.

We offer guided proof-of-concept deployments on your own infrastructure. Contact us to plan one.

You cannot add more of that item, but nothing existing is removed and monitoring continues. Upload an expanded licence to add capacity.

The MSP add-on creates separate tenants on one Kllyroo installation. Each tenant gets its own assets, users and alerts, optional white-label branding, and carve-outs of every counted licence limit. The MSP console shows all tenants and meters usage.

Yes. Route access is deny-by-default and every release runs an isolation suite that calls every API route as one tenant with another tenant’s IDs. The latest run: 415 routes, 9,622 cross-tenant probes, 0 leaks.

Chrome and Edge 87 or newer, Firefox 78 or newer, and Safari 14 or newer.

Yes. Kllyroo then uses HTTPS with its own self-signed certificate. You can move to a domain later with kllyroo set-domain.

Run sudo kllyroo update kllyroo-<version>.tar, then update agents from the portal. The update backs up first and rolls back automatically if anything fails.

Run sudo kllyroo backup and copy the backup folder to another machine regularly.