Border0

www.border0.com/Privileged access management (acquired by Tailscale)egress/border0JSON compare report an error provider JSON

Free allowance: No allowance could be read: https://www.border0.com/pricing returns a 404 body.
Verdict: fails: egressdata cannot be read back out at a usable rate or price
Cost: not statedsee Price below
Identity: emailno card, no phone
Binding limit: noneno named constraint binds
Evidence: documented3 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23

Free tier	No allowance could be read: https://www.border0.com/pricing returns a 404 body. The home page offers 'Start for free today' with no number and no plan table. unit none; metered on unstated
Price	unverified
Binding	none No meter is published to bind. The deciding fact is elsewhere: the socket families carry no UDP and the generic TCP socket is explicitly 'with authentication', so a public unauthenticated reader is not the shape of the product.
Identity	email a portal account at portal.border0.com/register; the company is now part of Tailscale
Egress	unverified: no plan or allowance page could be read; ingress: tcp free allowance: none published
Interface	cli connector deployed in the private network, clients authenticate through the portal
Tooling	Border0 connector and client, portal dashboard
Composes with	composes with nothing: it is a private access layer with authenticated sockets
Reliability	an acquired product with 'no short-term migrations planned' is a moving target; expect the control plane to fold into Tailscale
Notes	The 404 and the Tailscale sales link have three possible causes: the provider is dead, the pricing path moved, or the reader rewrote the link. The blog post and a law-firm deal note show the provider is dead only in part - the company was acquired on 2026-03-17 - but its docs still serve and the product still runs, so the record is fails-egress rather than dead. The reader did not rewrite the link: the origin returned a real 404 body with upstream_status 404.
Evidence note	documented The socket list and the acquisition are first-party and dated today. The free allowance is unverified because the pricing page is gone.

Evidence 3

date	source	what it proved
2026-10-23	docs.border0.com/docs/sockets	'The platform currently support various service types: HTTP(s) SSH Database: MySQL, Postgres TLS (Generic TCP ports with authentication)'
2026-10-23	www.border0.com/blogs/border0-is-joining-tailscale	'Today I'm excited to share that Border0 has been acquired by Tailscale', dated March 17, 2026, with 'no short-term migrations planned'
2026-10-23	tailscale.com/contact/sales-border0	the sales path now says 'talk to us about Tailscale PAM', which is where Border0's commercial page leads

More fields 6

wg path	none
wg detail	No WireGuard and no .conf. A socket is a platform-managed service: 'HTTP(s), SSH, Database: MySQL, Postgres, TLS (Generic TCP ports with authentication)'.
ingress	tcp
volume stated	unverified: no plan or allowance page could be read
bytes transit	yes
transit note	the connector carries the session to Border0's platform, which terminates it for an authenticated user

Unknown values 2

per object cap stated: the field does not apply to this kind of offer
retention stated: the field does not apply to this kind of offer