OPEN SOURCE ↗

Your application.
Shared rules.
Verifiable results.

Yano X is a shared application platform for Java. Build applications that organizations run together, with shared records, approval workflows, and integrations — and results participants can independently verify.

JAVA 25 / JVM PLUGINS / CARDANO ANCHORING

EXPLORE A SHARED APPLICATIONILLUSTRATION

Record what happened.

Keep a shared, verifiable history of application events.

SIGNED APPLICATION EVENTorder.created #A-100
Record
Order A-100 was created
Claim
This event appears in the agreed history
Member A9f3c…a17bsame state root
Member B9f3c…a17bsame state root
Member C9f3c…a17bsame state root
MEMBER-CERTIFIED RESULTOne event. One agreed history.

The configured member threshold certifies the result. A proof can establish that this event was recorded.

Example data · optional Cardano anchoring

ONE FOUNDATION. YOUR EXTENSIONS.Yano provides the foundation.
Yano X makes it yours.

Powered by Yano, with optional commitments published to Cardano. Yano coordinates member agreement and provides verifiable records. Yano X adds your application rules and integrations as JVM plugins. Connect over HTTP from any language.

Understand the relationship ↗
WHY SHARED APPLICATIONS?

Less reconciliation.
More shared certainty.

When several organizations need to agree on what happened, a shared API alone is not the whole answer.

01 / AGREE

The same rules.
On every member.

Members independently execute ordered commands and certify the resulting state. Agreement follows the configured member threshold.

Understand finality ↗
02 / VERIFY

Evidence you
can check.

Verify supported state claims against a certified root. Optionally anchor commitments on Cardano for an independently observable L1 record.

Explore proofs ↗
03 / EXTEND

Your domain.
Without a host fork.

Choose existing capabilities, compose workflows, or build Java plugins. Keep application rules separate from the infrastructure that coordinates members.

Meet the plugin framework ↗
WHAT WILL YOU BUILD?

Start with the outcome.

Explore a path. You can learn the underlying machinery as you go.

01 / Registry · Document trail

One record. Every member agrees.

Track ownership, documents, or attestations across organizations. Start with a registry or document trail, then retrieve a proof of the recorded state.

Build a registry ↗
  1. 01Submit a signed update
  2. 02Apply the same rules on every member
  3. 03Verify a record against the certified root
02 / Role approvals · Composition

Make the rules part of the record.

Give people business roles — issuer, reviewer, auditor — separate from the members running the software. Require approval from the right roles and organizations before an action proceeds.

Explore role approvals ↗
  1. 01Define participants and roles
  2. 02Collect the required approvals
  3. 03Record the authorized transition
03 / Generic observations · Signed source evidence

Bring outside evidence into shared decisions.

Receive a signed delivery report or another supported external input. Members check the evidence against agreed source and acceptance rules before your application uses the certified result. A source report is evidence of its claim, not proof of physical delivery.

Understand observations ↗
  1. 01Request an external observation
  2. 02Check source evidence and acceptance rules
  3. 03Apply the certified result
04 / Effects · Connectors

Connect decisions to the real world.

Authorize a webhook, publication, or payment from a finalized transition. Executors handle network work outside consensus; results return as sequenced messages.

Connect a webhook ↗
  1. 01Commit an effect request
  2. 02Execute outside consensus
  3. 03Incorporate the reported result
A SMALL FIRST STEP

See it work.
Then make it yours.

Start on a private local devnet. No public-network wallet or test ADA needed.

  1. 01

    Run the local demo

    Download the showcase archive, check prerequisites, and start three members.

    Follow the local quickstart →
  2. 02

    Submit. Inspect. Verify.

    Send an event, compare member state, and understand what a proof establishes.

    Continue with guided tutorials →
  3. 03

    Choose your own rules

    Pick a recipe, configure your application, then extend only where you need to.

    Choose a recipe →
LOCAL DEMObash

In yano-x-jvm-<version>/examples/showcase

# Check Java 25 and local prerequisites
./showcase.sh doctor --profile light

# Start a private three-member devnet
./showcase.sh quickstart \
  --profile light --nodes 3 --instance first-demo

# Check agreement, then open the console
./showcase.sh verify all --instance first-demo
./showcase.sh ui --instance first-demo

# Keep your data for next time
./showcase.sh stop --instance first-demo
Choose the right download ↗
WHEN YOU ARE READY

Room to go deeper.

Keep learning at your pace. The reference is here when you need it.

13 recipes44 capabilitiesExplore the generated catalog →

Yano X is pre-release. Begin with local development and validate security, operations, and domain behavior before production use. Documentation follows this checkout; use the identities and manifests shipped with your downloaded release.