Conxian Labs builds and operates the software surfaces around the Conxian ecosystem. Buyers can start with public source, local evaluation, and documented boundaries, then choose a bounded pilot or a contract-scoped path when the evidence and use case justify it.
The public portfolio is intentionally evidence-led. Readiness is stated per surface; a repository, demo, or local response is not by itself a hosted-service, settlement, custody, or availability commitment.
Each surface has a distinct role in evaluation and engagement. Follow the source and readiness evidence before treating a capability as a fit for a specific program.
Conxian Gateway is the integration surface for application workflows and verification rehearsal. The current public path is local or self-hosted pilot work; there is no generally available hosted endpoint or production settlement claim.
Evaluate now: source, developer sandbox, health and supported-chain discovery, and agreed local proof rehearsal.
Gateway proof sourceConxius Wallet is a stable, non-custodial, Android-first reference client. It supports demo and integration-to-launch evaluation; it is not a hosted or custodial service, and this brief makes no mainnet-proven claim.
Evaluate now: client source, local signing boundaries, device assumptions, and a scoped integration plan.
Wallet proof sourceConxius Enclave SDK is the builder surface for enclave, signing, attestation, and key-management boundaries. It is available for local evaluation and integration work; no production readiness or provider enablement claim is made here.
Evaluate now: repository capability and readiness documents, local builds, and the specific interface needed for the use case.
lib-conxian-core is the live shared software and credibility foundation beneath the public stack. It exposes stable API and fail-closed verification boundaries while launch and commercial gates remain in progress.
Commercial boundary: Core is shared foundation software, not a paid fourth tier or a promise that every dependent surface is ready.
Core proof sourceEvaluation should produce evidence that a buyer, engineering team, and security reviewer can inspect together.
Review the source repositories, local setup instructions, readiness documents, and the product boundary that matches the intended workflow.
Open documentationUse a written scope, named evidence checkpoints, measurable success criteria, and an explicit exit decision before expanding the work.
Open pilot briefFor procurement, private deployment, or support requirements, define the surfaces, gates, responsibilities, and terms in a contract or invoice.
Contact enterprise