> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/supersim/super-sim-advisories/kore-super-sim-pooled-plans-december-2025.md).

# KORE Super SIM Pooled Plans - December 2025

## Simplify Your IoT Data Management with KORE Super SIM Pooled Plans

Managing data for a large IoT fleet can be complex. KORE offers flexible solutions to fit your specific needs, whether you have predictable data usage or require more adaptable options.

For deployments with many devices, our **Super SIM Pooled Plans** offer a smart way to increase efficiency. By allowing your entire fleet to share a single bucket of data, you minimize waste and reduce costs. This model provides operational flexibility, as high-usage devices are automatically balanced by low-usage ones, all under a single, easy-to-manage plan.

To ensure you are always in control, our platform includes smart monitoring tools. You can set custom usage thresholds to receive automatic alerts, helping you manage costs effectively.

Whether you prefer the budget predictability of a pooled plan or the unmatched flexibility of a[ **Pay-As-You-Go**](https://docs.korewireless.com/en-us/supersim#pricing-and-billing) model, KORE has a solution tailored for you. 

Here is a simple comparison to help you choose the right fit:

| Feature                       | Pay-As-You-Go Plan                                                                                    | Pooled Plan                                                                    |
| ----------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **Best For**                  | New deployments, unpredictable usage, or low data needs.                                              | Fleets of devices with variable but predictable total usage.                   |
| **Data Model**                | Each SIM is billed individually for the data it consumes.                                             | A single data allowance is shared across all SIMs in the pool.                 |
| **Cost Structure**            | Maximum flexibility. You only pay for the data you use.                                               | A predictable monthly fee for the entire data pool, optimizing costs at scale. |
| **Service Delivery Platform** | [Super SIM Console](https://supersim-app.korewireless.com/)[™](https://connect-app.korewireless.com/) | [ConnectivityPro™](https://connect-app.korewireless.com/)                      |

Ready to find the perfect fit for your deployment? [**Contact a KORE expert today**](https://www.korewireless.com/contact-us/) to learn more about our Super SIM connectivity options.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.korewireless.com/supersim/super-sim-advisories/kore-super-sim-pooled-plans-december-2025.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.