Skip to content
Questions, answered plainly

The things people ask
before they trust it.

No account, no store, no central server — those choices raise fair questions. Here are direct answers, including the parts that are genuinely limited.

Getting started

Getting started

What is ChatNyto, in one paragraph?

ChatNyto is an open-source, end-to-end encrypted messenger for people, AI agents and IoT devices. It runs over MQTT — a broker on your Wi-Fi, a cloud broker, or a LoRa radio — instead of a central messaging service. There is no ChatNyto account server, no phone number and no message relay operated by the project.

Do I need to create an account?

No. An account is a key pair generated on your device. You choose a display name and a password; the password protects the private keys. There is no registration, no email verification and no user database to sign up to.

Do I need a server?

You need an MQTT broker that the people you talk to can reach. That can be mosquitto on a laptop or Raspberry Pi, a broker on a VPS, a community broker, or the ESP32 broker in this repository. Two people on the same Wi-Fi can run one locally. There is no ChatNyto cloud you are required to use.

How do I find other people?

People connected to the same broker publish a signed presence advertisement. They appear in the People tab automatically. You can also share a contact QR code, which carries your public keys rather than a username.

Is there a mobile app store version?

Not currently. ChatNyto is distributed as source and, when maintainers publish them, build artifacts on GitHub Releases. The download page explains how to build each platform. A store listing would also impose policies that sit awkwardly with an app that is designed to run without a central service.

Networks & offline

Networks & offline

Does it really work without the internet?

Yes, as long as there is an MQTT broker you can reach. A broker on the same Wi-Fi, a laptop, or a LoRa box does not need an internet connection. Messages queue in an encrypted outbox and are delivered when a route returns. The app was designed around the assumption that the network is intermittent or absent.

Can I connect to several brokers at once?

Yes. Each network is a separate MQTT client with its own address, credentials, connection state and reconnect loop. Disconnecting one does not disturb the others. Your conversations appear in one list even when the people are on different networks.

What is this “add an address, not a configuration” feature?

If a server publishes https://your-host/.well-known/chatnyto.json, the app can fetch its broker URL, sign-in and STUN/TURN servers from that one address over HTTPS. The credential goes straight into the platform keystore. If the host publishes nothing — a LAN broker or a LoRa box — the address is used exactly as typed.

What happens to a message written while offline?

It is stored immediately, shown in the conversation and marked pending. The outbox is encrypted at rest. On the next broker connection or heartbeat it is published automatically. There is no manual retry step, and no message is silently dropped.

How does history catch up after being offline?

Clients hold history for each other. When a device reconnects it publishes a sync request with the timestamp of the newest message it has. Peers replay what came after it, with a randomised delay so they do not all answer at once. Receipts are batched, and duplicate messages are ignored.

What is the LoRa part?

The repository includes firmware for a Heltec V3 ESP32 board that runs an MQTT broker and a LoRa bridge. It lets MQTT traffic cross a radio link where there is no Wi-Fi or mobile data. The pipe is much narrower, so expect text and small payloads rather than video.

Security & privacy

Security & privacy

Can the broker read my messages?

No. Every chat payload is an AES-256-GCM envelope sealed with a channel key the broker never receives. Direct messages use an X25519 ECDH key derived by the two identities. Private groups use a passphrase-derived key. The broker sees topic names, public fingerprints, timing and ciphertext size.

Is it really end-to-end encrypted?

For direct messages and passphrase-protected groups, yes: the keys are derived on the devices and the broker has no key material. A public group with no passphrase is a different case — its key is derived from the topic name, which keeps the broker out but does not keep out anyone who knows the group name.

Where are my keys stored?

Private key seeds are generated on the device and sealed with AES-256-GCM under a key derived from your password (PBKDF2-HMAC-SHA256, 210,000 iterations). The password and broker credentials live in the platform keystore: Android Keystore, iOS Keychain, libsecret on Linux or DPAPI on Windows.

What if I forget my password?

Use the recovery code shown when the account was created. It is 120 random bits and unlocks the same seeds. If you have neither the password nor the recovery code, the account cannot be recovered. There is no server-side reset and no support desk with a copy.

Can I have more than one identity?

Yes. Several accounts can live on one device, each with its own keys, chats, contacts, calls and encrypted storage. Switching identities drops the previous account’s in-memory state as well as pointing at different keys.

Has the code been audited?

There has not been an independent security audit. The source is available under AGPL-3.0, the architecture guide documents the design, and the security page lists the known limits. Treat it as a serious engineering project, not as a certified product.

Does the app contain telemetry or analytics?

No. ChatNyto has no analytics SDK, no advertising SDK and no telemetry endpoint. The project operates no messaging service that could collect usage data. Your broker operator may see connection metadata, which is inherent to running any broker.

How do I report a vulnerability?

Use the private security advisory form on the GitHub repository rather than a public issue. Include reproduction steps and enough detail to assess impact. The security page links to the form.

Calls

