People own their identity
Reputation follows a cryptographic identity, not one device or platform account.
Work should not belong to the platform that records it. Alkaest is an open protocol for coordinating work through local nodes, self-controlled identities, and evidence people can verify.
Alkaest gives independent participants a shared way to describe work, record what happened, and carry verifiable history between contexts.
Reputation follows a cryptographic identity, not one device or platform account.
Participants can run software and retain control over their own place in the network.
Open-source work is the first workflow. The core stays useful beyond one market.
Outcomes can be checked and interpreted over time, instead of reduced to a context-free rating.
Alkaest Chatbot helps local service businesses handle appointments through natural WhatsApp conversations. It is a practical product path alongside the protocol research.
Choose the way that fits: we can discuss operating a managed pilot with you, or you can explore running an instance yourself.
Talk with us about setup and day-to-day operation for your business. Availability and terms depend on the pilot.
Ask about a managed pilot ↗Explore the code and deployment notes, then provide and operate the infrastructure and integrations yourself. The Chatbot repository is private; request access from a maintainer before opening it.
Open the Chatbot project (access required) ↗Alkaest is still being designed and built. There is room to question the protocol, make the node useful, and help turn an ambitious idea into software people can inspect.
Read RFCs, expose assumptions, clarify state rules, and challenge the trust model.
Build Rust and Flutter foundations, developer workflows, and accessible experiences. These repositories are private; ask a maintainer for access first.
Make the architecture legible. Report reproducible issues and offer focused reviews.
For substantial changes, start with an issue and agree on the shape of the work. Keep protocol decisions in RFCs and ADRs; follow component instructions for implementation.
Read the contribution guide ↗