The first cohort of onchain private credit issuers on Avalanche.
Plyra is opening a closed beta with institutional credit issuers, SDK integrators, and allocators. The Phase 3 target is written feedback from Avalanche-sourced testers. We run the operator. You run the testnet deal path.
What this is
Plyra is onchain credit infrastructure – Forge (structured credit vaults with senior/mezz/equity tranching), Shield (credit default swaps), and Nexus (cross-chain margin). Twenty-four verified contracts on Avalanche Fuji. 757 passing tests. Live AI analyst. The production privacy decision is standard ERC-20 assets on a private Avalanche L1. The completed eERC proof work is archived Phase 3 research, not a planned production component.
The beta is closed and curated. We are not opening this to self-serve applications from cold web traffic. Participant evidence is being gathered through Avalanche BD relationships, Avalanche Foundation channels, Pete, Matt, Brittany, and other Avalanche-introduced paths.
BitHedge Genesis Vault is the Fuji anchor example. It should not be counted as Avalanche BD-sourced unless Avalanche confirms that source channel, and any mainnet timing depends on audit, legal, and capital-readiness work.
Three cohorts. Six to nine participants total.
SDK integrators
Existing Avalanche protocols embedding Plyra as their credit primitive – vault factory, AI risk scoring, tranching – without rebuilding it. White-glove integration support during beta.
- You already have users and want a credit product surface
- You'd rather integrate than rebuild structured credit primitives
- You can ship a working integration inside the beta window
Vault issuers
The headline cohort. Native issuers of real credit vaults – RWA originators, private credit funds, structured credit shops. BitHedge Genesis is the anchor, already live on Fuji.
- You originate or structure private credit and want onchain rails
- You have a real deal or pipeline (not a hypothetical product)
- Standard ERC-20 vaults with a private-L1 production path
Allocators
Funds or tokenization shops seeking onchain exposure to private credit but blocked by the lack of permissioned rails. Allocate into Cohort B vaults, or commission a custom vault via the SDK.
- You want exposure to onchain private credit
- You need permissioned or private rails for accredited capital
- Size flexible – a $50K signal allocation is welcome
The exchange is asymmetric – by design
| Cohort | You get | We ask |
|---|---|---|
| Cohort A – SDK integrators | Free SDK access. Direct integration support from the team. First-loss tranche tooling. AI analyst access. Joint marketing at Avalanche Summit. | One shipped integration. Public case study. Permission to cite as a beta participant. |
| Cohort B – Credit issuers | End-to-end vault setup (encrypted or plaintext). Legal scaffolding via existing structured-credit counsel relationships. Operator-as-a-service during beta. AI risk scoring on your collateral. Summit demo slot. | One live vault. At least one real allocator deposit. 30-day retro. Permission to cite. |
| Cohort C – Allocators | Permissioned rails into beta vaults. Direct access to issuer reps. Audit and risk-scoring transparency. | One real allocation (size flexible). Feedback retro. Permission to cite. |
We are not paying participants. The currency is white-glove support and joint marketing through Avalanche channels. The earliest issuers on Plyra get to define the playbook.
The protocol is shipped – the program surface is what's new
From intro to live in five steps
- 01Warm introAvalanche BD or Foundation makes the introduction. We reply same-day and schedule a 30-minute fit call.
- 02Fit callConfirm cohort, use case, and timeline. Sign a short beta participation agreement covering case-study consent.
- 03Technical onboardingCohort A: SDK + integration. Cohort B: vault setup + operator handoff. Cohort C: KYC + allocation pathway.
- 04Live milestoneCohort A ships an integration. Cohort B deploys a Fuji vault and takes a testnet deposit. Cohort C evaluates a testnet allocation workflow.
- 05Retro + spotlight30-day retro. Joint marketing across Avalanche channels. Graduate from beta to live customer.
hello@plyra.io with your application – or have your Avalanche referrer route you to us directly.The application asks for name, company, cohort fit, use case, intro source, and timeline. Hitting reply on a warm intro from Ava Labs BD or the Avalanche Foundation records the source channel for the Phase 3 packet.