The same rules.
On every member.
Members independently execute ordered commands and certify the resulting state. Agreement follows the configured member threshold.
Understand finality ↗ OPEN SOURCE ↗ Your application.
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.
EXPLORE A SHARED APPLICATIONILLUSTRATION
Record what happened.
Keep a shared, verifiable history of application events.
APPLICATION EVENT
order.created #A-100- Record
- Order A-100 was created
- Claim
- This event appears in the agreed history
Member A
9f3c…a17bsame state rootMember B
9f3c…a17bsame state rootMember C
9f3c…a17bsame state rootMEMBER-CERTIFIED RESULTOne event. One agreed history.
Your application sends the event to one member, which signs it with its member key. Acceptance does not yet mean members have agreed on the result.
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.
Less reconciliation.
More shared certainty.
When several organizations need to agree on what happened, a shared API alone is not the whole answer.
The same rules.
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 ↗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 ↗- 01Submit an update to any member
- 02Apply the same rules on every member
- 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 ↗- 01Define participants and roles
- 02Collect the required approvals
- 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 ↗- 01Request an external observation
- 02Check source evidence and acceptance rules
- 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 ↗- 01Commit an effect request
- 02Execute outside consensus
- 03Incorporate the reported result
A SMALL FIRST STEPSee it work.
See it work.
Then make it yours.
Start on a private local devnet. No public-network wallet or test ADA needed.
- 01
Run the local demo
Download the Yano X JVM ZIP, check prerequisites, and start three members.
Follow the local quickstart → - 02
Submit. Inspect. Verify.
Send an event, compare member state, and understand what a proof establishes.
Continue with guided tutorials → - 03
Choose your own rules
Pick a recipe, configure your application, then extend only where you need to.
Choose a recipe →
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 --instance first-demo
./showcase.sh ui --instance first-demo
# Keep your data for next time
./showcase.sh stop --instance first-demoLEARN BY EXPLORING
Step through it.
Interactive explainers: play a round, switch to your terminal's view, and see what happens when something breaks. Start with What is an app ledger?
Life of a messageFrom an HTTP call to a final, provable result, with a leader that goes offline→Your first finalized eventEach command of the first tutorial, and what happens when a member is down→Nodes, chains, and portsWhich ports each way of running Yano X uses→Where each setting livesBlueprint, shared consensus values, node files, and secrets→The REST API by accessEvery endpoint group, and which key it needs→
WHEN YOU ARE READY
Room to go deeper.
Keep learning at your pace. The reference is here when you need it.
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.