Kubevox Terms Addendum

Effective: March 9, 2026

1. Scope

This Kubevox Service Addendum ("Addendum") supplements the Nimvox Terms of Service ("Terms"). It governs your use of Kubevox, Nimvox's Kubernetes portfolio orchestration platform.

In the event of a conflict between this Addendum and the main Terms, this Addendum governs for Kubevox-specific matters. All other provisions of the main Terms remain in full force and effect.

2. Definitions

In addition to the definitions in the main Terms, the following terms apply to Kubevox:

• "Cluster" means a Kubernetes cluster registered with Kubevox via kubeconfig credentials you provide.
• "Kubeconfig" means the Kubernetes configuration file containing API server endpoints and authentication credentials used to connect to your Cluster.
• "Workload" means a Kubernetes resource managed by Kubevox, including Deployments, StatefulSets, DaemonSets, CronJobs, Jobs, and Horizontal Pod Autoscalers (HPAs).
• "Policy" means the scaling rules and guardrails you configure within Kubevox, including minimum and maximum replica counts, cooldown periods, criticality tiers, and cost weights.
• "Scaling Action" means any modification to a Workload's replica count or resource configuration executed by Kubevox on your Cluster.
• "Dry-Run Mode" means the Kubevox operating mode in which recommendations are generated and displayed but no Scaling Actions are executed on your Clusters.
• "Live Mode" means the Kubevox operating mode in which Scaling Actions are automatically executed on your Clusters based on your Policies.
• "Emergency Freeze" means the Kubevox feature that immediately halts all automated Scaling Actions across all Clusters and Workloads.
• "Portfolio" means the collection of all Clusters and Workloads registered under your Kubevox account.
• "Organization" means the multi-user entity available on higher-tier plans that allows team members to share access to a Portfolio.

3. Service Description

Kubevox is a Kubernetes portfolio orchestration platform that provides:

• Cluster registration and workload discovery across multiple Kubernetes clusters
• Automated workload analysis with explainable recommendations
• Policy-bounded scaling with configurable guardrails
• Dry-run portfolio preflight showing proposed changes and cost impact estimates
• Live orchestration with continuous planner cycles
• Full action audit logging with reasons for each Scaling Action
• Cost analysis and FinOps reporting
• Alerting and incident management features

Supported Workload types include Deployments, StatefulSets, DaemonSets, CronJobs, Jobs, and HPAs. Support for additional workload types may be added over time.

4. Cluster Access & RBAC

To use Kubevox, you must provide kubeconfig credentials that grant Kubevox access to your Kubernetes clusters. By providing these credentials, you represent and warrant that:

• You have the authority to grant Kubevox access to the Cluster
• The credentials have been scoped with appropriate RBAC permissions
• You have reviewed and approved the level of access being granted

4.1 Required Permissions

Kubevox requires the following Kubernetes API permissions to function:

• list and get on Deployments, StatefulSets, DaemonSets, CronJobs, Jobs, HPAs, Pods, and Namespaces — for workload discovery and monitoring
• patch on Deployments and StatefulSets — for executing Scaling Actions in Live Mode

4.2 Your Responsibility

You are solely responsible for the RBAC permissions granted to Kubevox. Nimvox strongly recommends creating a dedicated, namespace-scoped service account for Kubevox rather than providing cluster-admin credentials. Nimvox is not liable for any consequences arising from overly broad permissions you grant.

Nimvox accesses your Clusters solely to provide the Kubevox service. We do not access your application data, Kubernetes Secrets, ConfigMaps, or any resources beyond the workload metadata necessary to deliver the service.

5. Infrastructure Control Risks & Disclaimers

You acknowledge and agree that automated orchestration of production Kubernetes infrastructure carries inherent risk. By enabling Live Mode, you accept the following:

5.1 Policy Configuration

You are solely responsible for configuring Policies correctly, including minimum and maximum replica counts, scaling bounds, cooldown periods, and criticality tiers. Misconfigured Policies may result in under-provisioned or over-provisioned workloads. Nimvox does not validate whether your Policies are appropriate for your application requirements.

5.2 Cascading Effects

