Teleport Is Still Legally Named Gravitational. Every Rename Since Tells You Where The Money Moved.

July 16, 2026

Editorial note. The publication date shown above may be in the future. That is intentional. Posts on this site are scheduled against an editorial calendar that aligns with product releases, book launches, and platform-signal timing; the datePublished reflects the date the post is slated to go public, which is also the date indexers and syndication partners should treat as canonical. If you are reading this before that date you were early — welcome.

That isn't a stale copyright string somebody forgot to update. Open Teleport's Terms of Service, last revised May 8, 2026, and the first line of the agreement is this:

"GRAVITATIONAL, INC. ("TELEPORT") AND CUSTOMER SHALL EACH INDIVIDUALLY BE REFERRED TO AS A 'PARTY'..."

Gravitational, Inc. is the company. Teleport is a name it does business under. If you sign a Teleport contract in 2026, your counterparty is Gravitational. The GitHub org is still github.com/gravitational. The old domain still 301s to the new one.

I went looking for the story behind that, because I'd written about what Teleport actually sells and kept tripping over the older name. What I found is more useful than trivia. This company has renamed itself three times in six years, and every single rename is a decision you can read: a product they killed, a market they chased, and one word they slipped in without telling anyone.

2015: the planet is one computer

Gravitational was founded in 2015 by Ev Kontsevoy, Sasha Klizhentas, and Taylor Wakefield. It went through Y Combinator. By late 2019 it was still small: TechCrunch put it at 20 employees and roughly 100 paying customers.

The founding idea was bigger than the company. Kontsevoy laid it out in the post that eventually announced the rename, and it's worth reading because almost nobody writes a mission statement this legible:

"We started Gravitational because we found this mess with environments unpleasant. We liked the simplicity of giving instructions to a computer better. Can we have that in the modern era of cloud computing? We believe the answer is yes, but we have to let go of environments and move into environment-free computing, i.e. fully embrace the promise of the cloud and treat the entire planet as a single, multi-tenant computer."

Treat the planet as one computer. Fine. A computer needs two things:

"What we built at Gravitational is Gravity and Teleport. The Gravity project was meant to be the 'runtime' for this computer, while the goal of Teleport was to provide an easy way to access it."

So: Gravity was the operating system, Teleport was the way in. Two products, one thesis. The name Gravitational covered both, because neither one was the point. The point was the planet-computer.

That's the part people miss. Gravitational wasn't a bad name for an access company. It was a fine name for a company that wasn't an access company yet.

And the money followed Gravity, not Teleport. The $25M Series A that Kleiner Perkins led in November 2019 was reported as a round to ease cloud deployment with Kubernetes. That's the Gravity thesis. They raised on the runtime.

Twelve months later they renamed themselves after the other product.

November 2020: the rename

On November 19, 2020, Kontsevoy published "Gravitational is Teleport." Here is the actual reason, in his words, and I'd frame this on a wall in any product org:

"What we have noticed is that Gravity's primary use case became deploying SaaS applications into restricted environments, i.e. Gravity today enables SaaS companies to convert their offerings into downloadable software. This is fantastic, but not exactly as grand as we have imagined. So it really is a no-brainer. This is why we are renaming ourselves Teleport."

Read that again, because it is an unusually honest sentence for a press cycle. Gravity worked. Customers used it. It made money. And it had quietly become a narrower thing than the founders wanted: a way to ship SaaS as an on-prem download. "Fantastic, but not exactly as grand as we have imagined."

Meanwhile the side product, the way in, was eating the world. So the company renamed itself after its best-selling thing and pointed everything at that.

The press release the same day framed it more gently, as you'd expect:

"The decision to formally change our name to Teleport supports the natural evolution that our company has followed from the point it was founded."

That release doesn't mention Gravity once. The blog post at least said goodbye.

What "actively supported" turned out to mean

The rename post included a promise:

"Gravity will still be actively supported, but we have learned from successful companies that focus is what creates great companies and today we are focused on Teleport."

Here's what happened to Gravity after that sentence, from the repo itself:

