The idea behind PushPort

Give useful messages a clear way through.

A product update. A reminder someone asked for. News that matters to a particular audience. PushPort is built for these everyday moments.

It started with a simple job.

Connect an application and send its users a notification. Then a few practical questions follow: who can receive it, which language should it use, and when should it go out?

PushPort brings those decisions together. An application, its audience and its messages belong in one clear workflow. Our aim is to make that workflow understandable for the person running the product, while keeping integration straightforward for its developer.

A useful notification starts with a reason to send it.

What shapes our decisions

Respect the recipient

Permission and subscription choices determine who can receive a message. Relevance starts with respecting those choices.

Make the result understandable

A request accepted by a push provider and a notification opened on a device are different events. We give them different names.

Build the next step carefully

Android comes first. iOS, Web and team workspaces are the next directions, with their current availability made explicit.

PushPort

Small enough to understand. Built to develop.

We are concentrating on the core: connecting Android applications, understanding subscriptions, composing localized messages and keeping schedules on the server. The shape of the product will grow from real use and real questions.

Features ↗