We Built the PTT System We Wished Existed

Communications for field teams and security-conscious organizations should not require a mandatory sign-up, a central dependency, or marketing fluff where encryption is concerned. FREEPTT exists to provide an auditable security model, genuinely private calls when you need them, zero friction to start, and full infrastructure ownership when stakes demand it.

Why These Choices

Why no account to get started?

Requiring sign-up before first use is friction that serves the vendor, not the user. Your device generates a cryptographic identity on first launch — enough to connect. An account is only relevant if you choose billing in a future tier.

Why Android?

Android Keystore provides hardware-backed identity on modern devices; we also support API 19+ so rugged hardware is not excluded by an arbitrary minimum OS.

Why open and encrypted channels?

Many operations rely on open broadcast-style channels. Forcing encryption everywhere would break those workflows. FREEPTT supports both open and encrypted channels so you can match mode to mission.

Why self-hosted?

Any cloud we operate is a component you must trust. The architecture allows operators who trust no one else to run a complete system — your keys, your server, your data.

Why open architecture?

Security through obscurity is not security. The design uses standard primitives (AES-256-GCM, RSA-OAEP, X.509 PKI, TLS) and published threat models.

Contact

Replace placeholder addresses with your production contacts.