Port began with a simple idea: people should have control over who can contact them, how much access they’re given, and how long that access lasts.

Little did we know how deep this rabbit hole would go.

To bring this simple idea to life, we had to completely rethink how digital connections are made — starting by removing persistent identifiers like phone numbers, emails, and usernames from the process. Along the way, we learned a lot — from basic mistakes like poor framework choices to more complex protocol errors. But we pushed through and built Port Messenger.

When we released Port, we were energized by the feedback we received. Sure, there were a few bugs, but the core innovation — how we connect — was sound. Many of you told us how Port empowered you to connect without the hesitation of sharing personal contact information.

We’ve always seen Port not just as a better way to connect, but as a step forward for privacy itself. By removing identifiers from how we connect and communicate, we’ve fundamentally removed the instruments of data collection. Naturally, we thought users who value privacy and security would be our earliest adopters.

However, the response from this community — one we deeply respect — was mixed. Many of you wanted proof of our privacy and security claims. And you were right to ask. Our word wasn’t enough (nor should it be). We received numerous requests to make our protocols and codebase public, so they could be audited and our claims verified.

This was always our intention.

Today, we’re publishing our codebase here and taking things one step further. We want Port to become a community effort — to help reimagine how we connect in the AI age.

Like any project, it won’t be perfect. We welcome your feedback, your contributions, and your scrutiny.

We’re looking forward to your support!