> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/settings/subscription.md).
# Subscription
View, compare, and upgrade your Kilo IoT plan, and see the device, dashboard, and rule limits each tier includes.
The Subscription page lets you view your current plan, compare available tiers, and manage billing. It is the central place to understand what your plan includes and to upgrade when your deployment outgrows its current limits.
## Accessing Subscription
Navigate to **Settings > Subscription** in the sidebar.
## Plan Tiers
Kilo IoT Server offers a free tier alongside paid tiers that scale up to a custom **Enterprise** plan. Each step up raises the ceilings your deployment runs against — devices, custom dashboards, rules, and how far back device logs are retained — and unlocks more of the notification and support features. Pricing is per month.
| Tier | Price | Devices | Custom dashboards | Rules | Device-log retention |
| -------------- | ---------- | ---------- | ----------------- | --------- | -------------------- |
| **Free** | €0 | Up to 5 | 1 | 1 | 1 day |
| **Starter** | €25 | Up to 25 | Up to 5 | Up to 50 | 1 week |
| **Pro** | €145 | Up to 100 | Up to 50 | Up to 150 | 1 month |
| **Business** | €379 | Up to 500 | Up to 100 | Up to 300 | 12 months |
| **Max** | €659 | Up to 1000 | Unlimited | Up to 600 | 12 months |
| **Enterprise** | Individual | Custom | Custom | Custom | Custom |
Beyond these ceilings, the plan comparison on the Subscription page also shows which tiers include unlimited gateways, the Notification Center, email and push notifications, and email support. The free tier lets you explore the platform with no payment details required; the **Enterprise** tier carries everything from the other plans with the option to raise specific limits to fit your operation, on individual pricing and terms.
## Data retention
Data retention is the period of device history available under your subscription. The plan table above lists the standard device-log retention for each tier; Business and Max include 12 months. A digital twin keeps its identity when you replace its physical sensor, but that replacement does not extend the retention period of its earlier readings.
If your organization needs longer data retention for compliance or operational requirements, contact the Kilo team to discuss an extended retention period and agree suitable terms. On **Settings > Subscription**, choose **Talk to sales** on the Enterprise tier. Include the period you need and the devices and measurements it should cover, so the arrangement can be agreed before you rely on it for record keeping.
For example, a pharmaceutical refrigeration operator can keep the same refrigerator twin through probe replacements and discuss a longer period for its temperature records. The required period depends on the organization's obligations; a sensor replacement alone does not establish compliance or recover expired readings.
## Upgrading Your Plan
To move onto a paid plan, choose the tier you want on the plan comparison and click **Upgrade Plan**. If the organization does not have a paid subscription yet, **Choose payment method** opens:
* **Pay by card** continues to Stripe checkout. The plan activates after the card payment clears.
* **Pay by invoice (bank transfer)** creates the subscription after you confirm it. This option requires complete company billing details; the invoice and bank-transfer information are sent to the billing email.
Once a paid subscription exists, its payment method stays with it. A card-paid subscription continues through Stripe when you select another plan. An invoice-paid subscription opens an in-platform confirmation and applies the plan change to the existing subscription. See [Billing and Invoices](/settings/billing-and-invoices.md) for billing details, invoice payment terms, and plan changes.
For the **Enterprise** tier, click **Talk to sales** to reach the Kilo IoT team for custom pricing and terms.
## Plan limits
Each plan caps how much of the platform you can use — devices, custom dashboards, rules, and history retention. Limits apply from the moment a plan is active, and the platform enforces them as you work rather than at billing time.
**Dashboards are a common limit to hit.** When you reach the number of custom dashboards your plan allows and try to add another, Kilo tells you the **Dashboard limit reached** and explains that your plan allows up to your tier's count. From there you can **Upgrade Plan** to raise the limit, or remove an existing dashboard to free a slot. The same applies to other capped resources — the comparison matrix shows the ceiling for each one, so you can size the right tier before you hit it.
## Managing an Existing Subscription
Current subscribers paying **by card** see a **Manage my subscription** button. This opens the Stripe customer portal, where you can:
* Update your payment method
* View invoices and payment history
* Cancel or modify your subscription
Organizations billed **by invoice** manage things differently: their invoices live on an **Invoices** page inside Kilo rather than in the Stripe portal, and plan changes are applied in place instead of going through checkout. See [Billing and Invoices](/settings/billing-and-invoices.md).
## SMS Credits
If your plan supports SMS notifications, the Subscription page includes an SMS add-on section showing your current credit balance and the per-message cost. To purchase additional credits:
1. Enter the desired quantity in the top-up form.
2. The minimum purchase is 0.50 EUR.
3. Confirm the purchase — credits are added to your balance and remain valid for one year.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kiloiot.io/settings/subscription.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
