Voxpery

Voxpery — Free Download. Communication platform

Voxpery is a free, open-source communication platform for communities that need real-time text chat, direct messages, voice channels, screen sharing, moderation tools, and account data controls. Use the hosted service at voxpery.com in your browser, or deploy the same stack on your own infrastructure with Docker. The hosted and self-hosted builds share one public AGPL codebase, so every feature can be inspected, reviewed, and audited.

★★★★★
5.0(2 ratings)
Download Voxpery (Official links)
File size: 10.2 MB
The latest version of Voxpery is: 0.3.0
Operating system: Windows, Mac OS, Linux
Languages: English
Developer: Emircan Agac
Price: $0.00 USD (Open Source (AGPL-3.0))
  • Voice channels with LiveKit SFU. Voxpery uses LiveKit as its selective forwarding unit to route audio between participants. The server adapts voice quality automatically based on network conditions. Users can join voice rooms, mute microphones, adjust input and output devices, and share their screen during a call. Screen sharing works alongside voice so communities can present, collaborate, or run live sessions without leaving the platform.
  • Text chat and direct messages. Servers organize conversations into channels, and channel management stays compact so navigation does not become cluttered. Direct messages sort by recent activity so active conversations stay at the top. Users can pin important conversations and switch between servers, channels, and DMs through a quick switcher. Message history loads as users scroll, and reactions let members respond with emoji without writing a reply.
  • Friends and presence system. Users can add friends, view their current status, and see mutual presence across the platform. Presence updates appear in the friends list and in direct message views. This gives communities a social layer without requiring a separate application. Friend requests, acceptances, and removals follow standard account-level controls.
  • Attachment uploads with signed access. Files uploaded to Voxpery use signed URLs instead of permanent public links. Access to an attachment is authorized through the server or DM viewer context. This means a file shared in a private server cannot be opened by someone outside that server, even if they obtain the URL. Attachment handling covers images, documents, and other common file types within message size limits.
  • Authentication with JWT and Argon2id. Account sessions use JSON Web Tokens for stateless authentication. Passwords are hashed with Argon2id, a memory-hard algorithm designed to resist brute-force and GPU-based attacks. Session cookies are marked httpOnly to reduce exposure to client-side scripts. Google OAuth is available as an alternative sign-in method, and it only confirms identity without exposing the user's Google password to Voxpery.
  • Google OAuth sign-in. Users can create and access accounts through Google OAuth. The OAuth flow returns only the account information needed to sign the user in. Voxpery does not receive or store the Google password. This option reduces friction for new members while keeping the authentication decision in the user's hands.
  • Moderation and trust and safety tools. Server owners and moderators can report users and messages, issue bans, and review an audit log of moderation actions. Moderation surfaces are built into the platform rather than bolted on. Reports, bans, and audit entries give community staff a record of what happened and who acted. These controls support communities that need basic governance without enterprise overhead.
  • Account data export and deletion. Users can export their account data and permanently delete their account from within the product. Export produces a copy of the data associated with the account. Deletion removes the account and its associated data according to the platform's retention rules. These controls exist by default, not as a paid add-on or a manual support request.
  • No behavioral analytics or ads. Voxpery does not include advertising or behavioral analytics. Optional operational counters use only allowlisted event codes, contain no message content or user identifiers, and are disabled by default for self-hosted deployments. This keeps operational visibility separate from user tracking. Communities that run their own instance can leave counters off entirely.
  • Self-hosting with Docker Compose. The full Voxpery stack can be deployed on infrastructure the operator controls. Docker Compose provides a one-command deployment path, and operations documentation covers the deployment and maintenance process. PostgreSQL and Redis back the stack, and the architecture supports horizontal scaling. Self-hosting gives communities full control over data storage, network exposure, and upgrade timing.
  • Tauri-based desktop client. The desktop client is built with Tauri, which uses the operating system's native webview instead of bundling a full browser runtime. This keeps runtime overhead low compared to Electron-based alternatives. The desktop app supports tray unread indicators and taskbar attention notifications, so users can see when messages arrive without keeping the main window open.
  • Quick switcher for navigation. A keyboard-driven quick switcher lets users jump between servers, channels, and direct messages. Instead of clicking through nested sidebars, users open the switcher and type part of a name. This reduces the number of steps needed to move around a large community. The switcher covers servers, channels, and DMs in one search surface.
  • Themes and custom appearance. Voxpery ships with ready-made themes and a simple custom color option. When a user selects a custom color, the system generates a contrast-safe palette from that color. This keeps text readable against backgrounds without requiring users to manually tune every shade. Appearance settings apply across the web and desktop clients.
  • Direct feedback through GitHub templates. Bug reports and feature requests open the matching GitHub issue template from either the web or desktop client. This connects user feedback to the public repository where the code lives. Reports and requests stay visible to the community and the maintainers, and the template structure captures the details needed to reproduce or evaluate a request.
  • PostgreSQL and Redis data layer. Voxpery stores persistent data in PostgreSQL and uses Redis for caching and real-time coordination. This combination supports message history, account data, server configuration, and session state. The architecture is designed to scale horizontally, so additional application instances can be added behind a load balancer as a community grows.

Voxpery has been developed by Emircan Agac, identified by the TR flag in the project's developer information. The platform is distributed under the AGPL license, and its public codebase covers the hosted web app, backend, and desktop clients. The project was created to give communities a smaller, inspectable, self-hostable alternative to mature commercial platforms. Discord and Slack still have larger ecosystems, polished mobile apps, app directories, and years of edge-case hardening. Mattermost remains more mature for enterprise compliance and large deployments.

Latest News

Latest Programs