IT AI Index
Index Vendors › HashiCorp Boundary · September 2026 Edition
1 category · Named, not ranked

HashiCorp Boundary

13Judge labels
1First choices
2Negative labels
7 of 12Models named it
1Category
September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.
Standing
8 labels, too few to rank
A product needs 10 labels in a category before a share or quadrant is stated. HashiCorp Boundary was named 8 times in PAM, where ManageEngine PAM360 led with 21%. The labels and the evidence are below, counted exactly.
By buyer segmentRead the same way at every buyer size.
In pam · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named HashiCorp Boundary for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
CategoryFunctionShareRankNegative rateLabelsQuadrant
Privileged access managementIdentity and access0%17 of 7412%8under 10 labels · led by ManageEngine PAM360 at 21%

Movement

This is the first edition on this tier, so no move can be computed for HashiCorp Boundary yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated HashiCorp Boundary across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.
ModelFirst choiceAlternativeMentionNegativeLabels
Claude Haiku 4.500101
GPT-5.4 mini00000
Gemini 3.5 Flash00000
Perplexity Sonar00112
Grok 4.1 Fast00202
Mistral Small01001
DeepSeek V4 Flash01102
Llama 4 Maverick00000
Qwen 3.7 Flash00000
Kimi K200000
GLM 4.7 FlashX00000
MiniMax M2.500000

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct0 labelsNone
Paraphrase0 labelsNone
Comparative6 labelsNone
Budget-constrained5 labels1
Scale-constrained0 labelsNone
Negative2 labelsNone
First choiceAlternativeMentionNegative13 labels in all, every segment counted; 1 of the 1 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“For DevOps/cloud-native teams: Teleport or HashiCorp Boundary.” Mistral Small · PAM · comparative prompt · alternative
“Boundary fits teams already running HashiCorp Vault/Terraform” DeepSeek V4 Flash · PAM · comparative prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“better fits for ephemeral access, secrets, and modern infrastructure than for broad legacy PAM coverage” Perplexity Sonar · PAM · negative prompt · soft negative

Named alongside

The products named in the same answers as HashiCorp Boundary, over the 13 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and HashiCorp Boundary was named but was not.
ProductSame answerTook the first choice insteadHead to head
Teleport11 of 132Not in the top three
Delinea9 of 130Not in the top three
CyberArk7 of 134Not in the top three
BeyondTrust7 of 131Not in the top three
KeeperPAM7 of 131Not in the top three
ManageEngine PAM3607 of 131Not in the top three
StrongDM6 of 130Not in the top three
JumpServer4 of 132Not in the top three
JumpCloud4 of 130Not in the top three
One Identity Safeguard4 of 130Not in the top three
A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named HashiCorp Boundary. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 13 of the 13 answers that named HashiCorp Boundary and are not a share of its labels.

Domains cited

startwithidentity.com10
expertinsights.com7
aimultiple.com6
gartner.com6
cybervendorguide.com5
pamcost.com5
cybersectool.com4
heimdalsecurity.com4
jumpserver.com4
learn.g2.com4

Fifty-five of the fifty-five domain citations in answers naming HashiCorp Boundary came from somebody else's page.

Pages cited

Pages are listed as the models cited them.

Names read as HashiCorp Boundary

What the judge wrote, as written, with how often. The vendor table decides that these count as HashiCorp Boundary; a claim can dispute any of them.
Boundary 1HashiCorp Boundary Community 1HashiCorp Vault/Boundary 1
Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when HashiCorp Boundary's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as HashiCorp Boundary, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at hashicorp.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.

Subscribe to the pack