End User License Agreement

Last updated 29 July 2026

0. What this document is, and how it differs from the Terms of Service

The Terms of Service govern your subscription — money, renewal, cancellation, support.

This EULA governs the software itself — your right to install it, run it, copy it, and what you may not do with it. KubeManta is self-hosted: we hand you container images and a Helm chart, and you run them on your own infrastructure. That makes a real software license necessary, separate from the subscription.

Both documents apply to you. Where they genuinely conflict, this EULA governs questions about the Software and the Terms of Service govern questions about the subscription.

Capitalised terms not defined here have the meaning given in Terms of Service §2.

1. Parties and acceptance

This is an agreement between you (the "Licensee" — you personally if you are acting for yourself, or the organization you are authorized to bind) and Infrastratus, a sole proprietorship registered in the Republic of the Philippines (full registered address available on request and stated on invoices) ("Licensor", "we", "us").

You accept it by ticking the acceptance checkbox at signup or checkout, or by installing or using the Software — whichever happens first. If you are accepting on behalf of an organization, you confirm you have authority to bind it.

If you do not accept, do not install or use the Software.

2. License grant

Subject to your compliance with this EULA and the Terms of Service, and for as long as your Subscription is active, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to:

Install and run the Software on the number of Clusters covered by your Subscription, for your own internal business operations.
Copy the container images and Helm chart as reasonably necessary to run and operate the Software — including mirroring them into your own private registry. Internal mirroring is expressly permitted and needed for air-gapped and policy-controlled environments.
Make backups as reasonably necessary for disaster recovery.
Use the documentation to support the above.

That is the whole grant. All rights not expressly granted are reserved. No implied license is granted, by estoppel or otherwise.

2.1 Scope is per Cluster

The license is scoped per Kubernetes Cluster, identified by the Cluster Fingerprint described in §3. One Cluster entitlement covers one Cluster. Running the Software on more Clusters than your Subscription covers is outside the license grant.

For what does and does not consume a Cluster entitlement (reinstalls, restarts, cluster rebuilds), see Terms of Service §4.1.

Within a Cluster, the number of user accounts that may hold the admin role at one time is set by your Subscription's paid Admin Seat count (Terms of Service §5.3); viewer accounts are free and unlimited. The seat limit constrains the assignment of new admins only — it never revokes an existing admin, blocks a login, or reduces functionality mid-incident.

2.2 Free tier

The Free tier is licensed on the same terms, limited to the Free feature set and one Cluster, and is provided "as is" with no warranty and no support commitment. We may change or discontinue the Free tier on reasonable notice.

3. License keys, the Cluster Fingerprint, and node-locking

Your license key is issued to you and is confidential. Do not publish or share it — it also authenticates image pulls from our registry, so leaking it leaks your ability to obtain the Software.

The Software binds your license to a Cluster using a Cluster Fingerprint: the metadata.uid of the cluster's kube-system namespace — a random identifier Kubernetes generated when the cluster was created.

We want to be precise about what this is, because "node-locked" can sound more invasive than it is:

It is a random UUID. It reveals nothing about your cluster's contents, size, name, cloud, or workloads.
The things the Software sends to our licensing provider are your license key, this fingerprint, and — unless you switch it off (LICENSE_METER_ENABLED=false) — a small node-count report carried on the keep-alive heartbeat: size counts and timestamps only, never anything describing your workloads, and never used to calculate a charge.
It exists to enforce one-license-per-Cluster and to release the entitlement when a cluster is decommissioned.

Full detail, including what is not transmitted, is in Privacy Policy §3.3.

4. Restrictions

You may not, and may not permit anyone else to:

4.1 Reverse-engineering

Reverse-engineer, decompile, disassemble, or otherwise attempt to derive the source code of the Software or of any compiled or obfuscated component of it.

We state the reason openly: part of the agent ships as compiled native modules rather than readable source (the Python sources are Cython-compiled during the image build, and the build fails if readable source leaks into the shipped image). That compilation is a deliberate protection of our intellectual property, and this restriction protects it contractually as well as technically.

Statutory exception. This restriction does not apply to the extent that such acts are expressly permitted by applicable law notwithstanding a contractual prohibition — for example the limited interoperability and error-correction rights under EU Directive 2009/24/EC and equivalent national law. Where you intend to rely on such a right, we ask (but cannot require) that you contact us first at [email protected]; we would usually rather just give you the information.

4.2 Circumventing licensing

Bypass, disable, tamper with, or circumvent any license validation, feature gating, tier enforcement, Cluster Fingerprinting, or registry authentication — including by patching the Software, spoofing a fingerprint, redirecting our endpoints, or pulling images without a valid license.

4.3 Redistribution

Distribute, publish, resell, rent, lease, lend, host as a service for third parties, or otherwise make the Software available to anyone outside your organization.

To be concrete about the boundary:

Permitted	Not permitted
Mirroring images into your own private registry	Publishing images to a public or shared registry
Running the Software for your own organization's clusters	Running it as a managed service for your customers
Your employees and contractors using it, on your behalf, for your operations	Sharing your license key outside your organization
Sharing configuration and Helm values you authored	Sharing the Software itself

Managed service providers and resellers: this is a real restriction, but it is not a refusal. Contact [email protected] — a separate agreement is available.

4.4 Other restrictions

Remove, obscure or alter any copyright, trademark, or proprietary notice.
Use the Software to build a competing product, or to benchmark it for publication, without our prior written consent.
Use the Software outside the scope of your Subscription tier.
Use the Software in breach of applicable law.

