Private beta

Help shape release evidence for restricted software deployments.

CS Code is looking for software vendors and consultants who need credible buyer evidence without uploading source code by default.

Controlled beta: access is reviewed manually. You can evaluate the CLI and sample evidence asynchronously before scheduling anything.

You sell software into restricted, offline or heavily controlled environments.

A buyer has asked for SBOMs, vulnerability posture, install/rollback notes or update evidence.

You cannot or do not want to upload source code to a SaaS scanner.

You want a repeatable release evidence workflow before scaling into a larger platform rollout.

How access works

Designed for async evaluation, not calendar pressure.

Tell us your company, role and restricted deployment challenge.

We approve a small number of high-fit beta users manually.

Start with non-sensitive/test projects and generate evidence without uploading source code.

Use dashboard upload only after checking `cscode upload --dry-run`.

Send async feedback from the app or by email. A live call is useful but not required.

Beta boundaries

The first goal is to validate evidence format, workflow fit and buyer usefulness with controlled, non-sensitive projects.

Private beta is controlled access, not open self-serve.

Use non-sensitive or test projects first.

Do not upload classified data to the SaaS beta.

Local CLI output works without a CS Code account.

Dashboard upload is metadata-only unless an evidence PDF is explicitly uploaded.

Local CLI demo against a Docker Compose app.

Sample buyer evidence pack generated from demo or representative project data.

Metadata-only dashboard walkthrough.

Upload-boundary review using `cscode upload --dry-run`.

30-minute feedback call on your restricted-release workflow.