Typed at every boundary

Integrate deception without hand-copying the domain model.

HNPT keeps schemas, interfaces, SDK bodies, database adapters, and command contracts distinct—then tests that they still agree.

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.

Rust, Dart, and TypeScript
Tier 1 models and adapters receive the deepest validation for SeaORM, Flutter/Dart, Prisma, Drizzle, and JSON Schema workflows.
Foundation available
17-language client surface
Generated SDK lanes cover TypeScript, Rust, Dart, Python, Go, Java, Kotlin, Swift, C#, C, C++, Ruby, PHP, Elixir, Lua, Zig, and Shell.
In development
Transport-neutral interfaces
Schemas and types remain separate from client bodies so transports can evolve without redefining the domain.
Foundation available
CLI and daemon control
The Rust hnpt CLI, with hpt as its short alias, uses flags-2-env and communicates with the local daemon.
In development
Public API
The reserved API origin will expose tenant-scoped ingestion and control only after cluster ingress and Shared Auth verification are complete.
Reserved, not live

The hostnames are reserved as architecture contracts. Public traffic waits for a verified service, ingress, certificate, and negative auth test.

api.honeypotrus.comTenant API · reserved pending ingress verification

hnpt / hptRust CLI · local daemon control

$HOME/.hnpt/config/hnpt-config.tomlCanonical local configuration path

.zpkg.tomlEcosystem dependency and release authority

Build with us

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