Skip to content
OnicostOnicostOnicost
ProductScheduler BetaPricing
fren
Sign inTry Onicost

Terms of use

Last updated: 17 October 2026

This translation is provided for information: in case of discrepancy, the French version prevails.

Purpose and acceptance

These terms of use (the “Terms”) govern access to the Onicost service (the “Service”) and its use by any account holder (the “User”) and the organization on whose behalf they act (the “Customer”). Onicost is based in Paris.

The Service helps the Customer understand Kubernetes and cloud costs, allocate spending by cluster, namespace, workload and available labels, and review sizing recommendations. It provides reports and CSV/PDF exports according to the plan. The Cloud space imports billing data from the Customer’s connected AWS, Azure, Google Cloud and Scaleway accounts.

Scheduler Beta also lets the Customer simulate and explicitly activate recurring rules to stop and resume supported resources, with a chosen time zone, exceptions and temporary wake-ups. A sizing recommendation does not itself change infrastructure.

The Service is intended for professionals. The User declares that they act for their professional activity and have authority to bind the Customer. The current Terms are published on this page. Stripe’s subscription checkout requires acceptance of the terms; this acceptance relates to that checkout and does not describe acceptance in every other access path.

Account and sign-in

Access to the Service requires an account, created with the identity provider of the Service. This provider, operated by Onicost and hosted at Scaleway, authenticates the User and passes their identifier, e-mail address and name to the Service. The password is typed only on the pages of the identity provider, which keeps a hash of it only: the application never receives it.

The User provides accurate information, keeps their credentials confidential and reports any unauthorized access without delay to contact@onicost.com. The User is responsible for the actions taken from their account.

Organizations and roles

The Customer’s data belongs to an organization. The User who creates an organization becomes its owner. Other members are invited by e-mail and receive one of these roles:

  • owner: management of the organization, members, subscription and Scheduler rules, and deletion of the organization;
  • admin: management of clusters, agent tokens, settings, recommendation status, Scheduler rules, invitations and members other than owners;
  • billing: viewing data and managing subscriptions, billing and payments;
  • viewer: viewing costs, recommendations and reports, and exports according to the plan.

Members, including viewers, may request a temporary wake-up of resources within the limits provided by Scheduler. Owners and administrators manage the rules.

The Customer chooses its members and their roles, and removes access for anyone who should no longer see its data or act on its resources.

Agent and responsibilities of the Customer

To measure a cluster, the Customer installs the Onicost agent using the Helm command provided by the Service, with a token specific to that cluster. The Service keeps only a hash of the token.

Collection reads CPU and memory usage and the Kubernetes inventory with read permissions. The agent reads neither Secrets nor ConfigMaps. Scheduler action permissions are a separate option from collection: they allow actions on Deployments, StatefulSets and CronJobs targeted by the rule’s namespaces and labels.

The Customer reviews the simulation before activating a rule. Following explicit activation, Scheduler may execute the planned stops, resumes and wake-ups. The Customer selects resources, schedules, time zones and exceptions, and checks that they meet its teams’ needs.

In the Cloud space, billing read access is separate from the write identity used for Scheduler actions. The Customer grants and may remove these permissions. Credentials kept by the Service are encrypted at rest. Supporting a provider does not mean that all its services can be controlled.

  • The Customer holds the rights needed to connect its sources and grant collection or action permissions;
  • it checks targeted resources, collection exclusions and dependencies before activating a rule;
  • it keeps tokens confidential and renews or revokes them in case of doubt;
  • it disables rules and removes permissions or the agent when it no longer wants to use the corresponding functions.

Nature of the results

The costs shown are estimates. Each container is priced per hour at the price of its node, from the public prices of AWS, Azure, Google Cloud, OVHcloud and Scaleway refreshed every day, AWS spot nodes at the public spot price. A node whose instance type is missing from these prices is estimated from the vCPU and GiB prices of the region when the provider publishes the data needed for it; a node whose provider is not detected takes a price per vCPU and per GiB set by the Customer. The costs may differ from the bills of the providers (negotiated discounts, credits, commitments, taxes).

Sizing recommendations, potential savings and month-end projections are estimates, without guaranteed results. Comparing observed costs before and after an action does not prove that Onicost alone caused the difference.

Stopping pods does not necessarily reduce the number of billed nodes; capacity may need to be adjusted. Disks, storage and other charges can continue during a stop. The Customer checks the results and its provider invoices.

Plans, prices and payment

Plans and prices appear in the Pricing section of the home page. On the date of these Terms:

  • Free: no charge, up to 1 cluster, 32 billable cores and 2 members, with 31 days of viewable history, Kubernetes allocation and recommendations;
  • Team EUR: €99 excl. VAT per month, with the first 64 billable cores included; €3.20 excl. VAT per additional core per month from the 65th to the 500th core, then €2.60 from the 501st;
  • Team USD: $109 per month before taxes, with the first 64 billable cores included; $3.52 per additional core per month from the 65th to the 500th core, then $2.86 from the 501st;
  • Team includes clusters and members without a standard limit, the Cloud space, CSV/PDF exports, 13 months of viewable history and Scheduler Beta. Scheduler is limited to 100 rules per organization, including rules in simulation and paused rules;
  • Business and Enterprise: on quote, through the site’s contact address.

