Stringer — Managed Post-Quantum Zero Trust
Stringer is a fully managed post-quantum zero-trust network access (ZTNA) service. We deploy, run, and support the AVON platform for federal and commercial customers, so you get the cryptography and the compliance posture without standing up an operations team for it.
How Stringer relates to AVON
AVON is the open-source post-quantum ZTNA platform we steward. It’s free, Apache 2.0 licensed, and self-hostable. Anyone with the operational talent can run AVON in their own infrastructure — and many do.
Stringer is the same software, operated for you. It’s the same relationship as Red Hat to upstream Linux: the open-source project remains free and unencumbered, and Stringer is the commercial offering for teams who’d rather buy the operations.
You can move between the two. Customers sometimes start by self-hosting AVON, then move to Stringer when their team’s priorities shift; others start with Stringer and graduate to self-hosting once their internal team is ready. Both paths are first-class.
What you get with Stringer
- Managed deployment. We stand up the platform in your environment of choice (cloud or on-prem) and run it under SLA.
- Continuous compliance. FIPS-validated post-quantum cryptography with audit-ready evidence, mapped to the controls you have to attest against.
- 24/7 operations. Engineering on-call with named escalation paths, P1 response under one hour for Enterprise.
- Federal-ready architectures. IL-N target, US-citizen support, FedRAMP-aligned controls under separate contract vehicles.
- Custom engineering. Protocol extensions, MDM bridges, custom policy engines — the team that built AVON also writes the code that integrates it with your stack.
Who Stringer is for
Stringer fits teams that:
- Have a post-quantum migration on the docket and don’t want to staff an operations rotation around new cryptographic infrastructure.
- Need FedRAMP-aligned or SOC 2 Type II–aligned posture and would rather inherit ours than build their own.
- Want the option of self-hosting AVON in the future without locking themselves out of it now.
- Have unusual integration requirements (custom IDPs, exotic MDM, regulated networks) that need engineering work, not just configuration.
Where to next
- Getting started — what onboarding looks like, day-by-day.
- Support — SLA tiers, escalation paths, contact channels.
- Everything else in the sidebar — operator-facing reference material, much of which is being authored. If a page is marked “Coming soon,” contact us and we’ll walk you through the topic on a call.