Commercial brief // buyer and executive context

A proof-first path from software evidence to scoped engagement.

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.

Read the scoped pilot brief Review packaging guidance

Current public posture

Five active surfaces, honest readiness boundaries.

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.

Market Active market, liquidity, and asset execution engine.

Gateway Beta and pilot-first integration surface. Local and self-hosted evaluation are the current entry points.

Wallet & SDK + Core Wallet is stable reference client; SDK is Beta/conditional; Core is live shared foundation.

Active public software surfaces

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.

Active Market Surface

Market (conxian-market)

Conxian Market is the active execution engine for liquidity routing, order matching, and asset settlement.

Evaluate now: repository source, market execution specs, and order routing verification harnesses.

Market proof source

Beta / pilot-first

Gateway

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 source

Stable reference client

Wallet

Conxius 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 source

Beta / conditional

Conxius Enclave SDK

Conxius 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.

SDK context SDK proof source

Live shared foundation

Core

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 tier or a promise that every dependent surface is ready.

Core proof source

What can be evaluated now

Evaluation should produce evidence that a buyer, engineering team, and security reviewer can inspect together.

Review active source repositories (including conxian-market and conxian-gateway) and readiness material linked from them.
Build and inspect the Conxius Enclave SDK locally against the documented capability boundary.
Run a Wallet reference-client or integration rehearsal on the agreed Android environment without transferring custody.
Rehearse the Gateway developer path locally or against an instance explicitly provided for a pilot.
Use Core APIs and fail-closed verification boundaries as shared evidence, while recording dependent-surface gaps separately.

What this brief does not claim

Buyer boundary: Public source and a successful local rehearsal do not create a commercial entitlement or readiness certification.

No generally available hosted Gateway or Market endpoint or production settlement service is represented.
No custody of funds, assets, private keys, or signing control is represented.
No blanket provider enablement, adapter coverage, mainnet proof, or production-readiness claim is represented.
No uptime, SLA, operational guarantee, support response target, or compliance commitment exists unless written for the engagement.
No fixed public price, quota, credit balance, or customer usage ledger is implied by this brief.

Buyer and pilot entry paths

Path 01 // evidence review

Start with the public record

Review the source repositories, local setup instructions, readiness documents, and the product boundary that matches the intended workflow.

Open documentation

Path 02 // bounded evaluation

Run a scoped pilot

Use a written scope, named evidence checkpoints, measurable success criteria, and an explicit exit decision before expanding the work.

Open pilot brief

Path 03 // contract discovery

Discuss an institutional program

For procurement, private deployment, or support requirements, define the surfaces, gates, responsibilities, and terms in a contract or invoice.

Contact enterprise

Proof links

Conxian Market repository — market, liquidity, and asset execution source.
Conxian Gateway repository — current middleware source, sandbox, and readiness context.
Conxius Wallet repository — reference client, release, and security context.
Conxius Enclave SDK repository — capability matrix and production-enablement boundaries.
lib-conxian-core repository — shared primitives, API, and fail-closed boundaries.
Pricing and packaging guidance — commercial mechanisms without invented rates or service guarantees.