Getting Started
What WorkCheats is, who it is for, and how to get access during closed beta.
WorkCheats is an operational workspace for authorised security work. It helps you organise commands, workflows, sessions, variables, notes, and reports in one place — for labs, defensive validation, incident response, and professional technical operations.
WorkCheats does not execute scripts or commands. Commands and scripts are content artifacts you store, organise, and copy when you choose to run them in your own authorised environment.
Who WorkCheats is for
WorkCheats is built for people who need a structured, trustworthy workspace for technical operations, including:
- Penetration testers and red-team operators working under authorisation
- Defensive security, SOC, and DFIR practitioners
- Lab and CTF practitioners building repeatable methodology
- Team leads who need shared operational libraries and traceability
You do not need to be a developer to use WorkCheats. The interface is designed for both technical and non-technical users who follow step-by-step workflows.
Closed beta access
WorkCheats is in closed beta on production infrastructure. It is not generally available and there is no public launch yet.
| Rule | What it means for you |
|---|---|
| Invite or access required | You need beta access or a private invitation. Product access is controlled by beta grants — not open self-serve signup for everyone. |
| Sign-up may be reachable | The sign-up page may be available by direct link or invite, but creating an account does not guarantee full product access without the expected grant. |
| Features may change | UI, capabilities, and documentation may change between releases during closed beta. |
| Billing is not live | Public Pricing shows a preview for planning only. There is no live checkout, real subscriptions, or paid unlocks during closed beta. |
Need access? Use Contact to request beta access, or use the sign-up link your operator shared if you already have an invite.
- Request or receive an invite from your organisation or the WorkCheats team.
- Create your account using the sign-up flow linked from your invite.
- Sign in and complete MFA if your account requires it.
- If you cannot sign in or see expected features, see Troubleshooting or Feedback & support.
Create your account
- Open the sign-up page from your invite link (or
/auth/sign-upwhen your host allows it). - Enter your email and choose a strong password.
- Complete any captcha or spam-protection step shown on the form.
- Confirm your email if prompted.
- Complete your profile after first sign-in.
Screenshot placeholder: Account creation screen showing the WorkCheats sign-up form.
Sign in and MFA
When enabled for your environment, you can sign in with:
- Email and password
- GitHub
Available methods depend on how your host is configured. If a provider button is missing, that method is not enabled there.
- Go to the sign-in page and enter your credentials, or choose a provider.
- If MFA is enabled, enter the code from your authenticator app after password or OAuth sign-in.
- You land in your personal workspace at
/home.
Screenshot placeholder: Sign-in screen with email, password, and MFA verification step.
If sign-in fails repeatedly, see Troubleshooting.
Captcha and spam protection
WorkCheats uses different spam protection on different surfaces:
| Surface | Behaviour |
|---|---|
| Password sign-up / sign-in | May show a captcha challenge or verify invisibly in the background, depending on host configuration. |
| Contact form | Uses its own spam protection — separate from sign-up or sign-in. |
| OAuth (Google / GitHub) | Uses the provider’s sign-in flow. OAuth does not use the WorkCheats sign-up or contact-form captcha path. |
If captcha fails or loops, try another browser, disable aggressive privacy extensions temporarily, or use Feedback & support.
Personal workspace vs team workspace
WorkCheats supports two workspace types:
- Personal workspace — your individual account at
/home. Your library, workflows, and settings belong to you. - Team workspace — a shared account for collaborators at
/home/[team]. Content and permissions are scoped to that team.
You can switch between workspaces from the workspace menu in the app header. Team features depend on your beta access and team membership.
Screenshot placeholder: Workspace switcher showing personal and team workspaces.
Where to go next
- Core Workspace — profile, settings, billing preview notes, search
- Command Library — organise operational commands
- Marketplace — install curated packs (trusted server-side copy)
- Import & Export — upload packages (always untrusted until you confirm)
- Security & Responsible Use — authorised use and content safety
- Feedback & support — in-app feedback widget and bug reports
Roadmap
The following are not available yet and may change before general release:
- Public launch and open self-serve signup without invite or grant
- Live billing, checkout, and paid plan activation
- Expanded onboarding tours and in-app guides
- Additional workspace types or enterprise onboarding flows

