Boundary
Boundary is building BAML -- a programming language to build AI agents. We used to code in assembly, and moved on to C. From C, we moved on to higher level languages like Python. Now we are going from Python to natural language. What does the code look like when 50% of the business decisions is decided by an AI agent / prompts? How do you test these AI components? We made BAML to address these problems. BAML helps has built-in tools to test, observe, and work with structured LLM outputs / tool calling natively in the language 10x faster. With BAML you can also instantly parallelize LLM Calls, or react to certain events or changes in your pipelines, without having to write any boilerplate. It's like using 'React' for AI. BAML code can used from any other language -- providing a standardized way to organize and declare any LLM or AI code.
Vendors
0Third parties this company currently discloses, grouped by function when classified.
No disclosed vendors yet
Vendors appear only once a public disclosure or other published evidence names them.
Customers
0Companies whose current disclosures name this company as a vendor.
No observed customers yet
Customers appear when another company's current disclosure names this company as a vendor.
Potential customers
0Companies using another vendor in one of Boundary’s categories, excluding Boundary’s observed customers.
No potential customers found
Potential customers appear after Boundary has a category assignment and current vendor relationships can be compared.