Choosing between free and premium KocakZ access is easier when you separate four questions: how long the key lasts, how many devices it can bind, how many sessions can run, and which claim steps are required. These limits solve different problems, so comparing only one number gives an incomplete picture.
This guide explains the current access model and shows how to decide which tier fits your actual use. For the complete free claim sequence, read How to Claim Your First KocakZ Key.
Free and premium at a glance
| Feature | Free access | Premium access |
|---|---|---|
| Key validity | 24 hours | Up to the paid entitlement expiry |
| HWID allowance | 1 device identifier | Up to 5 device identifiers |
| Active session allowance | Up to 5 | Up to 50 |
| Discord identity | Required | Required |
| Human verification on website flow | Required | Required |
| Blog checkpoint | Required | Skipped |
| Discord Get Key | Returns a valid key or creates a claim | Returns or creates the premium key directly |
Premium is useful when you need longer access, several devices, more concurrent sessions, or a shorter claim path. Free access is suitable when one device and a 24-hour key are enough.
A key, an HWID, and a session are different
Many access questions become confusing because these three terms are treated as if they mean the same thing.
A key is the credential stored for a Discord account. It has a tier, an issue time, an expiry, and its current bindings. Requesting Get Key again while it remains valid returns that same credential.
An HWID is the device identifier presented when the loader starts an authenticated script session. Generating a key in the browser does not bind an HWID. The first accepted loader run creates the binding, subject to the tier's allowance.
A session is one active script run. Sessions have their own server-tracked activity. The loader sends a heartbeat every 20 minutes, and a session becomes stale after 45 minutes without a valid heartbeat. Closing something locally and freeing its server slot are therefore not always simultaneous.
The practical lesson is to read which limit an error names. A new key is not the answer to every HWID or session problem.
How free access works
A free user connects Discord, passes Turnstile, and completes an assigned blog checkpoint. The server verifies ownership and state at each important step. After completion, it issues one 24-hour key associated with that Discord account.
Free access allows one HWID. This does not mean one browser, one claim tab, or one Discord session; it means one device identifier accepted during loader use. The key can support up to five active script sessions within the free tier's other limits.
When the free key expires, it can no longer authorize new use. The user may begin a new claim and complete the current free flow again. An old completed flow does not reactivate itself, and repeatedly retrieving a still-valid key does not move its expiry forward.
Free access is a good fit when
- You use one device.
- You need access for a short session or day.
- Five active sessions are more than enough.
- Completing the verification and content checkpoint is acceptable.
- You are evaluating whether KocakZ fits your use.
Free does not mean untracked or unlimited. It uses the same account ownership, expiry, HWID, and session enforcement principles as premium with smaller limits and an extra checkpoint.
How premium access works
Premium access is backed by a paid entitlement stored for the Discord account. The entitlement is the source of truth even if Discord role synchronization is temporarily delayed. Each supported Trakteer unit adds 30 days, stacked onto the remaining entitlement when it is still active or onto the current time when it has expired.
A premium key does not automatically receive an extra 30 days every time it is requested. Its expiry follows the paid entitlement. This prevents a late claim from extending access beyond the supported period.
Premium supports up to five HWIDs and 50 active sessions. It also skips the free blog checkpoint. A premium Get Key request in Discord can create the key if none exists or return the stored valid key.
Premium is a better fit when
- You regularly use more than one device.
- You need access beyond a single 24-hour period.
- Your workflow involves more than five active sessions.
- You prefer to skip the recurring free content checkpoint.
- You want to support KocakZ through its configured payment channel.
Larger allowances are not a reason to expose a key. Every person should use their own Discord-linked access rather than sharing a credential and consuming another account's device or session capacity.
What happens when a free account becomes premium
A payment extends the account's premium entitlement. The current implementation upgrades the account's existing access in place rather than treating payment as permission to create duplicate keys. The key's tier and expiry align with the entitlement, while the larger premium limits become available.
This design protects continuity: normal payment processing does not need to discard all existing bindings merely to change the tier. Payment does not clear revocation on an existing key. The issuing code blocks replacement while a revoked key remains unexpired; after its expiry, a later eligible claim can issue a new key. Contact support about a revocation instead of treating a purchase as a reset.
Discord role synchronization is a visible convenience, not the database authority for access. If the provider or Discord is temporarily unavailable, the role can lag behind the entitlement. Avoid buying again merely because a role update is delayed; check the account state and ask support with the transaction context, without sharing payment credentials.
How payment duration is calculated
KocakZ currently treats one supported Trakteer unit—IDR 15,000—as exactly 30 days. Whole units are calculated from the accepted payment amount, and partial amounts below a full unit do not create a fractional access period.
For example:
- One unit grants 30 days.
- Two units grant 60 days.
- A new purchase made with 10 days remaining adds its duration after those remaining 10 days.
- A purchase made after expiry starts from the processing time.
The payment message must contain one unambiguous line in the form Discord: yourID. Use the Discord user ID belonging to the account that should receive access. Do not place a password, token, or KocakZ key in the payment message.
Decision framework: which tier fits?
Use this sequence instead of choosing only by the biggest number.
- How long do you need access? If one day is sufficient, free may fit. Recurring or longer use favors premium.
- How many devices will actually run the loader? One fits free. Two to five requires premium under the current limits.
- How many active sessions do you legitimately need? Compare the free limit of five with the premium limit of 50.
- How often are you willing to complete a checkpoint? Free keys require a new claim after expiry. Premium skips the content checkpoint while entitlement remains active.
- Are you choosing for yourself? Do not select a tier based on plans to share a credential; keys remain account-bound access.
| Situation | Likely fit | Reason |
|---|---|---|
| One device for an occasional day | Free | The duration and HWID allowance match. |
| Desktop and laptop use | Premium | Free permits only one HWID. |
| Regular use over several weeks | Premium | Entitlement avoids daily free reclaims. |
| Testing whether the workflow suits you | Free | You can evaluate it without a paid period. |
| One device but many legitimate concurrent sessions | Compare carefully | Session need, not HWID count, determines the constraint. |
This is a fit framework, not a recommendation to maximize spending. Choose the smallest tier that supports the duration and limits you genuinely need.
Common misconceptions
"Generating a key binds my browser or computer"
It does not. Key generation and hardware binding are separate. The binding occurs when the loader submits a device identifier during an accepted script start.
"Pressing Get Key again gives me a new expiry"
A valid stored key is reused. Repeated retrieval does not refresh free access or extend premium beyond its entitlement.
"Five sessions means five devices"
Sessions and HWIDs are separate allowances. Free access can have several active sessions while still permitting only one bound HWID.
"The Discord role alone decides premium access"
The database entitlement is authoritative. Role synchronization can be delayed by an external service failure without changing the intended paid expiry.
"Closing the game immediately removes the session"
Cooperative cleanup can stop a session, while stale-session handling provides a fallback. A recently closed run may not disappear from server state at the exact instant the local window closes.
Check your access before troubleshooting
When something is rejected, gather these facts in order:
- Which Discord account owns the key?
- Is the key still before its displayed expiry?
- Does the message mention HWID, session, revocation, or connectivity?
- How many devices have actually used the key?
- Are old sessions still within the heartbeat/stale window?
Do not post the full key in a support channel. Share the non-secret error, approximate time, tier you expected, and whether the issue occurs on one or several devices.
Choose the access period you will actually use
Compare the tier with a concrete pattern of use
Start with the period during which you expect to use the service. Someone who needs one occasional day faces a different choice from someone returning regularly across several weeks. Duration is a practical requirement, not simply a number to maximize.
Next, count the devices that will actually submit identifiers during loader use. Opening the website on a phone to retrieve information is not the same as running the loader on another device. This distinction can prevent you from overestimating the HWID allowance you need.
Finally, consider overlapping runs rather than the total number of launches across the whole access period. Session capacity concerns current active state. A large lifetime total of separate attempts does not necessarily mean many simultaneous sessions, while several overlapping runs can reach a limit quickly.
Two hypothetical choices with different constraints
Imagine a user who returns occasionally on one device and runs only one session at a time. Their main question may be whether completing the free claim after expiry fits their routine. The larger premium device and session allowances may offer little practical benefit for that specific pattern.
Now imagine a user who works across two devices during the same paid period. Their device requirement exceeds the free allowance even if they never run more than a few sessions. In that case, the HWID difference matters independently of whether the higher session ceiling is used.
These examples are illustrations, not reports of customer behavior. Use them to identify which constraint applies to your own situation. Choosing a tier from the biggest headline number can obscure the smaller limit or timing detail that actually controls your workflow.
Check current account state before changing tiers
An access failure is not automatically evidence that the lower tier is insufficient. Expiry, revocation, a malformed copy, or an unavailable request can produce a rejection that larger capacity will not address. Read the exact message before treating payment as troubleshooting.
If the problem is a genuine device or session allowance, compare that need with the tier limits. If it concerns account identity, reconnect the intended account. If it concerns an expired free period, decide whether a new free claim or a paid period matches the duration you want.
For an unexpected premium state, preserve the transaction reference and account context for support. Avoid exposing payment credentials or buying again merely to see whether the website changes. An attribution or processing question needs evidence about the original transaction.
Keep payment timing and key retrieval timing separate
The implementation extends premium entitlement from the later of the current expiry and the processing time. This means an active period can retain its remaining duration when a supported extension is applied. It also means an expired entitlement does not gain time from a date that has already passed.
A key retrieved during that period follows the entitlement expiry. Requesting it later does not add another full period beyond the account's paid end. Read the date shown after processing rather than estimating it from when you last pressed Get Key.
Check the payment method and instructions currently offered on the homepage. Different provider workflows can use different attribution details, while the account entitlement remains the state the application uses for access. Do not assume instructions copied from an old message describe every currently available checkout route.
Plan for ordinary interruptions
Consider how you will return after a break, switch between intended devices, and close runs you no longer need. A tier choice does not replace those habits. Keeping the owning account and current result identifiable helps you use either tier without accumulating uncertain copies and old flow links.
If a local run closes unexpectedly, session cleanup may not be reflected at the same instant. Record the timing before assuming your allowance has permanently decreased. The distinction between a recently active session and a stale one can matter at the next allocation.
When your needs change, repeat the comparison using actual duration, device count, and concurrent runs. You do not need to defend an earlier choice if your pattern of use is now different. The useful decision is the one that fits the next period and the current rules.
Before choosing a tier, write down how long you need access, how many devices will run the loader, and how many sessions may overlap. Compare those needs with the table above, then open the KocakZ homepage with the Discord account that should own the key. Check the payment options and account details shown there if you decide to use premium.
If the numbers are still confusing, read how keys, devices, and sessions differ before changing your access. A device limit and a session limit describe different constraints, and understanding the one you actually reach will help you avoid an unnecessary purchase or another duplicate claim.