Run the whole deployment from one console

Provision people, shape channels, set your retention and AI posture, and see every administrative action — including ours.

Try for free Contact us

The push.tt management console dashboard

See the security posture, not just the user count

The dashboard leads with what is actually true about your data right now: whether messages are end-to-end encrypted, whether anything is being retained, and whether any AI feature can read content.

Encryption, retention and AI transcription each shown as a live state with the consequence spelled out
Retention shows its window and scope, so "on" is never ambiguous
Nothing here is a badge that overstates — if a limitation exists, this is where it is stated

Security posture panel showing encryption, retention and AI transcription states

Provision people before they install anything

Create accounts centrally, put them in the right channels, and hand out credentials. The device key is generated on first sign-in and never leaves the handset.

Org members are provisioned by an admin rather than self-registering into your org
Channel membership and key grants are managed from the console
Active device sessions are listed and individually revocable

The console user list with roles and last-seen times

Compliance archives your organisation can read and we cannot

When retention is on, channel keys are also wrapped to an org keypair generated in your admin's browser. The Vault decrypts client-side with that key.

The escrow private key is sealed to the admin device — we never hold it
Turning retention on requires an explicit acknowledgement of what it changes
Members see an in-app notice in retained channels, because otherwise the word "delete" would be a lie

The Message Vault, listing archived channels available for compliance review

An audit trail that includes us

Every administrative action is recorded — provisioning, membership, key grants, settings changes, and each time somebody opens the archive.

Always on; not a paid add-on and not something an admin can quietly disable
Records the actor, the target and the change, not just that "settings were updated"
Retention purges are themselves audited, including how many messages were removed

The audit log listing administrative actions with actor and target

White-label it as your own

Two tiers: a full rebrand for resellers with their own app listings, and runtime org branding that retheme the app and console at sign-in inside any build.

See white-label options