CHANGELOG PRIVATE-BETA MILESTONES
Built with care.
Access still closed.
This is a product-progress log, not a release announcement. Pushify remains in private testing and the Android client is not publicly distributed.
NOWStability lap
IN PROGRESS
Testing before public release
The current build is going through another sustained private test. The focus is notification delivery, interactive answers, reconnection behavior, Android data preservation, and documentation accuracy.
- No public registration
- No APK or store download
- No public credentials
- Interfaces may still change
AUG2026
ACCESS CONTROL
Scoped access management
Pushify can manage users, exact channel grants, revocable device sessions, and short-lived Android enrollment without shared credentials.
AUG2026
LIBSIGNAL E2EE
Encrypted channels are ready for controlled use
Pushify now has device and prekey management, pairwise encrypted events and answers, generic Firebase wake-ups, protected Android crypto state, exact retry journals, and authenticated encrypted purge controls. Activation remains an explicit per-channel private-beta operation.
AUG2026
SENSITIVE LIFECYCLE
Messages can leave less behind
Sensitive notifications can use generic lock-screen text, absolute expiry, delete-after-open, remote channel purge, whole-app wipe, anti-resurrection tombstones, and optional two-person approval.
AUG2026
SAFE SELF-SERVICE
Private beta became supportable
Invited users can manage groups, devices, scoped tokens, blocks, content-minimal reports, support cases, metadata export, and closure requests. Operators gain auditable suspension, quarantine, and review controls. Public registration and recovery remain deliberately disabled.
AUG2026
CHANNEL MANAGEMENT
Stable channel identities
Private-beta administrators can create, describe, archive, restore, and inspect channels with immutable IDs and routing slugs. Android gains a cached selectable catalog while the server keeps a tested rollback bridge for existing automation.
AUG2026
PUBLISHING
One-line authenticated sends
A service can now post a plain-text title directly to /{channel}. The shorter route keeps the same bearer authentication, channel scopes, validation, persistence, delivery, deduplication, and limits as the complete JSON API.
AUG2026
PRIVATE-BETA HARDENING
Recovery and access boundaries
Scoped publisher and listener credentials, request limits, guarded backup and recovery, safer deployment verification, and clearer operational security boundaries were completed for the private environment.
BETACore loop
INTERACTION
Phone answers became durable
Pushify gained validated notification actions, small native forms, idempotent phone responses, response history, live response streams, and publisher-specific answer access.
BETAFoundation
SIGNALS
From a ping to an event bus
Title-only notifications expanded into channels, severity, structured metadata, deduplication, expiry, durable history, Server-Sent Events, a reliable Linux listener, and an Android inbox.
NEXT CHECKPOINT
Release only after the test.
Public onboarding, app distribution, and final installation documentation remain deliberately absent until testing is complete.
Review the current manual →