5. Ownership

The Software is licensed, not sold. We and our licensors retain all right, title, and interest in it, including all intellectual property rights, and including any modifications or derivative works.

"KubeManta" and our logos are our trademarks. This EULA grants no trademark rights beyond describing the Software accurately.

Your content is yours. Manifests, Helm values, runbooks, saved bundles, alert rules, and any other configuration you author remain entirely yours. We claim no rights in them, and — because they never leave your cluster — we do not hold them.

6. What happens when your Subscription ends

The Software keeps running. This is a deliberate design decision, and it is a term of this license, not merely a courtesy.

On expiry, non-renewal, cancellation, or lapse of a paid Subscription:

Your license to run the Software continues, perpetually, at the Free tier feature set, for one Cluster.
Paid features stop working. Gated endpoints return an upgrade-required response; gated UI areas show an upgrade note.
Nothing is deleted, disabled, or held hostage. Your audit log, scan history, saved bundles, runbooks and settings stay in your cluster's database.
Your data is unaffected, because it is in your cluster and always was.

The license enforcement is written to degrade gracefully, including tolerating our own license service being unreachable for a grace period before any feature reduction. See LICENSING.md for the full state table.

What does end is your right to run the Software on more than one Cluster, and your right to use paid features. Terminating for a material breach of §4 ends the license entirely, and you must then stop using and delete the Software.

7. Third-party open-source components

The Software bundles third-party open-source components. Each is governed by its own license, not by this EULA. Nothing here restricts any right you have under those licenses.

The inventory is THIRD_PARTY_LICENSES.md, shipped with the Software and regenerable from the dependency manifests. It covers the base images and system tooling, the Python dependencies of the agent, and the JavaScript dependencies of the UI, and calls out every copyleft component (LGPL, MPL) and attribution-required component (CC-BY) explicitly.

No GPL- or AGPL-licensed code is linked into or compiled into any Software binary. The base operating systems contain GPL-licensed system utilities, which we redistribute unmodified as an aggregate; a written offer for their complete corresponding source — valid for three years, at no more than our cost of distribution — is in the inventory, alongside the upstream archives that carry the identical source.

Three clarifications that matter in practice:

Bundled vs. spawned vs. connected. The inventory covers software shipped inside our images. Images your cluster pulls from an upstream registry when you enable a feature (Trivy, Prometheus, netshoot, Litestream) are not redistributed by us. External systems the Software merely connects to — Prometheus, Grafana, trivy-operator, cloud provider APIs — are not bundled; you run and license those yourself.
Grafana specifically. The Software can embed your Grafana's dashboards in an iframe and query your Prometheus over HTTP. It contains no Grafana or Prometheus code, and modifies and serves neither, so Grafana's AGPL obligations are not triggered by your use of the Software. We claim no affiliation with, or endorsement by, Grafana Labs or the Prometheus project.
User-installed software. Anything you install yourself inside the product's browser terminal (for example a vendor CLI installed via npm) is licensed to you directly by that vendor, under that vendor's terms. It is not redistributed by us and is not covered by this EULA. Notably, proprietary CLIs are deliberately not baked into our images for exactly this reason.

8. Support, updates, warranty

Support depends on your tier and, for Enterprise, on the support terms agreed in your contract. Free carries no support commitment.

Updates. We may provide updates, but are not obliged to. You are responsible for applying them; because the Software is self-hosted, we cannot update it for you. Updates are provided under this EULA unless accompanied by different terms.

The Software can check whether a newer version exists. That check transmits nothing about you or your cluster and can be disabled entirely — see Privacy Policy §3.4.

Warranty and liability are addressed in Terms of Service §§11–12 and apply to this EULA in the same way and to the same extent. In summary: the Free tier is "as is"; paid tiers carry a limited conformity-to-documentation warranty; AI output and security scanning are assistive and are not guarantees.

9. Term and termination

This EULA starts when you first install or use the Software and continues until terminated.

You may terminate at any time by ceasing use and deleting the Software.

We may terminate this EULA if you materially breach it — in particular §4 (restrictions) — and, where the breach is curable, fail to cure it within 30 days of notice.

On termination for breach: all license rights end immediately, including the perpetual Free-tier right in §6. You must stop using the Software, delete all copies including mirrored images, and confirm on request.

Surviving: §§4 (restrictions, to the extent they protect our IP), 5 (ownership), 7 (third-party components), 9, and 10.

10. General

Governing law. the Republic of the Philippines, per Terms of Service §15.

Export compliance. You must comply with applicable export-control and sanctions laws, and may not use or export the Software in breach of them.

Government end users. If you are a government entity, the Software is "commercial computer software" provided with only the rights granted here.

Entire agreement. This EULA, with the Terms of Service and the documents they incorporate, is the entire agreement on this subject and supersedes any prior understanding about the Software.

Severability and waiver. If a provision is unenforceable, the rest stands. Failing to enforce a right is not a waiver.

Changes. We may update this EULA per Terms of Service §14. The document version above changes each time, and material changes apply from your next renewal — never during a period you have already paid for. A change to this EULA never retroactively removes the perpetual Free-tier right in §6 for a Cluster already installed.

11. Contact

Purpose	Contact
Licensing questions, MSP/reseller arrangements, interoperability requests	[email protected]
Security vulnerabilities	[email protected]

Infrastratus · a sole proprietorship registered in the Republic of the Philippines (full registered address available on request and stated on invoices) ·