For you

Find your path through Confium

Confium is a heavy system — 43 crates, three deployment modes, a dozen protocol implementations, multiple standards integrations. The right entry point depends on what you're trying to do. Pick the audience below that matches your role.

Business value, risk, and compliance

Executives

You're evaluating Confium for organizational adoption. You need to understand the cost model, the risk reduction, the compliance hooks, and how it compares to the PKI you already operate.

You\'re asking

? What does it cost to deploy?
? What risks does it mitigate?
? Which compliance frameworks does it support?
? Who else has deployed it?

Read the executives guide →

Threat model and integration patterns

Security architects

You're designing a deployment. You need the threat model, the integration patterns, the defense-in-depth story, and the failure modes for every component.

You\'re asking

? What's the trust model?
? How does it integrate with my existing PKCS#11 / OpenSSL / JCE consumer?
? What are the failure modes?
? How does defense in depth work?

Read the security architects guide →

API, examples, and SDK choice

Developers

You're building an application that consumes Confium. You need to pick a binding (Ruby / Rust / WASM), get to a working verify in five minutes, and understand the typed error model.

You\'re asking

? Ruby, Rust, or WASM — which do I use?
? How do I verify a signature?
? What does error handling look like?
? Where are the examples?

Read the developers guide →

Deployment, monitoring, and runbooks

PKI operators

You're running Confium in production. You need the deployment runbook, the monitoring hooks, the backup and recovery procedures, and the upgrade path.

You\'re asking

? How do I deploy a coordinator?
? What metrics should I monitor?
? How do I back up threshold shares?
? How do I rotate signers without downtime?

Read the pki operators guide →

FIPS, jurisdictions, and audit

Compliance officers

You're responsible for regulatory alignment. You need to know which FIPS mode Confium supports, how jurisdictional policies work, what the audit log format is, and how it maps to eIDAS / HIPAA / FedRAMP.

You\'re asking

? Is there a FIPS 140 mode?
? How do jurisdictional algorithm policies work?
? What's in the audit log?
? How does it map to eIDAS / HIPAA / FedRAMP?

Read the compliance officers guide →

Test vectors, benchmarks, and protocol references

Evaluators and researchers

You're evaluating Confium against alternatives (NIST MPTS, academic protocols, commercial threshold solutions). You need test vectors, performance benchmarks, protocol references, and a comparison matrix.

You\'re asking

? How does it perform vs single-key signing?
? Where are the test vectors?
? Which papers describe the protocols?
? How does it compare to other threshold solutions?

Read the evaluators and researchers guide →

Strategic adoption and risk posture

CTOs and engineering directors

You're making the organizational adoption decision. You need strategic framing, vendor-independence analysis, team investment estimates, and a risk table.

You\'re asking

? Why now?
? What's the team investment?
? What if the project is abandoned?
? How does this compare to commercial alternatives?

Read the ctos and engineering directors guide →

Scoping threshold-trust features

Product managers

You're scoping a threshold-trust feature for your product plan. You need to identify the trust boundary, map stakeholders, plan integration timelines, and craft customer-facing value props.

You\'re asking

? What does this look like as a product feature?
? How long does integration take?
? How do I communicate the value?
? What are the common PM pitfalls?

Read the product managers guide →

Code, docs, plugins, security research

Open source contributors

You're contributing to Confium itself. You need the development workflow, coding standards, plugin author guide, and contribution paths for code, docs, design, and security research.

You\'re asking

? Where do I start?
? What are the coding standards?
? How do I write a plugin?
? How do I report a security issue?

Read the open source contributors guide →

Don\'t see your role?

Start with the architecture overview

The architecture page covers the engine, plugin contract, coordinator, and the three deployment modes. From there you can branch into any specific area.

Architecture overview Three modes Glossary