Skip to main content
technical fit before procurement

Validate the local workflow before discussing a commercial programme.

Start with a bounded technical validation using the Free local workflow. If the workflow proves relevant, we can discuss the appropriate next step without turning a technical fit conversation into an implied purchase.

Request a fit discussionReview Preview access
For approved Preview recipients

Bounded Free technical validation

A bounded product-fit exercise for approved Preview recipients. It uses the Free local source build only; paid licences, production autofix, signed installers, and live Tier B integrations remain unavailable.

  • Confirm that an approved user can verify and build the history-free Free Preview archive
  • Run the documented offline/no-telemetry workflow against one representative repository
  • Review whether findings and Free evidence outputs are relevant and traceable enough for the intended workflow
  • Record setup blockers, unsupported boundaries, false-positive questions, and the next technical decision
Cost and data boundary: there is no fee for this validation. CipherMap does not ask you to upload repository source. Do not email source, credentials, or sensitive scan output.
Future · discussion only

Commercial fit and readiness scope

This conversation can explore future product and readiness needs, but it is not presently a purchasable service, licence evaluation, quote, or promise of deliverables.

  • A mutually agreed repository and environment scope
  • Baseline source-level cryptographic inventory and finding-review workshop
  • A documented policy-gap summary and prioritized migration-planning observations
  • Technical and executive readout with agreed limitations and next-step options
Commercial boundary: a future licence or assessment requires release promotion, agreed scope, pricing, final terms, and a signed agreement. Discussion does not activate Tier A or Tier B.
A bounded path

One question, one representative workflow, one decision

The validation is deliberately narrow. It does not certify organizational readiness, replace a complete cryptographic inventory, or promise that every finding has an automatic remediation.

  1. 01

    Fit discussion

    Align on the repository type, languages, environment constraints, evaluation question, and decision stakeholders.

  2. 02

    Approved Preview access

    A named recipient accepts the Preview terms and follows the checksum-bound local build workflow. Access is not guaranteed.

  3. 03

    Bounded validation

    The validation window is agreed during the fit discussion. Your team builds, scans, and reviews Free outputs in its own environment.

  4. 04

    Decision readout

    Capture fit, gaps, open questions, and whether to stop, continue product discovery, or discuss a future commercial scope.

Named Preview recipients review the Preview terms, privacy notice, and support boundary before access.

What to prepare for the fit discussion

  • Repository count, representative size, and primary languages
  • Operating system, Go toolchain policy, CI environment, and air-gap constraints
  • The audit, migration, policy, or delivery decision the evaluation should inform
  • Technical reviewer, business owner, target timeline, and procurement constraints

Start with the technical question—not a sales form.

Tell us what decision a representative repository scan should inform. We will reply with fit questions and, when appropriate, the bounded Preview access path.

Request a fit discussion