Built by the company that had to trust it first
TrustedLogin came out of GravityKit’s own support team, and GravityKit still runs its support through it every day.
It started as GravityKit’s fix for its own support bottleneck
Zack Katz founded GravityKit, a WordPress plugin business now in its second decade, built on GravityView and its add-ons. Running support for GravityView, the recurring bottleneck was getting access to look at the bugs. Every ticket that needed a site login added a round of email, a wait, and often a password left sitting in the thread afterward. TrustedLogin started as the fix for that, inside GravityKit, before it was a product anyone else could buy.
If it broke, GravityKit’s support team would feel it first
GravityKit is a profitable, decade-old WordPress business whose runway is its own revenue. It runs its own support team through TrustedLogin today: the same one-click access, the same dashboard, the same expiry rules you’d get. When a GravityKit customer asks for help, someone is inside the site within minutes, and there is a record that they were there. If TrustedLogin broke in a way that mattered, GravityKit’s own support team would feel it before any customer did.
Small team, on purpose
TrustedLogin is run by a small team. That means fewer people who could mishandle a customer’s access request, a shorter chain between a bug report and a fix, and nobody routing your support data through a department that’s never touched the product. Every support reply comes from the founder, within one business day.
Three things that hold if TrustedLogin disappears
Each one holds regardless of team size, and regardless of whether TrustedLogin as a company is still around in five years:
The SDK, the code that runs inside your plugin, is open source: read it at github.com/trustedlogin/client. The Connector is GPL-licensed and its full source ships through WordPress.org.
The Connector has been live on WordPress.org since September 2024, with a public listing, public reviews, and a public version history.
Every time a customer grants access, their own site creates a real WordPress account. The customer, or their host, can revoke it directly in wp-admin, with or without TrustedLogin’s service being reachable.