The terms of using Kuberly.

Kuberly is an AI DevOps autopilot. We provision and operate infrastructure inside your cloud account (AWS today; GCP and Azure in beta) and ship every line of infrastructure code into your Git provider. We don't host your application data, secrets, or state outside your own cloud.

The service includes: provisioning, monitoring, security scanning, GitOps automation, the AI assistant in the dashboard and IDE, customer-owned IaC in your Git repo, and on-call human supervision from a Kuberly engineer.

You give Kuberly a scoped, cross-account IAM role (or equivalent on GCP/Azure) so the autopilot can provision and operate the platform in your cloud. The role is least-privilege and documented in your IaC repo. You can revoke it at any time from your cloud console — that revokes our access immediately and irreversibly. The cluster keeps running; we no longer touch it.

You are responsible for:

• Maintaining the cloud account, including paying your cloud provider directly.
• Maintaining your Git provider account and the IaC repo we populate.
• Keeping the credentials of users you grant access to the Kuberly dashboard secure (we recommend SSO + MFA).
• The application code you push into the platform, including its security and compliance posture above the platform layer.

The platform fee scales with the size of the infrastructure under management. Tiers are published at kuberly.io/#pricing. Cloud usage is billed by your cloud provider, not by us. Billing cadence (monthly or annual) is selected at signup; annual prepay saves 2 months on any tier.

Tier upgrades take effect prorated at the start of the next billing period when sustained spend crosses a tier threshold. Downgrades apply on the next billing period.

Monthly subscriptions cancel at the end of the then-current month. Annual subscriptions cancel at the end of the term — the 3-month money-back guarantee applies to first-time annual customers if you cancel within 90 days of your first paid invoice.

The eject path is real. On cancellation, the OpenTofu + Terragrunt repo, your cloud account, and all data inside both stay with you. We don't run a migration project, hold state hostage, or force you onto another tool. Revoke our IAM role; your infra keeps running.

Operational commitments (availability targets, on-call response, incident communication) are described in the Service Level Agreement attached to your MSA. Tier 05 (Enterprise) customers receive a custom SLA on request.

Don't use Kuberly to violate the law, infringe IP, distribute malware, run unsolicited commercial messaging, attack other systems, or attempt to break out of the platform's security boundaries. Don't probe Kuberly's own systems for vulnerabilities without written permission — disclose findings to [email protected].

Yours stays yours. Your application code, configuration, content, and the IaC we ship into your repo are owned by you, subject to upstream open-source licenses for components like OpenTofu, Terragrunt, Kubernetes, Istio, and friends.

Ours stays ours. The Kuberly dashboard, the autopilot's runtime services, the AI models we operate, and our internal modules are owned by Kuberly. You receive a non-exclusive license to use them for the duration of your subscription.

Each side keeps the other's non-public information confidential and uses it only to operate the service. This survives termination. Detail in the MSA.

We provide the service with reasonable skill and care. We do not warrant that the service will be uninterrupted, error-free, or fit for a particular purpose. Open-source components carry their own license terms and warranties.

The service is provided "as is" and "as available." To the maximum extent permitted by law, we disclaim all implied warranties.

Neither side is liable for indirect, special, incidental, consequential, or punitive damages, including lost profits or lost data — even if advised of the possibility. Each side's aggregate liability is capped at the fees you paid Kuberly in the 12 months preceding the claim.

Some jurisdictions don't allow these limits — they apply only to the extent legally permitted.

You'll indemnify Kuberly against claims arising from your application code, your content, your use of the service in violation of these Terms, or your violation of third-party rights. Kuberly will indemnify you against claims that the platform itself infringes a third party's IP, subject to the limits in the MSA.

We update this page when our practices change. Material changes (those affecting your rights or fees) are communicated by email with at least 30 days' notice. Continued use after the effective date is acceptance.

Governed by the laws specified in your MSA. Until you sign one, the governing law is set out in the order form you accept at checkout.

Questions about these Terms or anything else legal: [email protected].

← Back to homePrivacy notice →