# UpScalp Lite vs Premium: Choose the Path You Can Operate Calmly **Last reviewed:** 2026-05-22. Lite and Premium are not difficulty badges. Choose the path that matches how well you can read a signal, manage risk, and wait for valid entries. Use Lite when you want a simpler signal flow while you build consistency. Use Premium when you already have a written process and can use extra context without forcing trades. ## Start with the decision that matters | Choose | Best fit | Do not choose it if | | ---------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | Lite | You are still learning how to read entry, stop loss, and take profit fields. | You expect every alert to be a trade instruction. | | Premium | You already follow risk rules and want more signal context. | Extra detail makes you rush, over-size, or second-guess stops. | | Private Beta API | You are an eligible Premium Holder and have been approved through the Access Bot path. | You need a public self-serve API product today. | Start with Lite if you are unsure. A simpler workflow is better than a richer workflow that you cannot follow under market pressure. ## Upgrade only for the right reason | Reason | Better action | | --------------------------------------------------- | ---------------------------------------------------------------------- | | You missed a move and want more alerts. | Review skip discipline before changing access. | | You want Premium context to override risk. | Re-read the risk guide; context does not replace a stop. | | You think API access is included by default. | Treat API as approved beta only and read the automation boundary page. | | You cannot keep Telegram and access setup straight. | Finish the Get Started and Telegram setup guides first. | Premium should add context to a stable process. It should not become a shortcut around missing setup, risk rules, or patience. ## Lite is the safer starting point when 1. You are still learning how UpScalp formats signals. 2. You need fewer inputs before deciding whether to skip. 3. You are setting your first written risk rules. 4. You want to prove you can ignore late entries before using richer context. The goal with Lite is not to trade more. The goal is to build a repeatable process before adding complexity. ## Premium makes sense only when 1. You can define maximum loss before opening the exchange. 2. You can read extra context without treating it as certainty. 3. You can skip a signal even when the quality label looks strong. 4. You can keep access requirements current without interrupting delivery. Current Premium access uses a token-gated requirement shown in the official access flow. The current public docs state `5,000,000 UPSCALP` as the Premium Holder gate. If announcements or the Access Bot show different requirements, follow the official current flow. ## Private Beta API is not the normal onboarding path The API path is a controlled Premium Holder Private Beta. It is for approved users only and should not be treated as a public product path. Do this instead: 1. Complete Premium access first. 2. Use the official Access Bot if you are eligible for beta consideration. 3. Wait for approval before expecting any API behavior. 4. Do not create exchange API keys until an approved beta setup flow explicitly tells you to do so. 5. Never enable withdrawal permissions for any exchange connection. 6. Do not send API keys, exchange credentials, seed phrases, or private keys in Telegram DMs. ## How to decide today Choose Lite today if one of these is true: 1. You have not completed Telegram setup yet. 2. You cannot explain entry, SL, and TP without checking the glossary. 3. You do not have a written max-loss rule. 4. You are choosing Premium mainly because you fear missing better trades. Choose Premium today only if all of these are true: 1. You meet the current access requirement. 2. You can read more context without increasing size. 3. You can skip when price has already moved away from the entry zone. 4. You understand that Premium context does not remove trading risk. ## Next step | If you chose | Next guide | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Lite | [How to Set Up UpScalp Telegram Alerts](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup) | | Premium | [How to Complete UpScalp Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification) | | Not sure | [How to Read an UpScalp Signal Before You Trade](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals) | | Concerned about trade size | [UpScalp Risk Management Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety) | If the next guide creates a conflict with what an announcement, Access Bot, or support route shows today, stop and verify through official links before continuing. ## Related 1. [UpScalp Get Started Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-get-started) 2. [How to Read an UpScalp Signal Before You Trade](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals) 3. [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate) 4. [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) --- # Agent Instructions: 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: ``` GET https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-plans-and-access.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.