strakedata

8 posts

strakedata

strakedata

@strakedata

The AI data layer. A sandboxed execution environment where agents meet your data

Katılım Ocak 2026
27 Takip Edilen1 Takipçiler
strakedata
strakedata@strakedata·
"agents that should 'just work on a laptop' shouldn't need to ship a database container." Total agree about embedded databases for agents! Also, there is a need for sandboxed and governed access for agents that strake brings to the table.
English
0
0
0
10
strakedata
strakedata@strakedata·
Strake v0.2.4 is live! Rust 2024 edition, one GenericSqlConnector unifying all SQL dialects. Hardened secrets, async circuit breakers, and granular schema drift detection. Cleaner architecture, safer code. github.com/strake-data/st…
strakedata tweet media
English
0
0
0
15
strakedata
strakedata@strakedata·
@levie This post perfectly describes why we think agents need an "ai data layer". They need sandboxes with code execution, pushdown optimization, and isolation. Not a simple query tool but a high performance infrastructure layer where agents actually process data.
English
0
0
0
28
Aaron Levie
Aaron Levie@levie·
It’s wild to think about what types of infrastructure and services must change in a world where agents can process information a hundred or a thousand times faster than humans. Even the tools that were built for machine speed before, generally were still in service of end-users making a request somewhere in the system. Agents running 24/7 and in parallel modify these requirements meaningfully. Here are just a few examples: * Sandboxes. Agents need sandboxes to operate in that have to be insanely low latency because they can boot up these environments for coding at any moment. * Search (both publicly and within an enterprise). Agents can parallelize searches hundreds or thousands of times so they need to be able to work with fast indexes of information. * Payments. Agents can now pay in micro transactions, and aren’t bothered by the friction of paying $0.01 for a resource that a human would be. * File systems. Agents need to be able to work with files at a scale that humans never had to worry about. You’ll have all new complexity around version control, permissions, and having agents reading/writing from data at insane speeds. And there are tons more. We’re going from a word where software was built for people to a world where it’s built for agents. Lots of changes downstream as a result.
vitrupo@vitrupo

Jeff Dean says we’re going to have to re-engineer our tools because they were designed for human speed. An AI agent can run 50x faster, but the tools it relies on don’t. So even if the model gets infinitely fast, you only get 2-3x improvement overall. Amdahl’s law still applies.

English
65
43
314
103.2K
strakedata
strakedata@strakedata·
MCP is powerful but has a scaling problem: tool definitions and data rows explode your context window. We built Strake around the "code execution pattern". Agents write code to interact with MCP servers, process data locally, return only what matters. strakedata.substack.com/p/stop-sending…
English
0
0
0
29
strakedata
strakedata@strakedata·
Strake is the AI data layer: sandboxed Python execution on live data. No ETL, just zero-copy. This DevOps agent demo correlates SQL, Parquet, JSON, CSV, and APIs without pipelines. Plans before it acts. Runs code where your data lives. #mcp #agenticai github.com/strake-data/st…
strakedata tweet media
English
0
0
0
42