The tiers are graduated: at 128 billable cores, the monthly total is €303.80 excl. VAT or $334.28 before taxes. The 5,000-core sales contact threshold is not a technical limit of the Team plan.

Billable cores are the rounded average CPU capacity of observed nodes across all clusters, rather than CPU actually consumed. For serverless, the calculation follows the billed pods’ vCPU-hours. The Team base fee also applies to cloud-only organizations; no percentage of cloud spending is added.

The Team subscription is billed monthly in arrears, using the average measured over the past month. Prices are before taxes; applicable taxes are added.

Payment goes through Stripe Checkout, operated by Stripe Payments Europe, Limited. Card data is entered on Stripe’s pages: Onicost neither receives nor stores it. Invoices and payment methods are managed in Stripe’s customer portal, opened from the Service.

For a quote, write to contact@onicost.com.

Onicost may change its prices. A price change to an existing subscription is announced at least 30 days before it applies; the Customer may cancel before that date.

Trial

Each organization gets a free trial of the Team plan for 14 days, without a card. The trial starts at the first reading of an agent, and at the latest 30 days after the creation of the organization. During the trial, the organization may count up to 50 clusters, 5,000 billable cores, 10 members and 5 cloud accounts.

At the end of the trial, without a subscription, the organization moves to the Free plan and its limits apply.

Limits and suspension

Billable cores are compared with the limits of the Free plan as a 7-day average, with a 10% tolerance. Beyond a limit, the Service warns the Customer. If the overrun lasts, the cost screens are locked after 7 days, then the agent tokens are suspended after 21 days: readings are refused until the organization is back under the limits or moves to the Team plan.

When a payment fails, exports, reports and the Cloud space are turned off after 7 days, then the organization becomes read-only after 14 days, until the payment is made.

Onicost may suspend the access of a User or a Customer without notice in case of a threat to the security of the Service, fraudulent use or serious breach of the Terms, and informs them.

Availability

Onicost uses reasonable means to keep the Service accessible, without a service level commitment. The Service may be interrupted for maintenance, an update or an incident. While reception is interrupted, the agent keeps its readings in memory for up to 2 hours.

Scheduler is offered in Beta, without a specific discount or SLA. The Customer considers how stopping resources affects its environments’ availability and dependencies. A resume or wake-up may depend on the provider, available capacity and resource state; instant restarts and continuous availability are not guaranteed.

Intellectual property

The Service, the agent, their interfaces, their texts and the Onicost trademark belong to Onicost, subject to the licenses of the open source components they include. Onicost grants the Customer, for the duration of its use, a personal, non-exclusive and non-transferable right to use the Service for its internal needs.

The Customer’s data remains its property. The Customer authorizes Onicost to process it only as far as needed to provide the Service.

Data

Onicost processes the Customer’s data to provide the Service, under the conditions described in the privacy policy. The data of each organization is isolated from that of the others. Onicost sells no data and uses none for advertising.

Liability

Onicost has an obligation of means. It is liable neither for the decisions the Customer takes on the basis of the estimates and recommendations of the Service, nor for indirect damage, such as a loss of revenue, of data or of expected savings.

For any direct damage, the liability of Onicost is limited to the amount paid by the Customer for the Service during the 12 months before the event that gives rise to it. These limits apply neither in case of gross negligence or wilful misconduct, nor to damage that the law forbids to limit.

Termination and deletion

The Customer may cancel the Team subscription at any time in Stripe’s customer portal. Cancellation takes effect at the end of the current period, whose usage remains due, and the organization returns to the Free plan.

The owner may delete their organization from the Service. Deleting an organization or cluster starts an asynchronous purge of the relevant data. This process has a 15-day retry window; that is not a guarantee that every copy will be deleted within that period. Backups and data subject to retention obligations follow their own rules, described in the privacy policy.

A User may request account deletion at contact@onicost.com. Onicost may terminate a Customer’s access for a serious breach of the Terms left uncorrected 30 days after formal notice, or immediately in case of fraud or a threat to the security of the Service.

Changes to the Terms

Onicost may change the Terms. The version in force is published on this page with the date of its last update. A substantial change is announced in the Service at least 30 days before it comes into force; using the Service after that date means accepting it.

Governing law and disputes

The Terms are governed by French law. In case of dispute, the parties first seek an amicable solution, to be requested at contact@onicost.com. Failing an agreement within 30 days, any dispute falls within the jurisdiction of the competent courts of the place of Onicost’s registered office.

OnicostOnicost

Cloud costs, from visibility to scheduled actions.

Kubernetes cost optimizationKubernetes requests and limitsCloud cost optimizationKubernetes and cloud scheduling
ContactBased in Paris

© 2026 Onicost

Legal noticeTerms of usePrivacy policy

Cookies and browser storage

The site does not include advertising trackers or audience analytics. We use technical browser storage, not tracking cookies.

Browser storage for your preferences

language and layout_version remember the language and theme you choose. onicost.cookie-notice-version remembers that you dismissed this notice. These values stay in your browser until cleared or replaced.

When you sign in

Local storage keeps your active organization. Session storage handles authentication, your return page and account actions. Keycloak handles sign-in; Stripe handles payment on its own service when you request it.

You can clear this data in your browser settings. Doing so may reset your preferences or end your sign-in session.

Read the full details in our privacy policy