Pricing
Sites your team helps and logins they perform, per month. Add agents freely: headcount is your business, not our meter. Limits never turn into charges, and we email you at 80%, so the first you hear of one is never an invoice.
Pay for helping customers, not for seats
Counted per month: a customer site the first time it grants your team access, and a support login each time an agent clicks Log In.
Free
$0
Customer sites / month
1
Support logins / month
5
Includes
- The complete grant flow, end to end
- Secrets, uncapped
- Room to build and test your integration
Support
$49/mo$490/yrbilled annually
Customer sites / month
25
Support logins / month
150
Includes
- Log in straight from the Help Scout ticket
- Every login on the record for 90 days
- Secrets, uncapped
- Answers from the founder within a business day
Growth
$99/mo$990/yrbilled annually
Customer sites / month
100
Support logins / month
500
Includes
- Everything in Support
- More than one team on one account
- Slack notifications when access is granted
Scale
$249/mo$2,490/yrbilled annually
Customer sites / month
500
Support logins / month
2,000
Includes
- Everything in Growth
- Same-day priority support
Enterprise
From $499/mo
Customer sites / month
Custom
Support logins / month
Custom
Includes
- Everything in Scale
- An SLA, a DPA, and a security review call
- Caps sized to your fleet
A customer site counts once per billing month regardless of how often it grants your team access that month. An expired grant doesn’t free the slot until the month resets. A login counts each time a team member clicks Log In and a support session opens.
Every plan, including Free, comes with secrets at no extra charge and no cap: a password, an API key, or an FTP login travels as a vanishing link instead of sitting in the ticket, in either direction.
Annual billing gets you two months free on every paid plan. Audit log export, API access, single sign-on, and longer audit retention are on the roadmap for Growth and Scale; we don’t sell features before they ship.
Never a surprise bill
Hit the site limit and nothing gets billed.
A site counts against that cap the first time it grants your team access in a billing month; granting again later that month doesn’t add a second count, and an expired grant doesn’t free the slot early. The count resets with the month rather than with the grant. Add a 26th distinct site on Support in a given month and TrustedLogin prompts you to upgrade before it connects; there’s no surprise per-site charge.
Hit the login limit and nothing gets billed, either.
A login counts each time someone on your team clicks Log In and a session opens. Cross 80% of your monthly allowance and we email you. Cross 100% and the access grant is still stored, so nothing is lost, but the login itself pauses until you upgrade or the month resets.
Outgrown the free temporary-login plugin?
TrustedLogin is priced for support teams: two or more people logging into customer WordPress sites every week, at plugin and theme companies and at agencies running a client fleet.
If you’re the only person who ever logs into someone else’s WordPress site, and it happens once in a while, install the free Temporary Login Without Password plugin on that site and skip this page. It costs nothing.
Where the free plugin stops fitting a support team:
| Temporary Login Without Password (free) | TrustedLogin | |
|---|---|---|
| The credential | A link. Anyone holding it is logged in. | A login tied to your support agent’s own TrustedLogin account. |
| Setup | Install and configure on every customer site, one at a time. | Customer clicks one button inside your plugin. Nothing to configure per site. |
| Seeing all your sites | None. Each site is its own island. | One dashboard across every customer who has granted you access. |
| Audit trail | Whatever that plugin’s own log shows, per site. | Who logged in, which site, what role, when, across every customer site, kept 90 days. |
| Built for | One person doing a one-off fix on one site. | A support team logging into customer sites every week. |
The free plugin covers the one-off. Once logging into customer sites is part of the job, you’ve outgrown it.
Three support staff, 40 logins a month: the $49 plan
Three support staff and roughly 40 logins a month across 15 customer sites fit Support ($49/mo), comfortably inside its caps. Crossing 25 customer sites a month, or logging in many times a day? Growth gives you room to stop counting.
The fine print, answered
What happens when TrustedLogin is unreachable?
The Grant button embedded in your plugin has a fallback built in: if TrustedLogin’s service can’t be reached, the button routes your customer to your own support page instead of failing. Access already granted keeps working on its own schedule regardless. It’s a real WordPress account on the customer’s site with its own expiry, rather than a session that depends on TrustedLogin staying reachable.
What can your staff see?
TrustedLogin’s team can see the metadata: which site, which of your support agents requested access, what role, and when. We can’t see the decrypted login itself. The key that would open it lives on your own site, inside the Connector plugin, and never leaves it, so there’s nothing on our servers to read even if we wanted to.
What counts as a site?
A customer site that grants your team access during a billing month counts once against your cap, regardless of how often it grants access that month. If a grant from that site expires, the site still holds its place against the cap until the month resets. Expiry doesn’t free the slot early.
What counts as a login?
Each time someone on your team clicks Log In and a support session opens, that’s one login. It’s counted at the start of the session, not by how long the session runs or what’s done during it.
What happens when we hit a cap?
Nothing is deleted. Access grants are always stored, even past a cap. At 80% of either monthly allowance, customer sites or support logins, we email you and post to Slack. At 100% of the site cap a new customer site can’t connect, and at 100% of the login cap logins pause, until you upgrade or the month resets. The grant stays on record and is ready as soon as you do either.
Can I send a customer an API key safely?
Yes. Every plan includes secrets: paste in whatever needs to move, in either direction, set it to disappear after one read or a chosen expiry up to 30 days, and send the link instead of the value. TrustedLogin can’t open it either: the decryption key lives only in the link, never on any server.