A community project · In development

Private conversations.
A public purpose.

Everyone deserves a little room to speak freely.

We’re building Hedylogos for private messages and calls, with a simple ambition: give people and communities more control over their communication.

Explore our purpose

Built toward open source and independent hosting.

The reason we’re here

Privacy should belong
to everyone.

Private communication helps people think, connect, and express themselves. Our goal is to make that freedom accessible, with technology that communities can inspect, improve, and eventually operate themselves.

We want trust to come from understandable design, public scrutiny, and meaningful choices about who runs the infrastructure.

01 / Privacy

Keep conversations
between people.

Hedylogos is being built for end-to-end encrypted messaging and calls, using established cryptographic building blocks.

02 / Openness

Make trust
something you can examine.

Our goal is a public source release with an explicit open-source license, protocol documentation, and clear security limitations.

03 / Independence

Give communities
more control.

We’re working toward documented self-hosting, so people can choose who operates their service and help shape its future.

Security, explained plainly

Trust needs
more than a promise.

We’ll describe the protections, the tradeoffs, and the work still ahead.

Established cryptography, carefully implemented

The current messaging design uses classical X3DH key agreement and Double Ratchet. Using established algorithms is a starting point; the implementation and its operation also need scrutiny. We do not claim post-quantum protection for the current production message protocol.

Encryption has real limits

End-to-end encryption protects conversation content in transit between participants. It does not make a compromised device safe, prevent a recipient from sharing a message, or hide every piece of metadata. Service operators can still observe information such as connection addresses, routing, timing, and message sizes.

Evidence before comparisons

We do not claim that Hedylogos is more secure than Signal or any other messenger. Meaningful comparisons need a defined threat model, current implementation evidence, and independent review. Internal testing is useful, but it is not a substitute for an independent security assessment.

Where we stand

A clear direction.
Work still to do.

Hedylogos is in development. We want the public story to reflect what is available today.

Source code
Currently private. An open-source release is planned.
Community hosting
A project goal. Public setup documentation will accompany a supported release.
Independent review
No independent external audit report is published here yet.
Public releases
Verified download and community links will appear here when available.

Freedom to speak.
Room to belong.

Back to the beginning