HowHow is in private alpha•Request early access
HowHow

Plan a deployment before calling it ready.

A discovery path for custom boundaries, policy and integrations. Production deployment is not yet available.

  • DISCOVERY ONLY
  • NO CERTIFICATION CLAIM
  • CUSTOM SCOPE
Start discoveryRequest a walkthrough

DISCOVERY SCOPE

Four things to verify before a pilot is proposed

01DEPLOYMENT

Define the required boundary

We map data, compute, network and export requirements before proposing a pilot. Self-hosted and private networking remain unverified until tested in the target environment.
  • Environment review
  • Boundary mapping
  • Export requirements

02POLICY

Plan your approvals

Target policy can include egress rules, allowlisted providers, budget reservations and explicit approval boundaries. Organisation-wide enforcement remains subject to implementation and validation.
  • Policy design
  • Budget boundaries
  • Approval requirements

03REVIEW

Satisfy your own reviewers

The target evidence trail is inspectable by someone who did not run the work: source spans, run manifests, gate reports, limitations and dissent remain attached where supported.
  • Inspectable chain
  • Audit export
  • Limitations retained

04INTEGRATION

Fit the tools you already run

Integration planning identifies which literature providers, model providers, runners and data sources are actually supported, partial, or still to be built.
  • Replaceable adapters
  • Pinned dependencies
  • No dual source of truth

THE PROCESS

From first call to a pilot decision

  1. 01STEP

    Scoping call

    The question class, data and code constraints, compute environment and review requirements.

  2. 02STEP

    Security review

    Egress, secrets, sandbox boundary, retention and audit expectations.

  3. 03STEP

    Pilot decision

    If feasible, define one bounded episode and the evidence required before any broader readiness claim.

  4. 04STEP

    Terms and rollout

    Commercial terms and access are agreed only after scope and current capability are explicit.

BOUNDARY

What we will not claim during procurement

Security posture

Egress, secrets, sandbox limits and audit expectations are documented as they actually are.
Read the security page →

Execution limits

TRUSTED_LOCAL is bounded execution, not an OS sandbox. Hostile code needs an external container.
Read the execution profiles →

Review artefacts

The package, gate report, limitations and dissent are what your reviewers will actually read.
Read the gate list →

NEXT

Start with the security conversation.

Bring the constraints that matter. We will separate current evidence, implementation work and unknowns before discussing a pilot.

Start discoveryPricing
Enterprise — HowHow