What is the fastest path for Code Radar license activation?
Code Radar license activation binds Free Preview to one local machine and binds paid licenses to machine slots plus repository slots when GitHub Actions tiers are used.
Docs
Activate a license
Free Preview claims one local machine. Paid licenses claim machine slots locally and repository slots for GitHub Actions tiers.
Direct answer
Activate a license
Free Preview claims one local machine. Paid licenses claim machine slots locally and repository slots for GitHub Actions tiers.
Which commands matter first for Code Radar license activation?
Start with `radar activate --free --email <your-email>`, `radar activate <license-key>`, and `radar license status`. These commands keep implementation proof close to the repository instead of turning the docs page into a generic product description.
What evidence confirms Code Radar license activation works?
Confirm machine-slot status, repository-slot status, entitlement validation, and a local scan that confirms the activated workflow works. This evidence should be visible before moving from documentation to a paid or shared workflow.
What should the reader avoid for Code Radar license activation?
Do not reuse paid keys across machines or repositories without deactivating the old slot first. Next step: Use pricing when the buyer needs repository CI slots, or troubleshooting when activation state does not match the expected entitlement.
Content decision bridge
Turn license activation workflow into a product decision.
Readers on Activate a license need a short route from answer-seeking to proof, rollout, and purchase evidence. Free Preview claims one local machine. Paid licenses claim machine slots locally and repository slots for GitHub Actions tiers.
Verify the proof surface.
Activate a license should lead to product proof, not only more reading. For this page, proof means a concrete local scan before the visitor chooses a paid boundary.
activate code scanner licenseteam sast pricing
Start proofApply the repeat workflow.
Activate a license becomes useful when the reader can repeat the workflow from the guide on a real repository. Here, rollout means evidence that clarifies whether Free, Solo, Pro, or Studio fits the job.
developer first sastlocal security review tool
Inspect evidenceChoose the paid boundary.
Activate a license should create a purchase path only when the product owns the next repeated job. For this intent, buying is justified by the need for full scans, repository slots, MCP, exports, or CI enforcement.
repository security gateteam sast pricing
Choose planStart Free Preview
Use an email address to claim the local CLI-only preview on this machine.
radar activate --free --email <your-email>
radar scan . --quickActivate this machine
Use the license key from purchase or redemption. Radar validates online and binds the machine fingerprint.
radar activate <license-key>
radar license statusMove a slot
Deactivate a machine or repo slot before moving the license to another environment.
radar license deactivate-machine .
radar license deactivate-repo .Implementation FAQ
Confirm the command, expected evidence, failure boundary, and next workflow before treating the task as complete.
What is the fastest path for Code Radar license activation?
Code Radar license activation binds Free Preview to one local machine and binds paid licenses to machine slots plus repository slots when GitHub Actions tiers are used.
Which commands matter first for Code Radar license activation?
Start with `radar activate --free --email <your-email>`, `radar activate <license-key>`, and `radar license status`. These commands keep implementation proof close to the repository instead of turning the docs page into a generic product description.
What evidence confirms Code Radar license activation works?
Confirm machine-slot status, repository-slot status, entitlement validation, and a local scan that confirms the activated workflow works. This evidence should be visible before moving from documentation to a paid or shared workflow.
What should the reader avoid for Code Radar license activation?
Do not reuse paid keys across machines or repositories without deactivating the old slot first. Next step: Use pricing when the buyer needs repository CI slots, or troubleshooting when activation state does not match the expected entitlement.