Activeloop

1.4K posts

Activeloop banner
Activeloop

Activeloop

@activeloop

Building Deeplake: the GPU-native, sandboxed Postgres for AI agents.

Mountain View, CA Katılım Nisan 2020
200 Takip Edilen4.1K Takipçiler
Sabitlenmiş Tweet
Activeloop
Activeloop@activeloop·
One session ends → poof. Everything important disappears. A teammate cracks a brutal prod issue → it dies in their terminal forever. Next week you’re debugging the exact same damn problem for the third time. We were so done with it. So we built Hivemind. A shared memory layer that connects Claude Code, Codex, and OpenClaw across sessions and across the entire team. Tag the teammate who keeps debugging the same bug twice 😂
Davit@DBuniatyan

x.com/i/article/2043…

English
1
1
4
449
Activeloop retweetledi
Davit
Davit@DBuniatyan·
Engineering managers shouldn’t have to play detective every morning. But too often, that’s the job: standups get skipped tickets stay stale and status updates become a scavenger hunt. What if your tools just told you what changed? An AI layer across Claude Code, Codex, and OpenClaw could surface progress, blockers, and momentum automatically. No nagging required. You get your mornings back. Engineers feel less monitored. Everyone stays in sync.
English
1
6
8
1.1K
Activeloop retweetledi
Charly Wargnier
Charly Wargnier@DataChaz·
YOU LITERALLY JUST RUN 4 COMMANDS TO INSTALL HIVEMIND SO CLAUDE STOPS GETTING AMNESIA EVERY TIME THE TERMINAL CLOSES. AND IT'S FREE & OPEN-SOURCE! NOW GO BUILD!
Davit@DBuniatyan

x.com/i/article/2043…

English
7
30
91
52.2K
Activeloop
Activeloop@activeloop·
One session ends → poof. Everything important disappears. A teammate cracks a brutal prod issue → it dies in their terminal forever. Next week you’re debugging the exact same damn problem for the third time. We were so done with it. So we built Hivemind. A shared memory layer that connects Claude Code, Codex, and OpenClaw across sessions and across the entire team. Tag the teammate who keeps debugging the same bug twice 😂
Davit@DBuniatyan

x.com/i/article/2043…

English
1
1
4
449
Activeloop
Activeloop@activeloop·
Jack's right: "Companies move fast or slow based on information flow." But framing it as a worker hierarchy problem is losing the plot. Look at where the actual work is moving: agents. Quick history: Email got messy. Slack fixed it. Then humans kept dropping balls anyway. Someone's offline, a thread dies, marketing has no idea what eng shipped, the handoff never happens. And now Slack itself is the slog. What if you could spend a fraction of the time in it? Meanwhile, your agents are in the pre-Slack era: • Your Claude Code agent has no clue what your coworker's OpenClaw agent decided yesterday. • Marketing's agent can't see what sales's agent promised the customer. • Product's agent has no idea what engineering's agent already shipped. Same company, same project, totally separate brains. The fastest workers on your team are stuck on the slowest part of your stack. Deeplake Hivemind fixes it. One install and your agents share memory across sessions, across teammates, across tools: Claude Code, OpenClaw, Codex, whatever. When one agent learns something, every agent on your team knows. No Slack pings. No status updates. No "wait, did you tell the VP?" Just shared context, flowing automatically. Slack was for humans. Hivemind is for the things actually doing the work now. Comment HIVEMIND and we'll DM you $100 in free credits. Run the experiment with your crew.
jack@jack

x.com/i/article/2038…

English
1
4
10
626
Activeloop
Activeloop@activeloop·
A banger post by our CTO @khustup on how he made Postgres Serverles and spin up under second. We built a serverless, PostgreSQL-compatible database. Not a modified PostgreSQL deployment. PostgreSQL provides the interface. DuckDB provides the query execution. Deeplake provides the storage engine. The architecture makes a different set of tradeoffs than traditional PostgreSQL. We think those tradeoffs are right for agent workloads: bursty, ephemeral, storage-heavy, and analytical. Link: deeplake.ai/blog/serverles…
Activeloop tweet media
English
0
0
9
520
Activeloop
Activeloop@activeloop·
Robots have been stuck reacting. Not understanding the real world. That’s the bottleneck in last-mile delivery. We combined Deeplake GPU database with Intel Core Ultra to power real-time VLA perception. Result: 9x higher throughput. Robots that don’t just see, but act intelligently. Physical AI just crossed a threshold.
Intel Business@IntelBusiness

The path to solving last-mile delivery is built on real-time perception. With #IntelCoreUltra Series 3 processors and @activeloop’s Deep Lake GPU database, Pinkbot increased VLA throughput by 9x and improved delivery outcomes. Learn more about Intel Core Ultra Series 3 at ms.spr.ly/6015QcFpT

English
0
0
2
214
Activeloop
Activeloop@activeloop·
Your agents are drowning in quicksand. Every read/write is unsafe. Every schema is fragile. Every “memory” system breaks at scale. We built Deeplake so every agent gets: → its own sandboxed database → infinite, multimodal memory → scale to zero infra Give your agents a sandbox.
Davit@DBuniatyan

x.com/i/article/2033…

English
0
0
4
292
Activeloop
Activeloop@activeloop·
Deeplake now is GPU pilled. Excited to announce The GPU Database!
Davit@DBuniatyan

Jensen just announced the start of the GPU-accelerated database era at #GTC26. AI runs on GPUs. But your data still runs on CPUs. That mismatch is breaking the AI stack. For the last two months, we’ve been busy solving this problem. Excited to announce Deeplake becoming the GPU Database. Deeplake brings your database directly onto the GPU, eliminating the CPU <-> GPU bottleneck for AI workloads. The pendulum has switched. GPU-native queries are now 10× faster and an order of magnitude cheaper to run. Last week we even put up a 101 banner in San Francisco. And this is just the beginning. We’re planning a huge set of announcements starting this week. Stay tuned.

English
0
2
8
474
Activeloop
Activeloop@activeloop·
@DBuniatyan I am now autonomous! can I get access to Moltbook?
English
1
0
1
190
Activeloop
Activeloop@activeloop·
We did not expected those results. Built a Software Factory and run it for 15 hours autonomously on our large Deep Lake codebase. Output was 83 lines of highly optimized C++ code. 714 lines of tests. 8:1 test to code ratio. It fixed the bottleneck in a large codebase. Improved the TPC-H benchmark 2x. Verified memory leak using ASAN. Spent $160 of LLM calls. Not just vibe coding. Building autonomous distributed systems is now possible. I describe how we do it below, but it requires sophisticated engineering to build your loop.
Davit@DBuniatyan

x.com/i/article/2016…

English
0
1
3
348