Last release: 9.0.0-beta.5, September 2021, about ten months after the promise
Last code push: June 28, 2023
The README's own banner: "Gravity was archived 2023-07-01"
GitHub API today: archived: true, Apache-2.0, 1,080 stars

It was never sold and never spun out. It stayed open source and was left to cool, then switched off. The README now tells you to go use a certified Kubernetes distribution instead.

I'm not going to pretend this is a scandal. Killing a product that pays the bills to chase one that pays more is often the right call, and it's obviously the call that worked here: the company was worth $1.1 billion eighteen months later. But "actively supported" and "archived within three years" are different promises, and if you're evaluating any vendor's commitment to a second product line, this is the shape that commitment usually has. The rename was the announcement. Everyone just read it as branding.

If your company runs on somebody's product number two, the rename is your notice.

The renames didn't stop

This is the part I didn't expect. Gravitational to Teleport was the loud one. There have been two more since, and both are quieter and more interesting.

February 25, 2025. The product line got renamed from the "Access" framing to the "Identity" framing. The Teleport Access Platform became the Teleport Infrastructure Identity Platform. Access became Zero Trust Access, and Identity Governance, and Identity Security. Same company, same certificates, different noun. "Access" is a feature you buy from a vendor. "Identity" is a budget line with a CISO attached to it. That rename moved the product from one purchasing conversation to a much larger one.

Somewhere between December 9, 2025 and January 4, 2026. This one was never announced at all, and I only found it by diffing archived copies of the homepage. The boilerplate sentence at the bottom of every page used to read:

"Teleport is the Infrastructure Identity Company..."

And then it read:

"Teleport is the AI Infrastructure Identity Company..."

Identical sentence. One word inserted. No blog post, no press release, nothing I could find announcing it. Two Wayback snapshots four weeks apart, and a company repositioned itself into the biggest capital market on earth with a single adjective.

I don't think that's cynical, exactly. Teleport has genuinely built for this: MCP servers are a first-class protected resource type now, they ship cryptographic identity for AI agents, and KuppingerCole's July 2026 report specifically credits their "purpose-built AI agent governance for infrastructure access." The product work is real. But the sequence is worth noticing. The word landed on the website before the announcement, because there was no announcement. It's the same instinct as 2020: watch where the demand is, then rename toward it.

Three renames, one habit. This company renames itself at its customers, and it does it fast.

The rename that reached backwards

Here's the detail that made me sit up.

In May 2022, Teleport announced its $110M Series C at a $1.1B valuation. The press release quoted a DoorDash engineer:

"Speed is key to our business. But so is security. The Teleport Access Plane allows our engineers to securely access the infrastructure they need to do their jobs without getting in the way of productivity. Everybody wins."

Luke Christopherson, Software Engineer at DoorDash

Go to goteleport.com today and that same quote is still on the homepage, still in quotation marks, still attributed to Luke Christopherson:

"Speed is key to our business. But so is security. The Teleport Access Platform allows our engineers to securely access the infrastructure they need to do their jobs without getting in the way of productivity. Everybody wins."

Plane became Platform. The product got renamed, so the customer's sentence got renamed with it.

It's a one-word change, it's four years old, and no reasonable person thinks Christopherson objects to it. But it's a quotation. Somebody edited a named human's words inside quotation marks to keep them consistent with a product rename, and left the attribution intact. That's the rename reflex reaching backwards through time to tidy up a 2022 sentence. Once you know the company renames itself constantly, you start reading its quotation marks differently.

So why do companies actually use it?

DoorDash is the logo everyone points at, including me at the top of this post. So let me be precise about what that logo is worth, because it's less than it looks.

There is no DoorDash case study. Teleport publishes eighteen case studies and DoorDash isn't one of them. What exists is a logo in the homepage strip, one testimonial from that 2022 press release, and a talk Christopherson gave at Teleport Connect 2022. That's it. Nothing states what DoorDash's problem was, what they replaced, how many engineers or servers are involved, or what improved. Every trace of the relationship dates to 2022. The TechCrunch and SiliconANGLE stories that name DoorDash as a customer both ran the same day as the press release, which makes them the press release.

