Founding design partners
We're looking for three teams to work with us as Luvion's first design partners. Selected teams receive a free, scoped pilot. Up to two partners who complete validation and the agreed co-development work may receive a Lifetime Founding License for an agreed scope.
Luvion is building distributed authorization for critical onchain operations: contract upgrades, admin changes, minting permissions and bridge controls. The goal is to make sure the operation that executes is exactly what was authorized, with authorization enforced at the execution point.
Discuss your workflow with Kevin
Who we'd like to work with
DeFi, RWA, stablecoin and cross-chain teams with a specific privileged operation to test. You might be reviewing who can upgrade a contract, change an administrator, adjust minting permissions or rotate bridge signers.
The important part is a real workflow, an engineering contact and access to a test environment. You do not need to replace your production systems to take part.
What we'll do together
We'll start with one operation in one testnet, sandbox or isolated shadow environment. The pilot normally takes 7-14 business days after both teams agree the scope and provide the required inputs, with up to four working sessions.
- Map the operation, permissions and possible bypass paths.
- Define the exact intent, policy checks, separated approvals and threshold authorization profile.
- Design the Gate or Adapter boundary and test authorization, rejection, altered requests, replay, failures and recovery within the agreed setup.
- Review the evidence together and identify the work needed for an integration.
You'll receive a control map, an acceptance matrix, a reproducible evidence package and an integration assessment. You'll work directly with our founding team, and your feedback will help shape the product.
The free offer covers Luvion's work on this design-validation pilot. Infrastructure, third-party costs and custom production development are separate and must be agreed before any chargeable work starts. The pilot uses test assets and non-sensitive examples, not production keys, customer data or live funds. There is no obligation to buy a production deployment.
Lifetime Founding License
Up to two partners can qualify after completing the pilot, joint acceptance and agreed co-development commitments. These include ongoing technical feedback, product reviews and an agreed reference or case study. Any public use of a partner's name, logo or results requires written consent.
The benefit is a waiver of base software licence fees within an agreed scope, not unlimited access to every Luvion product or service.
| Included scope | Agreed before the licence is granted |
|---|---|
| Partner | One original legal entity and protocol |
| Protected authority | One defined authority domain, such as upgrades or bridge administration |
| Deployment | One production environment and one test environment, with one supported standard Guard or Adapter |
| Usage and maintenance | Agreed authorization allowance, standard maintenance and review support |
Dedicated nodes or committees, cloud and Gas costs, third-party services, audits, custom Adapters, additional domains and premium support are outside the waiver. Usage limits and any out-of-scope fees are agreed in writing.
The licence continues while the original partner and protocol remain in scope and Luvion continues to offer the corresponding product, subject to the agreement. It is not transferable. Production use requires its own readiness review and agreement; completing a pilot does not establish production readiness.
Partners who prefer to keep the engagement private can still apply for a free pilot. A public reference is not required for that stage.
Start a conversation
Email Kevin@luvion.dev with your project, your role and one operation you'd like to explore. A short description is enough; please leave confidential technical material out of the first message.
We'll first discuss whether the workflow fits. Before starting, both teams agree the inputs, responsibilities, acceptance criteria and commercial boundaries. Participation and lifetime licences are subject to selection and written agreement, not automatically granted on enquiry.
Technical details
- Design-partner pilot: phases and test scope.
- Acceptance and ownership: joint review and responsibilities.
- Current implementation status: what has been validated and what remains to be built.
- Target architecture: the wider architecture, including high-threshold profiles and dynamic committees. A narrow pilot does not remove these capabilities from the target design or promise their production delivery.