Cybersecurity · head to head
Authelia vs HashiCorp Boundary

Authelia
Cybersecurity
Open-source authentication and two-factor portal for reverse proxies
- From
- Free
- Rated
- -

HashiCorp Boundary
Cybersecurity
Identity-aware session broker for infrastructure access without distributing credentials
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Authelia depends on a reverse proxy: it is not a standalone identity provider; HashiCorp Boundary hashiCorp was acquired by IBM in February 2025 and Enterprise licensing now runs through IBM Passport Advantage; IBM has already retired HCP Vault Secrets, so Boundary's roadmap depends on IBM portfolio decisions rather than HashiCorp's own product strategy.
- They diverge on capability: Authelia covers Reverse proxy integration, HashiCorp Boundary covers Identity-based access.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Authelia and HashiCorp Boundary actually diverge.
| Attribute | Authelia | HashiCorp Boundary |
|---|---|---|
| Platforms | Docker, Kubernetes, Linux, Self-hosted | Linux, macOS, Windows, Web |
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated), category (Cybersecurity).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Authelia
- Reverse proxy integration
- Two-factor authentication
- Access control rules
- Lightweight backends
Only in HashiCorp Boundary
- Identity-based access
- Just-in-time credentials
- Dynamic host catalogues
- Session recording
- Transparent sessions
- Multi-hop workers
- Audit logging
- Terraform provider
What people use each for
The jobs each tool is most often brought in to do.
Authelia
- Putting a login and 2FA in front of self-hosted services that have nonenot HashiCorp Boundary
- Adding SSO across a small set of internal tools without a full identity platformnot HashiCorp Boundary
- Home and small-team infrastructure behind a single reverse proxynot HashiCorp Boundary
HashiCorp Boundary
- A platform team replacing shared SSH keys and a bastion host so that leavers lose access the moment they are removed from the identity providernot Authelia
- Granting contractors time-boxed database access without ever issuing them a credential they could keepnot Authelia
- An estate where autoscaling replaces hosts continuously and a static access list is always out of datenot Authelia
- Producing session recordings as evidence for an audit that requires proof of who touched production and what they rannot Authelia
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Authelia
- Depends on a reverse proxy: it is not a standalone identity provider
- Configuration is YAML-first with no administrative interface, so changes mean editing files
- Not a full IAM: user management, provisioning and federation are limited compared with Keycloak
- Scales poorly as an organisation-wide identity solution, which is not its target
HashiCorp Boundary
- HashiCorp was acquired by IBM in February 2025 and Enterprise licensing now runs through IBM Passport Advantage; IBM has already retired HCP Vault Secrets, so Boundary's roadmap depends on IBM portfolio decisions rather than HashiCorp's own product strategy.
- Enterprise pricing is not published anywhere, and the features most organisations actually need for compliance, notably session recording, are Enterprise only, so the free community edition is rarely the version you end up buying.
- It solves access to infrastructure, not to applications; browser-based internal tools, SaaS admin consoles and APIs need a separate control, so Boundary is one component of a zero-trust programme rather than the whole thing.
- Running it yourself means operating controllers, worker nodes and a Postgres database in a highly available configuration, and if that control plane is down nobody can reach production, which makes it a new critical dependency.
- It is materially easier to adopt if you already run Vault and Terraform; teams without that ecosystem face a steeper learning curve than a device-based mesh product like Tailscale, for a similar access outcome.
Pricing, plan by plan
Authelia
Free- AutheliaFree
- Full functionality
- No usage limits
- Community support
HashiCorp Boundary
Free- Boundary Community EditionFree
- MPL 2.0 open source
- Self-hosted controllers and workers
- Identity-based target access
- Boundary Enterprise$undefined/year
- Session recording and playback
- Multi-hop and transparent sessions
- Multi-tenancy via scopes
Which should you pick?
Choose Authelia if
- You need reverse proxy integration.
- You want to start without paying.
- You work on Docker, Kubernetes, Linux, Self-hosted.
- You also want two-factor authentication.
Choose HashiCorp Boundary if
- You need identity-based access.
- You want to start without paying.
- You work on Linux, macOS, Windows, Web.
- You also want just-in-time credentials.
Questions people ask
- Is Authelia or HashiCorp Boundary better?
- Neither clearly leads. Authelia starts at Free and HashiCorp Boundary at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Authelia or HashiCorp Boundary?
- Authelia starts at Free and HashiCorp Boundary at Free.
- Does Authelia or HashiCorp Boundary run on more platforms?
- Authelia runs on Docker, Kubernetes, Linux, Self-hosted. HashiCorp Boundary runs on Linux, macOS, Windows, Web.
- Can I use Authelia for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Authelia best used for?
- Authelia is most often used for putting a login and 2fa in front of self-hosted services that have none, adding sso across a small set of internal tools without a full identity platform, home and small-team infrastructure behind a single reverse proxy. Of those, putting a login and 2fa in front of self-hosted services that have none and adding sso across a small set of internal tools without a full identity platform are not what HashiCorp Boundary is typically brought in for.
- What can Authelia do that HashiCorp Boundary cannot?
- Authelia covers Reverse proxy integration, Two-factor authentication, Access control rules, Lightweight backends. HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.
Answered from the vendors’ own pages
Authelia: Is Authelia free?
Yes, open source with no licence fee.
HashiCorp Boundary: Is Boundary open source?
The community edition is, under MPL 2.0. Boundary Enterprise is commercial and is now sold through IBM Passport Advantage.
Authelia: Does Authelia need a reverse proxy?
Yes. It integrates through forward authentication with Nginx, Traefik, Caddy or HAProxy rather than sitting in front of traffic itself.
HashiCorp Boundary: Does it replace a VPN?
For infrastructure access, largely yes. It grants a session to a specific target rather than putting the user on a network, but it does not cover browser-based internal applications.
Authelia: Authelia or Keycloak?
Authelia is far lighter and aimed at protecting self-hosted services behind a proxy. Keycloak is a full identity and access management platform, and much more to run.
HashiCorp Boundary: What does Boundary Enterprise cost?
HashiCorp does not publish Boundary pricing. It is quoted, and since the IBM acquisition it is transacted on IBM licensing paper.
HashiCorp Boundary: Do I need Vault to use it?
No, but the just-in-time credential brokering that makes Boundary worthwhile depends on Vault or an equivalent secrets store.
Related pages
More on HashiCorp Boundary
Other head to heads
- Authelia vs authentik
- Authelia vs Logto
- Authelia vs Ory Kratos
- Authelia vs Frontegg
- Authelia vs Infisical
- Authelia vs Bitwarden
- Authelia vs Semgrep
- Authelia vs Trivy
- Authelia vs Chainguard
- Authelia vs Passbolt
- Authelia vs 1Password
- Authelia vs Signicat
- Authelia vs Silent Eight
- Authelia vs Socket
- Authelia vs Socure
- Authelia vs SonicWall
- Authelia vs Sophos Intercept X
- Authelia vs Ory
- Authelia vs BeyondTrust
- Authelia vs Teleport
- Authelia vs Delinea
- Authelia vs LastPass
- Authelia vs Saviynt
- Authelia vs Beyond Identity
- Authelia vs One Identity
- Authelia vs Keygen
- Authelia vs KnowBe4
- Authelia vs Legit Security
- Authelia vs LogRhythm SIEM
- Authelia vs Metasploit
- Authelia vs MetricStream
- HashiCorp Boundary vs authentik
- HashiCorp Boundary vs Logto
- HashiCorp Boundary vs Ory Kratos
- HashiCorp Boundary vs Frontegg
- HashiCorp Boundary vs Infisical
- HashiCorp Boundary vs Bitwarden
- HashiCorp Boundary vs Semgrep
- HashiCorp Boundary vs Trivy
- HashiCorp Boundary vs Chainguard
- HashiCorp Boundary vs Passbolt
- HashiCorp Boundary vs 1Password
- HashiCorp Boundary vs Signicat
- HashiCorp Boundary vs Silent Eight
- HashiCorp Boundary vs Socket
- HashiCorp Boundary vs Socure
- HashiCorp Boundary vs SonicWall
- HashiCorp Boundary vs Sophos Intercept X
- HashiCorp Boundary vs Ory
- HashiCorp Boundary vs BeyondTrust
- HashiCorp Boundary vs Teleport
- HashiCorp Boundary vs Delinea
- HashiCorp Boundary vs LastPass
- HashiCorp Boundary vs Saviynt
- HashiCorp Boundary vs Beyond Identity
- HashiCorp Boundary vs One Identity
- HashiCorp Boundary vs Keygen
- HashiCorp Boundary vs KnowBe4
- HashiCorp Boundary vs Legit Security
- HashiCorp Boundary vs LogRhythm SIEM
- HashiCorp Boundary vs Metasploit
- HashiCorp Boundary vs MetricStream