Scaling Actions on one Workload may affect other workloads that share the same node pool, namespace, or cluster resources. For example, scaling up one Deployment may cause resource pressure on co-located Deployments. Kubevox considers Portfolio-level constraints, but cannot predict all infrastructure-level interactions.

5.3 Dry-Run vs. Live Mode

In Dry-Run Mode, Kubevox generates and displays recommendations without executing any changes to your Clusters. In Live Mode, Kubevox automatically executes Scaling Actions based on your Policies. You must explicitly enable Live Mode — it is never activated by default. Nimvox recommends reviewing recommendations in Dry-Run Mode before enabling Live Mode.

5.4 Limitation of Liability for Scaling Actions

To the maximum extent permitted by applicable law, Nimvox disclaims liability for any consequences of automated Scaling Actions, including but not limited to:

• Service degradation or outages in your applications
• Data loss resulting from workload scaling
• Increased cloud infrastructure costs
• Cascading failures across workloads or clusters
• SLA violations in your agreements with your own customers

Nimvox's total liability remains subject to the limitations set forth in Section 10 of the main Terms of Service. Kubevox is provided "as-is" without any uptime or availability guarantees, as described in Section 12 of the main Terms.

6. Telemetry & Prometheus

Kubevox optionally integrates with Prometheus to collect real-time workload metrics. This integration is not required.

• With Prometheus: Recommendations are based on actual CPU/memory utilization, request rates, and historical patterns.
• Without Prometheus: Recommendations are based solely on Kubernetes resource requests and limits declared in your workload specifications. Accuracy may be reduced.

Cost savings estimates displayed in Kubevox are projections based on replica count changes and your declared cost-per-pod values. They are not guarantees of actual cloud cost reductions. Actual costs depend on your cloud provider's pricing, reserved instance commitments, spot pricing, and other factors outside Nimvox's control.

7. Emergency Freeze

You may activate an Emergency Freeze at any time to immediately halt all automated Scaling Actions across your entire Portfolio. During a freeze:

• No Scaling Actions are executed on any Cluster
• Recommendations continue to be generated but are not acted upon
• Your workloads remain in their current state

Nimvox is not liable for any consequences arising from the freeze itself, including workloads remaining in a suboptimal state during the freeze period. Nimvox is also not liable for any state drift that accumulates during a freeze or for consequences of resuming automated orchestration after a freeze is lifted.

8. Data Handling & Security

Kubevox processes the following categories of data:

• Cluster credentials (kubeconfig): Encrypted at rest using AES symmetric encryption. Classified as critical-sensitivity data. Used solely to authenticate API calls to your Clusters.
• Workload metadata: Deployment names, namespace names, replica counts, resource requests/limits, HPA configurations. Stored in plaintext.
• Scaling action audit log: Records of all Scaling Actions executed, including timestamps, before/after states, and reasons. Stored in plaintext.
• Organization data: Organization names, team membership, and role assignments. Stored in plaintext.

Nimvox does not access, read, or store your application data, Kubernetes Secrets, ConfigMaps, environment variables, or container images. For full details on how we handle your data, see our Privacy Policy.

9. Multi-Tenancy & Organizations

Organization features, including team access and role-based access control within Kubevox, are available on higher-tier plans. If you create an Organization:

• You, as the Organization administrator, are responsible for managing member access and permissions
• You are responsible for ensuring all Organization members comply with these Terms and this Addendum
• Nimvox is not liable for Scaling Actions or Policy changes made by any member of your Organization

10. Service Tiers & Billing

Kubevox is offered in multiple tiers (Free, Pro, Team, and Enterprise), each with different limits on the number of Clusters, Workloads, and features available. Current pricing, limits, and feature availability are listed at nimvox.dev.

• No service-level agreement (SLA) or uptime guarantee is provided on any tier
• Subscriptions are billed monthly via Stripe
• No refunds are provided for partial months
• Pricing may change with 30 days' notice as described in Section 15 of the main Terms

11. Termination & Data Retention

Upon cancellation or termination of your Kubevox account, all associated data — including kubeconfig credentials, workload metadata, scaling policies, and action audit logs — is retained for 30 days and then permanently deleted.

You may request earlier deletion of your data at any time by contacting us at contact@nimvox.dev.

For questions about this Addendum, contact us at contact@nimvox.dev.