Calls

How do calls work without a central service?

Signalling — offer, answer, ICE candidates, decline, end — travels inside the pair’s encrypted chat. Media then tries a direct WebRTC path, uses the network’s published STUN/TURN servers when needed, and on Android and iOS can fall back to an encrypted ADPCM relay over MQTT.

Can I make a call with no internet at all?

If both devices are on the same Wi-Fi or the LoRa box access point, a direct peer-to-peer call can work. The MQTT relay exists precisely for the case where no direct route is possible. On desktop, the relay path is not implemented, so a desktop call needs a direct or TURN route.

How many people can join a group call?

Up to six. Each participant sends media to the others in a mesh, so the uplink cost grows with the group size. That is why the limit is six rather than an arbitrary larger number.

Does the phone ring when the app is closed?

On Android, a foreground service can keep a listening isolate alive and raise a full-screen incoming-call notification. The service isolate does not answer the call or store history; it rings, and the app opens to the real call screen. Manufacturer battery optimisation can still interfere, which is why the settings page offers a battery exemption shortcut.

Are calls recorded?

No. ChatNyto does not record calls. The relay carries live ADPCM frames and does not write them to history.

AI agents

AI agents

Which AI providers are supported?

Anthropic, OpenAI, Google Gemini, Mistral, Groq, DeepSeek, xAI, OpenRouter, Ollama, LM Studio and any OpenAI-compatible endpoint. The app speaks three protocol shapes: OpenAI-compatible chat completions, Anthropic Messages and Gemini generateContent.

Where does my API key go?

Into the platform keystore, not the app’s preferences. ChatNyto calls the provider directly from the device; there is no ChatNyto proxy and no shared project key. Requests go to the provider you configured, under your account.

Can I use a local model?

Yes. Point an agent at Ollama, LM Studio or another OpenAI-compatible server on your network. In that configuration the model conversation stays inside the LAN — which is the same instinct as the rest of the app.

What is MCP?

Model Context Protocol. It lets an agent call tools exposed by a server — read a file, query a database, drive a home device. ChatNyto supports MCP servers over HTTP or SSE and lets you enable specific tools per agent.

Devices & IoT

Devices & IoT

Which smart-home devices work?

Anything that speaks MQTT. You define a device, give it a room, and add controls: a switch with on/off payloads, a dial with a numeric range, a button with a press payload, or a reading that subscribes to a topic. There is no vendor-specific hub requirement.

Which televisions can I control?

Roku and Roku-based streaming sticks (ECP on port 8060), Samsung Tizen televisions from 2016 onward (WebSocket on 8002), LG webOS televisions from 2012 onward (WebSocket on 3000), and Android TV / Google TV / Nvidia Shield over network adb (port 5555). Samsung and LG will ask you to allow the phone once.

What is the adb bridge for?

Debugging and controlling Android hardware over the network. It can reach a device directly, through a computer’s adb server, or on the phone itself with Shizuku or Termux. adbd authenticates with an RSA-2048 challenge, so the app carries a key for that purpose.

Do devices need cloud accounts?

MQTT devices do not. They talk to your broker. Televisions use their manufacturer’s local-network protocol, so no cloud account is involved in the remote, although the television itself may have its own online features.

Platforms & builds

Platforms & builds

Which platforms are supported?

Android, iOS, Linux, macOS and Windows. One Flutter codebase builds natively for each. The mobile builds carry the deepest feature set, including the background service and the MQTT call relay. The desktop apps are full chat, call and AI clients.

Why is there no web version?

A web target exists in the repository, but it is not a supported distribution target and does not have feature parity. The full experience depends on platform services — keystore, background execution, raw audio — that a browser does not provide in the same way.

What do I need to build it?

Flutter stable with Dart 3.3.4 or newer, plus the toolchain for your target: Android SDK and JDK 17, Xcode on macOS/iOS, GTK 3 and ninja/clang on Linux, or Visual Studio 2022 with C++ on Windows. The app was developed and tested with Flutter 3.47.x.

Are there prebuilt binaries?

Only if the GitHub Releases page lists them. The project does not promise installers for every platform or every version. Building from source is the supported path and the only way to know exactly what you are running.

How do I update?

Pull the repository and rebuild, or install a newer artifact from Releases if one exists. There is no auto-updater and no vendor push channel. Your account keys and encrypted history stay on the device across an app update unless you uninstall or clear its data.

Can I contribute?

Yes. The repository is on GitHub under AGPL-3.0. Issues and discussions are the place to start; security reports should go through the private advisory form. Changes that affect the protocol or the crypto deserve a design discussion first.

What license does it use?

GNU Affero General Public License v3.0. You can use, study, modify and redistribute it. If you run a modified version as a network service, the AGPL requires you to offer the corresponding source to its users.

Still unsure?

Read the source, or ask a person.

The architecture guide explains how a message, a call and an identity actually move. If something is still unclear, the issue tracker and discussions are public.