Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Presented to the TAC:  February 21, 2024

Subgroup reviewed on: February 29, 2024

Subgroup readout to the TAC: March 6, 2024

Project Proposal - Project Introduction:

Required Information

Responses (Please list N/A if not applicable)

Name of Project


Project Description (what it does, why it is valuable, origin and history)

OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. The OpenBao community intends to provide this software under an OSI-approved open-source license, led by a community run under open governance principles. This project is a fork of Hashicorp's Vault.

Statement on alignment with Foundation Mission Statement

We agree with the foundation's mission statement.

High level assessment of project synergy with existing projects under LF Edge, including how the project compliments/overlaps with existing projects, and potential ways to harmonize over time. Responses may be included both here and/or in accompanying documentation. Both Open Horizon and Edge X Foundry will incorporate/utilize OpenBao.

Link to current Code of Conduct

We will adopt LF Edge's Code of Conduct.

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

James Butcher (EdgeX Foundry)
Joe Pearson (Open Horizon)

Project license

Mozilla Public License, Version 2.0

Source control (GitHub by default)

Issue tracker (GitHub by default)

External dependencies (including licenses)

View file

Release methodology and mechanics

GitHub Releases

Names of initial committers, if different from those submitting proposal

Matthew Burket (Independent)
Jeremiah Butler (independent)

Dan Ghita (ViaAccess-Orca)
jmls (Independent)
Robert Kregloh (Independent)
Lars Lehtonen (Independent)
Jan Martens (Independent)
Nathan Phelps (IBM, Open Horizon)
Gabriel Santos (independent)
Alexander Scheel (Independent)
Andrew Scorpil (Independent)
Jasper Siepkes (Independent)
Alexander Sharov (Independent)

Current number of code contributors to proposed project13 (Independent of the contributors to the upstream Vault source or its plugins)
Current number of organizations contributing to proposed projectFive companies, two LF Edge projects
Briefly describe the project's leadership team and decision-making processOpenBao has formed it's own technical steering committee (TSC) of five founding member organizations.  While incubating under Open Horizon, it has been following their Technical Charter.

IOTech Systems
Viaccess-Orca (Orange)
List of project's official communication channels (slack, irc, mailing lists)Mailing List
GitHub Discussions
CVEs can be reported via
Link to project's website

Links to social media accounts

Existing financial sponsorshipIBM, Viaccess-Orca, and Wallix have pledged support in the form of FTE contributions.
Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...)OpenBao needs a place to host its community supported plugins. Access to development/test hardware to support other architectures (RISC-V).
Currently Supported Architecturex86/64, ARM
Planned Architecture SupportRISC-V
Project logo in svg format (see for guidelines)
Trademark statusTrademark will need to be pursed by the Linux Foundation upon project proposal acceptance
Does the project have a Core Infrastructure Initiative security best practices badge? (See:
Any additional information the TAC and Board should take into consideration when reviewing your proposal?OpenBao is an incubation project under Open Horizon and is ready to become its own standalone member project under LF Edge.

Project Proposal - Mapping Criteria and Data:

Stage 1: At Large Projects (formerly 'Sandbox')


2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

A presentation at an upcoming meeting of the TAC, in accordance with the project proposal requirements

The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board.

Upon acceptance, At Large projects must list their status prominently on website/readme

*** For existing Projects requesting Stage 2 or Stage 3 consideration, please update the above with the Stage 2 or Stage 3 Mapping criteria, available at Project Stages Mapping: Criteria and Data

Project Proposal - Taxonomy Data:

Functions (Provide, Consume, Facilitate, or N/A; Add context as needed)

Functions(Provide, Consume, Facilitate, or N/A; Add context as needed)
APIsProvide, Consume

(OpenBao provides its own API interface, and consumes other APIs via plugins included)
Cloud Connectivity


(Support provided by plugins)

Container Runtime & OrchestrationConsume
Data GovernanceProvide, Consume, Facilitate

Data ModelsProvide

Device ConnectivityN/A


(Audit and Logging APIs)

Management UIProvide
Messaging & EventsProvide
Notifications & AlertsN/A
SecurityProvide, Facilitate

(Secrets management)
StorageProvide, Consume

(Support Provided by plugins)

Deployment & Industry Verticals (Support, Possible, N/A; Add context as needed)

Deployment Type(Support, Possible, N/A; Add context as needed)
Customer Devices (Edge Nodes)Support
Customer Premises (DC and Edge Gateways)Support
Telco Network Edge (MEC and Far-MEC)Possible
Telco CO & RegionalPossible
Cloud Edge & CDNsPossible
Public CloudSupport
Private CloudSupport

Deployment & Industry Verticals (✔ or X; Add context as needed)

Directly applicable Industry/Verticals use cases(✔ or X; Add context as needed)
Automotive / Connected Car
Facilities / Building automation
Metal & Mining
Oil & Gas
Health Care
Power & Utilities
Pulp & Paper
Telco Operators
Telco/Communications Service Provider (Network Equipment Provider)
Transportation (asset tracking)
Supply Chain
Preventative Maintenance
Water Utilities
Security / Surveillance
Retail / Commerce (physical point of sale with customers)
Other - Please add if not listed above (please notify when you add one)

Deployments (static v dynamic, connectivity, physical placement) - (✔ or X; Add context as needed)

Use Cases(✔ or X; Add context as needed)
Gateways (to Cloud, to other placements)

(Public/Private Clouds)
NFV InfrastructureN/A
Stationary during their entire usable life / Fixed placement edge constellations / Assume you always have connectivity and you don't need to store & forward.N/A
Stationary during active periods, but nomadic between activations (e.g., fixed access) / Not always assumed to have connectivity. Don't expect to store & forward.N/A
Mobile within a constrained and well-defined space (e.g., in a factory) / Expect to have intermittent connectivity and store & forward.N/A
Fully mobile (To include: Wearables and Connected Vehicles) / Bursts of connectivity and always store & forward.N/A

Compute Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Compute Stack Layers(Provide, Require, or N/A; Add context as needed)
VM/ContainersN/A (Optional)

Cloud Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Cloud Stack Layers(Provide, Require, or N/A; Add context as needed)
Configuration (drive)N/A
Content (management system)N/A
Physical InfrastructureRequire

Attachments (LF Edge PPT template is below, if proposing project would like to leverage):

View file