A logo tells you a company signed a contract at some point. It doesn't tell you why, or whether they still have it.

The eighteen actual case studies are much better evidence, and reading them all in one sitting is clarifying, because the real reasons are nothing like the vision:

TigerGraph: private key access was managed by one engineer. One. The company scaled and that person became the bottleneck.
Turo: their existing database access vendor, Cyral, got acquired and shut down. They needed a replacement, fast. Victor Mora, VP of Engineering: "Everything was up and running in two hours."
dbt Labs: shared passwords and a ten-step VPN process, during 10x headcount growth. Frank Wang, Staff Security Engineer: "We lacked a centralized solution for handling access and security."
Rush Street Interactive: Olga Daminova, Infrastructure Security Engineer: "We were spending too much time on trivial work. Managing SSH keys and firewall rules wasn't scalable."
thredUP: a homegrown kubeconfig and aws-iam-authenticator tool the SRE team couldn't scale, plus a SOC 2 audit.
Gladly: Charles Soesanto, Head of Security: "With auditors or some of our customers, when they ask about the efficacy of our security process, they ask for evidence."
PPI Financial Services: German and EU regulation. C5, KRITIS, DORA.
Exness: permanent Kubernetes tokens sitting in GitLab CI/CD.
GoTo: Pradithya Aria Pura, Principal Software Engineer: "all our Kubernetes clusters are private, meaning they can't be accessed publicly, both for the data plane and control plane. We needed a mechanism to..." reach them.
IBM Instana: Hunter Madison, Cloud Architect, on replacing VPNs, certificates, and legacy privileged access tooling.
Buyers Edge Platform: John Wieder, Senior Systems Administrator: "We didn't want to manually manage config information for our many dozens of databases."
Flywheel: onboarding went from about three weeks to about twenty minutes, which is the most specific number in the entire set.
ECMWF: a weather supercomputing centre replacing its own in-house ecAccess system.

Notice what is not on that list. Nobody says "we adopted zero trust." Nobody mentions the planet as a single multi-tenant computer. Nobody bought the vision.

Every one of them bought a fix for one specific broken thing, and the broken things fall into four buckets:

A person became the bottleneck. One engineer holds the keys. They go on holiday and the company can't deploy.
An auditor asked for evidence. SOC 2, FedRAMP, DORA, C5, KRITIS. Somebody needed a recording and a log, and "we trust our engineers" is not an artifact you can hand an auditor.
Growth broke the manual process. The ten-step VPN was fine at 40 people. At 400 it's a full-time job nobody wants.
Something died. Turo's vendor got acquired out from under them.

That's the honest answer to "why do companies use Teleport." Not because of the certificate model, elegant as it is. Because a specific thing broke on a specific Tuesday, and this fixed it.

Which is also the tell for whether you need it. If you can't name your broken thing from that list, you're shopping for a vision, and visions are the most expensive thing in enterprise software.

What to take from a rename

Three things I'd genuinely use, whether or not Teleport ever touches your infrastructure:

Read the entity name, not the brand. Gravitational, Inc. is who's on your contract. This is not unusual and it's not sinister, but the legal name is a fact about a company and the brand is a decision about you. When they differ, the older one usually tells you what the company was built to be.

A rename is a strategy diff. Gravitational to Teleport meant Gravity is over, and Gravity was archived thirty-two months later. Access to Identity meant we want the CISO's budget, not the platform team's. Adding "AI" meant exactly what you think it meant. None of these were dishonest. All of them were announcements, and only one came with a blog post.

Ask for the case study, not the logo. DoorDash is a logo. TigerGraph is a case study with a named engineer, a stated problem, and a thing that got replaced. When a vendor shows you a wall of logos, the interesting question is which of those logos has a story attached, and if the answer is "the big famous one doesn't," you've learned something about both the vendor and the logo.

The best thing I can say about this company is that when they killed Gravity, the CEO wrote down the real reason and published it under his own name. "Fantastic, but not exactly as grand as we have imagined" is the most honest sentence in this entire post, and it's theirs.

