Partitions beyond your resource plan quota consume broker resources on the ApsaraMQ for Kafka cluster and are billed separately.
Why additional partitions incur charges
A self-managed open source Apache Kafka cluster experiences sharp performance degradation when it exceeds more than 1,000 partitions. ApsaraMQ for Kafka removes this limitation. A topic can hold an unlimited number of partitions without performance degradation. However, each partition still requires broker resources. When your total partition count exceeds the quota included in your resource plan, the extra partitions are treated as additional partitions and incur charges.