Summary

  • Tailscale’s current seat-based plans charge for purchased seats, including vacant ones; successive users can reuse a seat within the same billing period.
  • An invitation alone does not occupy a seat. First login or device authentication does, and an admitted user arriving at full capacity can increase the seat count automatically.
  • Monthly additions are prorated, while reductions affect the next cycle. A completed access-removal task is not evidence that the next purchase has been reduced.

An empty chair is remarkably easy to employ. It needs no onboarding, submits no expenses and can remain in a software budget long after its occupant has gone. Tailscale’s newer commercial plans give that chair a precise meaning: purchased capacity that another user can occupy. Until the buyer decides what capacity it needs, an empty place can remain a paid one.

The private-network service connects devices and governs their access through identities and rules. Its current pricing page lists Standard at $8 per user per month and Premium at $18. Under the seat model, purchased vacancies are billable. Customers can remove seats they no longer need. The difficult word in that otherwise straightforward instruction is “need”. The billing system cannot read the staffing plan.

Reuse is a useful part of the bargain. If one user vacates a seat and another occupies it within the same billing period, the customer pays for one seat rather than two. A succession of contractors can therefore use a pool of capacity without every name appearing during the month becoming another full seat. People who need to work concurrently present a different requirement from people who take turns.

That leaves two kinds of vacancy looking identical on an invoice. One is waiting for a scheduled replacement. The other is the remnant of a project that has ended. The first buys flexibility; the second may buy nothing more than the survival of an old quantity. Knowing which is which requires somebody inside the customer’s organisation to make a decision.

The exit has two desks

Even vacating the seat requires the right operation. Tailscale’s member-removal documentation says that deleting, suspending or deprovisioning a user through the identity provider vacates a seat. Deleting all of that user’s devices alone does not. An immaculate device list can still leave an identity occupying capacity.

Suspension blocks access while retaining devices; deletion removes the user’s devices. The choice should follow what the organisation needs to do with the identity. Recent inactivity is a different question again. An emergency specialist can be valuable precisely because ordinary weeks require no intervention. Judging that account entirely by recent traffic would confuse a quiet service with an unnecessary one.

After a seat is freed, the purchase still needs attention. The plan-management instructions allow an Owner, Admin or Billing admin to change the purchased total on the billing page. The total cannot fall below occupied seats. The roles permitted to remove users and those permitted to change purchased quantities do not coincide completely.

An IT offboarding ticket can consequently close while a commercial question remains unanswered. Is a replacement arriving? Is this spare capacity for an agreed rotation? Has the team permanently shrunk? Keeping the seat can be sensible. Reducing the next purchase can be sensible. Treating a successful access revocation as if it had answered all three questions is how a quantity escapes management.

Admission has purchasing power

The entrance works differently. An invitation or advance provisioning through SCIM does not by itself occupy a seat. First access to the admin console or first device authentication does; administrative approval is also required where that feature is enabled. When the existing seats are full, an admitted new user increases the count to accommodate them.

The person approving access can thus expand a purchase without visiting anything that resembles a purchase-order form. This lets a colleague get to work without waiting for the old capacity limit to be adjusted. It also gives admission a financial consequence. Showing the approver how much capacity remains makes the difference between allocating an existing place and adding another one visible at the useful moment.

For monthly plans, added seats are prorated over the remaining period. Reducing seats does not reduce the cost of the current cycle; it affects the next one. Removing a user and lowering the quantity immediately after an overage does not erase the charge already incurred. A fast exit is not a time machine for purchased access.

The timing of a handover therefore matters, but a perfectly non-overlapping handover is not automatically good management. A predecessor and successor may need to work together. Eliminating that overlap to save a seat would let the billing unit decide how knowledge is transferred. The sensible task is to understand the temporary capacity requirement and decide what remains after it ends.

Who now carries the idle time?

Tailscale once emphasised a different meter. Its April 2023 pricing announcement described self-service monthly billing retrospectively for active users who exchanged bytes, with the first three free. Actual use was part of the calculation. An unused identity did not automatically carry the same economic weight as an active one.

The 8 April 2026 announcement introduced business seat pricing as a way to make bills more predictable, alongside changes to plan features. Predictability has value. A customer can plan capacity and rotate people through it. The customer also has more reason to manage how much unused capacity it keeps. A question previously answered through measured activity becomes more dependent on a purchased-quantity decision.

Existing customers remain a separate cohort. Tailscale promised at least twelve months of unchanged pricing for existing paid plans, without forcing a migration during that period. Its changelog distinguishes new seat-based signups from legacy plans that continue monthly-active-user billing. Applying the vacancy argument to every customer would begin with the wrong contract.

For a particular team, the missing inputs are its actual purchased and occupied counts, authorised staffing overlaps and next renewal date; those determine the value of retaining a vacancy. The service sells the ability to put somebody else in the place. The buyer needs to know who that somebody might be, and when. An empty seat with a named future use is capacity planning. One whose only sponsor is last month’s invoice deserves another look.