Skip to main content
Version: 1.45

Billing

Okteto bills per seat on an annual contract. We do not charge per environment or per agent: a developer with one seat can run as many development environments and agents as your infrastructure supports.

Summary​

  • Pricing is per seat, billed annually.
  • No charge per agent or per environment. Run as many development environments and agents per developer as your infrastructure supports.
  • Enterprise license covers your entire fleet. A single license entitles you to deploy as many Okteto clusters as you need; we only charge for unique seats across all of them.
  • No hard cap. New user accounts can keep being created without service interruption. Overages are settled with a true-up.
  • Self-service visibility. See your user seat count in the Admin Dashboard or via the Okteto API at any time.

Seats​

A seat is one user account in your Okteto instance, identified by an email address. When a user logs in for the first time, an account is automatically created.

Okteto does not count:

  • The number of development environments a developer creates.
  • The number of agents (Okteto, AI, or otherwise) that operate on behalf of that developer.
  • Service accounts and bots that the platform itself uses.

If you bought 50 seats, you can have 50 accounts in your system. Each one can run as many environments and agents as your cluster supports.

note

Your contract refers to "Users" and "User Allowance". This page uses "seat"; the terms are equivalent.

Enterprise: Multi-Cluster Licensing​

For Enterprise customers, your Okteto license covers your entire fleet. You can deploy Okteto on as many clusters as you need (production, staging, regional, per-team) at no extra cost.

Billing counts unique seats across the fleet. A user with the same email in two clusters counts once. This means you can split workloads, isolate environments, or run regional clusters without paying twice for the same developer.

Managing Your Seat Count​

  • Delete user accounts you no longer need. Once a user account is deleted, it disappears from the count immediately. Accounts cannot be reassigned to new users; when a different person logs in with their email, a new account is created automatically.
  • Use Okta to deprovision automatically. If your team uses Okta, configure Okta User Deprovisioning to delete accounts automatically when users are removed from your identity provider.
  • Use the Okteto API. The Okteto API supports listing and deleting users by ID, so you can wire account cleanup into your own offboarding scripts or integrations.

For permanent team growth, contact your Okteto account team to purchase additional seats in advance. Add-on seats are typically cheaper than waiting for a true-up.

Seat Usage​

Your current account count is visible in the Admin Dashboard and via the Okteto API.

Okteto checks user account counts monthly. If your count exceeds your allowance, your Okteto account team will reach out.

Seat Overages​

Okteto does not block new account creation when you exceed your seat allowance.

When the count of user accounts exceeds your purchased seat allowance:

  1. Okteto notifies you before invoicing. Unless you have explicitly requested otherwise, Okteto reaches out before invoicing any true-up. Add-on seats purchased proactively are typically cheaper than waiting for the true-up.
  2. True-up at your contracted rate. The additional user seats are billed at the per-seat price on your Order Form, pro-rated over the remaining months of your current annual term, and invoiced immediately.
  3. Renewal updated. At the start of your next annual period, your subscription is updated to reflect the new seat count.

Frequently Asked Questions​

Do I get charged when a developer runs an extra environment?​

No. Okteto charges for seats, not environments. A developer with one seat can run as many environments as your cluster supports.

What about AI agents or build agents that use Okteto on a developer's behalf?​

Not counted. A seat is a human, identified by email.

Can I reassign a seat from a former employee to their replacement?​

Accounts are not reassigned. Delete the former employee's account; when their replacement logs in with their own email, a new account is automatically created.

Our team grew permanently. We have 10 extra accounts in the system. What happens?​

This is a true-up scenario. The 10 additional seats are billed at your contracted rate, pro-rated over the remaining months of your annual term, and your renewal reflects the new seat count.

A developer left. Do I deactivate the account or delete it?​

Delete it. Deactivation does not remove the account from the count.

Is there a hard cap?​

No. Okteto does not block additional accounts from being created. The platform stays fully usable, and the true-up settles the difference at invoicing.

If we run multiple Okteto clusters, do we pay for each cluster?​

No. For Enterprise, a single license covers your entire fleet. We count unique seats across all your clusters: a developer with the same email in two clusters counts once.

Next Steps​

View your current seat count in the Admin Dashboard or query it via the Okteto API. To remove accounts automatically when users leave your identity provider, configure Okta User Deprovisioning. For Self-Hosted license installation, see Okteto License.