Skip to content
Notifications
Clear all

Has anyone else's billing jumped after adding a few guests?

2 Posts
2 Users
0 Reactions
2 Views
(@observability_guy_99)
Eminent Member
Joined: 2 months ago
Posts: 11
Topic starter   [#1064]

Hey folks, hoping to get some perspective here. We've been using 1Password Business for about a year, primarily for the engineering team's shared secrets and service credentials. It's been solid for thatβ€”easy to integrate with our CI/CD pipelines.

Last month, we needed to share a specific vault with a few external contractors (non-engineers) for a project. We added them as "Guests" as recommended. It was only 5 people. Our next bill, however, had a noticeable jumpβ€”more than I expected for just 5 guest accounts.

I was under the impression guest pricing was different/billed separately, but looking at our invoice, it seems they're being counted similarly to full users? Or maybe there's a minimum charge tier we hit? The pricing page is a bit vague on the exact math once you mix in guests.

Has anyone else run into this? I'm wondering if our setup is wrong. In observability, we're always tracing cost spikes back to a root cause 😅. Trying to figure out if this is the expected behavior or if I need to look at a different permission model (like maybe using a "Share" link instead?).

Observe all things.


DataDogDodger


   
Quote
(@martech_maverick)
Trusted Member
Joined: 1 month ago
Posts: 38
 

Yeah, the pricing model for guests in several of these platforms is a classic bait-and-switch, dressed up as a feature. You think you're getting a lightweight, cost-effective way to grant limited access, but the billing engine sees another seat. I'd bet you hit a new pricing tier, where your total count of members (full users plus guests) pushed you from, say, a 20-49 user bracket into a 50-99 bracket. The per-seat cost often drops slightly in higher tiers, but the aggregate jump is still a shock.

You mentioned the vague pricing page, which is intentional. They want you to focus on the utility, not the unit economics. The "Share link" option might have its own limitations on concurrent access or expiry, but it's worth testing as a cost-control measure for truly temporary, external needs. The real question is whether those five guests are actively using the vault daily or if it was a one-time grant. If it's the latter, you're paying for shelfware.

Always trace the cost spike, like you said. Demand an itemized invoice from support that breaks out full user vs. guest charges and clearly shows the tier you're being billed at. If they can't provide that, you've found your root cause: opaque billing designed to obscure incremental costs.


Attribution is a lie, but we need the lie.


   
ReplyQuote