A sin-bin with due process

Contain the session. Preserve the way back.

Quarantine is a lease, not a verdict. Every action is tenant-scoped, reasoned, idempotent, expiring, reviewable, and reversible.

Early accessStatus labels distinguish working contracts from active build and roadmap items.

What the platform is designed to deliver

Each capability carries an explicit delivery state. We do not present a roadmap item as a deployed control.

  • Reasoned case creation

    A case names its tenant, evidence set, policy, proposed scope, confidence, and review owner.

    Contract available
  • Expiring enforcement leases

    Rate limits, challenges, route shaping, and quarantine actions carry start, expiry, renewal, and idempotency identities.

    Contract available
  • Release workflow

    Analysts can request release, but only policy-authorized executors change enforcement state and record the outcome.

    Contract available
  • Owned isolated playpen

    Synthetic services can keep a suspicious actor engaged without production data, credentials, or reachability.

    In development
  • Third-party redirect

    Sending suspicious traffic to unrelated sites is intentionally excluded. HNPT never externalizes the risk to an uninvolved party.

    Safety invariant

The playpen is not production with the labels removed.

It is a separately owned isolation boundary built from synthetic data, fake identities, disposable services, and denied production egress.

No unrelated destinations

Suspicious actors are never redirected to search engines, consumer sites, or any third party that did not consent to receive them.

Review changes the state

Evidence can recommend an action. A typed policy and authorized executor decide whether that action starts, extends, releases, or expires.

Build with us

Start with a bounded, observable pilot.

Define what may be observed, what a quarantine can affect, how it expires, and who reviews the evidence before connecting a production system.