bem (@bem_hq) / X

bem

285 posts

bem

@bem_hq

Production infrastructure for unstructured data. Transform any document into structured, decision-ready data with composable AI functions.

San Francisco, CA

Joined November 2023

bem
@bem_hq
Jun 10
The same entity, under different names, across your corpus, on one record. A business ontology that assembles itself, no project to staff.
57
bem
@bem_hq
Jun 10
Then your agent traverses all of it with Unix verbs. ls, grep, cat, find, xref. Every file access enhanced by the graph underneath. Answers trace to document, page, section.
53
bem
@bem_hq
Jun 10
Memory, built in. Not bolted on. Walk a real one: bem.ai/walk-the-graph… Docs: docs.bem.ai/guide/file-sys… Launch: bem.ai/log/agentic-fi…
45
bem
@bem_hq
Jun 1
- N-way: 2, 3, 10 documents in one call, no shared layout needed - Visual lineage: every field traces to its source doc, page, and region - Accurate: conflicting values reconciled, your schema enforced - Evals + confidence: measured on your documents, not a vendor benchmark
39
bem
@bem_hq
Jun 1
Replying to @bem_hq
This is the foundation for verified AI: a path back to the source a human can walk, now across every document a record is built from. We are at Snowflake Summit 26 this week. What would you join first?
48
bem
@bem_hq
Jun 1
Technical writeup + the real reconciliation example:
Launching Data Join: Many Documents, One Record | bem
From bem.ai
14
bem
@bem_hq
May 22
Destinations matter as much as sources. Every bem workflow can terminate in a Send node: Drive folder, S3 bucket, or webhook. The systems your team already uses become the destinations of your pipelines. bem.ai/log/integratio…
00:00
48
bem
@bem_hq
May 21
The default pipeline today is a cron, a Lambda, or a person. Each is small infrastructure someone has to own. Most teams pay the tax three times before they stop noticing. Integrations remove it. bem.ai/log/integratio…
00:00
25
bem
@bem_hq
May 20
Setup: one workflow, one Connector, one folder. From that moment, every file in that folder fires the workflow automatically. No polling, no Lambda, no glue. Full walkthrough: bem.ai/log/integratio…
00:00
59
bem
@bem_hq
May 19
How to set up bem Integrations in three clicks per side. Settings, Integrations, Set Up. Add the connector to your workflow. Add a Send node. Done. Full walkthrough: bem.ai/log/integratio…
00:00
24
bem
@bem_hq
May 19
Point a workflow at any folder. New files trigger the workflow automatically. bem subscribes to the provider's native event stream. No polling. No Lambda. No custom event glue.
12
bem
@bem_hq
May 19
Every workflow can terminate in a Send node. Push structured output back to a Drive folder, an S3 bucket, or a webhook. The systems your team already uses become the destinations of your bem pipelines.
12
bem
@bem_hq
May 19
GA for every bem account today. Read the launch post:
Product Launch: bem Integrations | bem
From bem.ai
6
bem
@bem_hq
May 13
$690B in data center spending, built on one premise. That premise is getting shakier by the week.
00:00
88
bem
@bem_hq
May 8
Every deal shows the full email thread, AI summary, confidence score, and action items. Full provenance. Bem Labs AI CRM. Open source. github.com/bem-team/bem-c…
00:00
58
bem
@bem_hq
May 7
Your pipeline, populated by email. Zero data entry. Bem Labs AI CRM is open source. github.com/bem-team/bem-c…
00:00
64
bem
@bem_hq
May 6
Introducing Bem Labs. Our first open source project: AI CRM. An ambient CRM that reads your Gmail and maintains your pipeline automatically. Zero data entry. Built by @EthanMui on Bem's API primitives. MIT licensed. github.com/bem-team/bem-c…
00:00
69
bem
@bem_hq
May 5
Launching bounding boxes. Every extracted field now includes the exact page coordinates of its source. One flag. Works on every Extract function. Your users can click any value and see it highlighted on the original document. Provenance, not just extraction.
34