Fact-check notes and sources

The legal entity: Teleport's Terms of Service, last updated May 8, 2026, opens "GRAVITATIONAL, INC. ("TELEPORT") AND CUSTOMER SHALL EACH INDIVIDUALLY BE REFERRED TO AS A 'PARTY'". The footer on goteleport.com reads "© 2026 Gravitational Inc.; all rights reserved." The GitHub organisation remains github.com/gravitational, and gravitational.com returns an HTTP 301 to goteleport.com. I verified the redirect myself.
The rename and the reasons: Ev Kontsevoy, "Gravitational is Teleport", November 19, 2020. All Kontsevoy quotes in this post ("treat the entire planet as a single, multi-tenant computer", the Gravity runtime framing, "not exactly as grand as we have imagined", and "Gravity will still be actively supported") are verbatim from that post. The same-day GlobeNewswire release carries the "natural evolution" quote and does not mention Gravity.
Gravity's fate: the Gravity README states "Gravity was archived 2023-07-01". The GitHub API record returns archived: true, Apache-2.0, 1,080 stars, last push 2023-06-28. Last release was 9.0.0-beta.5 in September 2021. It was never sold or spun out.
Founding and funding: founded 2015 by Ev Kontsevoy, Sasha Klizhentas, and Taylor Wakefield (per Kontsevoy's own Series C post), Y Combinator alum. TechCrunch, November 20, 2019 reported the $25M Series A led by Kleiner Perkins, 20 employees, ~100 paying customers, and framed the round around Kubernetes deployment. Series B was $30M in August 2021. Series C was $110M at a $1.1B valuation, May 3, 2022, led by Bessemer with Insight participating. No Series D or IPO filing exists as of July 2026, so the $1.1B mark is over four years stale. Total raised is widely cited as ~$169M, but that figure comes from aggregators rather than a primary filing.
The 2025 product rename: the Teleport Access Platform became the Teleport Infrastructure Identity Platform on February 25, 2025.
The "AI" insertion: dated by diffing Wayback Machine snapshots of goteleport.com. The December 9, 2025 snapshot reads "Teleport is the Infrastructure Identity Company"; the January 4, 2026 snapshot reads "Teleport is the AI Infrastructure Identity Company". I retrieved and compared both myself. Those are the closest snapshots on either side, so the change happened inside that window. I found no announcement of it.
The DoorDash quote: the 2022 wording ("The Teleport Access Plane") is from the Series C press release, May 3, 2022. The current wording ("The Teleport Access Platform") is on goteleport.com today. I read both.
No DoorDash case study: enumerated from Teleport's case study index, which lists eighteen: PPI Financial, KnowBe4, Turo, Exness, Rush Street Interactive, GoTo, Carta, dbt Labs, TigerGraph, Buyers Edge Platform, ExtraHop, IBM Instana, thredUP, Qwilt, ECMWF, Flywheel, Gladly, Mapgears. DoorDash is absent. goteleport.com/case-study/doordash/ returns HTTP 404. The Teleport Connect 2022 agenda lists "Modernizing DoorDash's Internal Access Story with Teleport" by Luke Christopherson.
Customer quotes: each is from that company's own case study page under goteleport.com/case-study/, except Nasdaq's and DoorDash's, which survive only as homepage pull-quotes, and Carta's, which is on the SaaS use-case page. ExtraHop, KnowBe4, and ECMWF have no named individual attached to their quotes, which makes them weaker evidence than the rest. All customer quotes are vendor-published marketing and should be read as such.
The AI agent governance credit: KuppingerCole Leadership Compass "Zero Trust Platforms", document LC80980, July 13, 2026, Teleport chapter, strengths list.

Teleport Is Still Legally Named Gravitational. Every Rename Since Tells You Where The Money Moved.

2015: the planet is one computer

November 2020: the rename

What "actively supported" turned out to mean

The renames didn't stop

The rename that reached backwards

So why do companies actually use it?

What to take from a rename

Fact-check notes and sources

Related reading

Send a Message