Softwr

Government · head to head

DataSF vs HashiCorp Boundary

DataSF logo

DataSF

Government

San Francisco Open Data Portal

From
Free
Free plan
Yes
Full reviewWebsite
HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • They diverge on capability: DataSF covers Open Datasets, 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 DataSF and HashiCorp Boundary actually diverge.

Attributes where DataSF and HashiCorp Boundary differ
AttributeDataSFHashiCorp Boundary
Pricing modelfreeOpen source, no licence fee
PlatformsWebLinux, macOS, Windows, Web
CategoryGovernmentCybersecurity
Founded2009Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 DataSF

  • Open Datasets
  • Data API
  • Visualizations
  • Data Catalog
  • Automated Updates
  • Socrata
  • ArcGIS
  • Analysis Tools

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.

DataSF

  • Citizen Servicesnot HashiCorp Boundary
  • Records Managementnot HashiCorp Boundary
  • Public Safetynot HashiCorp Boundary
  • Civic Engagementnot 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 DataSF
  • Granting contractors time-boxed database access without ever issuing them a credential they could keepnot DataSF
  • An estate where autoscaling replaces hosts continuously and a static access list is always out of datenot DataSF
  • Producing session recordings as evidence for an audit that requires proof of who touched production and what they rannot DataSF

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

DataSF

Nothing recorded yet. See the DataSF review.

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

DataSF

Free
  • Public AccessFree
    • Dataset Access
    • API Access
    • Visualizations

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 DataSF if

  • You need open datasets.
  • You want to start without paying.
  • You also want data api.
DataSF review

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.
HashiCorp Boundary review

Questions people ask

Is DataSF or HashiCorp Boundary better?
Neither clearly leads. DataSF 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, DataSF or HashiCorp Boundary?
DataSF starts at Free and HashiCorp Boundary at Free.
Does DataSF or HashiCorp Boundary run on more platforms?
DataSF runs on Web. HashiCorp Boundary runs on Linux, macOS, Windows, Web.
Can I use DataSF for free?
Both have a free tier, so you can try either at no cost before committing.
What is DataSF best used for?
DataSF is most often used for citizen services, records management, public safety, civic engagement. Of those, citizen services and records management are not what HashiCorp Boundary is typically brought in for.
What can DataSF do that HashiCorp Boundary cannot?
DataSF covers Open Datasets, Data API, Visualizations, Data Catalog. HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.

Answered from the vendors’ own pages

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.

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.

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.

Share

Related pages

More on DataSF

More on HashiCorp Boundary

Keep looking

Other head to heads