Overview
PingMe at a glance
Privacy and storage
✓
End-to-end encryption active
The server stores encrypted payloads. Administrators can manage service metadata but cannot read private content.
User accounts
Create, rename, enable or disable invited users.
| User | Status | Last active | Chats | Messages | Devices | Server storage | Created | Actions |
|---|
Conversation metadata
Participants, encrypted item counts and storage only—no private content.
| Members | Type | Messages | Encrypted storage | Created |
|---|
Wishes & festival effects
Schedule celebrations on users' PingMe home screens.
Upcoming birthdays
Birthday details voluntarily added by users.
Schedule an effect
Scheduled and recent effects
Branding & visual effects
Change public PingMe labels and optional ambient animation without editing code.
System status
Live health information for your self-hosted service.
Email OTP / SMTP
Configure signup verification email. The password is encrypted at rest and never displayed again.
PingMe service architecture
Node.js application, PostgreSQL database and a self-hosted TURN relay run on your VPS. The administrator dashboard exposes operational metadata only.
Open public health endpoint ↗