Developer platform
Build quantum-secure infrastructure in minutes
First-party SDKs in TypeScript, Python, Go, Rust, and JVM/Android plus documented REST APIs. Package availability and operation support are verified separately.
Quick start
From zero to quantum-secure in 4 steps
Sign up free
Create your account at cloud.qnsi.heossi.com and provision your tenant in minutes
Install SDK
SDK install and usage instructions are provided in the documentation portal
Upload your first document
Use QNSI APIs to upload documents with quantum-secure encryption
Build your app
Integrate QNSI into your application with full PQC protection
Most Requested Tier - Dev Team
$1,499/month - designed by the community. CBOM export, quantum readiness reports, 90-day audit retention included from day one.
Request lifecycle
How a QNSI API call flows.
What happens between an SDK call and a tamper-evident audit-ledger entry. The dashed cross-verification branch on signing operations (liboqs + @noble/post-quantum, with provider attestation written into the Merkle ledger) is the architectural choice that sets QNSI apart from single-provider PQC platforms.
Cross-verification logic and audit-chain checkpoint generation are both independently reproducible from the public mirror at github.com/heossihq/qnsi-public.
Migration build path
How engineering teams move workloads onto QNSI
Most teams start with APIs and SDKs, but the broader migration path is the same: connect sources, discover what exists, then cut workloads over so production trust calls QNSI directly.
Connect sources
Use provider connectors for AWS, Azure, GCP, Vault, and supported APIs. Use QNSI agents where discovery must happen inside private environments.
Discover and inventory
Run discovery before refactoring application code so the migration plan is based on actual keys, secrets, certificates, and cryptographic dependencies.
Switch application trust paths
Update services, CI jobs, agents, and apps to call QNSI KMS, Vault, storage, search, audit, and policy-managed interfaces through SDKs, APIs, and the CLI.
Validate evidence
Use readiness reports plus CBOM, QBOM, and SBOM outputs to verify cutover and prove that production no longer depends on legacy trust systems.
SDK packages
SDKs in TypeScript, Python, Go, Rust, JVM/Android - free on every plan
One package per language, all sharing the same wire contracts: TypeScript (pnpm add @heossihq/qnsi), Python (pip install qnsi), Go (go get github.com/heossihq/qnsi-public/sdks/go/qnsi@latest), Rust (cargo add qnsi), JVM/Android (implementation('com.heossi:qnsi:0.4.0')).
@heossihq/qnsi (npm - TypeScript / Node.js)AvailableSingle Node.js / TypeScript package covering all 11 QNSI services, webhook verification, activation, HSPK client methods, and the local `qnsi crypto scan` CLI. Replaces the 11 deprecated per-service @heossihq/qnsi-*-sdk packages.
qnsi (PyPI - Python)AvailableSingle Python package mirroring the same 11-module surface, plus local PQC primitives (qnsi[crypto] extra → liboqs-python) and webhook verification.
github.com/heossihq/qnsi-public/sdks/go/qnsi (Go)AvailableSingle Go module with the 11-service surface as sub-packages (qnsi/vault, qnsi/kms, …) + qnsi/crypto via liboqs-go. Concurrency-safe activation cache; share one client across goroutines.
qnsi (crates.io - Rust)AvailableTokio-based Rust crate with all 11 services as modules (qnsi::vault, qnsi::kms, …) + qnsi::crypto behind the `crypto` feature flag (oqs 0.11). Client is Send + Sync and cheap to clone.
com.heossi:qnsi (Maven Central - JVM / Android)AvailableKotlin SDK with a Java-interop-clean API; all 11 services as sub-clients plus webhook verification. Built on OkHttp-one artifact for Spring/JVM backends and native Android (API 21+).
@heossihq/qnsi-mcp (npm)AvailablePublished Model Context Protocol server exposing QNSI tools, including HSPK seal/sign operations, to compatible AI assistants.
SDK access and full API reference: docs.qnsi.heossi.com · npmjs.com/package/@heossihq/qnsi
API reference
REST API - Edge Gateway
All services accessible via a single edge gateway. Full OpenAPI specifications available in the documentation portal.
https://api.qnsi.heossi.com/auth/v1/tenant/v1/billing/v1/storage/v1/vault/v1/kms/v1/search/v1/ai/v1/platform/v1CI/CD Integration
GitHub Actions
Workflow templates for SDK usage, API key injection, and PQC audit webhooks.
GitLab CI
Pipeline examples for vault secrets injection and PQC-signed artifact verification.
Jenkins
Shared library examples for QNSI SDK integration and compliance report generation.
CircleCI
Orb examples covering auth, storage upload, and audit log retrieval.
FAQ
Developer FAQ
Direct answers to the questions developers ask before building on QNSI.
What SDKs does QNSI offer?
QNSI ships first-party SDKs for five languages, one package per language, all sharing the same wire contracts across 11 services: TypeScript/Node (@heossihq/qnsi on npm), Python (qnsi on PyPI), Go (github.com/heossihq/qnsi-public/sdks/go/qnsi), Rust (qnsi on crates.io), and JVM/Android (com.heossi:qnsi on Maven Central). All are free on every plan.
Is there a free QNSI tier?
Yes. QNSI has a free-forever tier with no credit card required. It includes 10 GB of storage allocation, 50,000 API calls per month, 20 KMS keys, 25 vault secrets, and SDK access. Entitlement does not prove that every operation or PQC transport path is available; verify the exact service and evidence required.
Resources