Blaxel (YC X25)’s cover photo
Blaxel (YC X25)

Blaxel (YC X25)

Software Development

San Francisco, California 3,267 followers

The perpetual sandbox platform

About us

Blaxel keeps infinite, secure sandboxes on automatic standby to run AI code, while co-hosting your agents for near instant latency.

Website
https://blaxel.ai
Industry
Software Development
Company size
2-10 employees
Headquarters
San Francisco, California
Type
Privately Held
Founded
2024
Specialties
AI Agents and Developer Platform

Locations

Employees at Blaxel (YC X25)

Updates

  • Blaxel (YC X25) reposted this

    Treating every agent task as a new session works only when the task is isolated. An autonomous agent can clone a repo, install dependencies, start processes, write files, expose a preview, wait, and resume. When its environment disappears between those steps, the system keeps rebuilding the same execution context. That is why we built Blaxel (YC X25): Infrastructure for Autonomous Agents. Compute gives the agent somewhere to work. Storage keeps its state. Networking connects it to the systems it needs. The sandbox is the entry point. The infrastructure has to follow the rhythm of the agent. https://blaxel.ai/sandbox

    • No alternative text description for this image
  • Blaxel (YC X25) reposted this

    Most software experiences assume the human comes back and decides what happens next. Agents complicate that model. An agent may work for hours, pause, resume, and continue from a state the human never saw. It needs its files, processes, logs, and previews. The human needs enough continuity to understand what happened and where to step in. I think “give your agent a computer” makes this concrete. A computer is not only compute. It's a place where work happens and can be resumed. This is the product experience we're building toward at Blaxel (YC X25): the agent and human should both be able to return to the same work without reconstructing what happened. https://blaxel.ai/sandbox

    • No alternative text description for this image
  • Your coding agent should keep working when your terminal disconnects. Blaxel’s official Herdr plugin runs the agent in a persistent Sandbox while Herdr remains where you manage the local worktree. That matters when the agent is inspecting a repo, installing dependencies, running tests, serving a preview, or waiting for its next instruction. From Herdr, you can: • Review the target, settings, and files before upload. • Reconnect to the same remote session after the local terminal disconnects. • Open private application previews. • Apply a checked Git patch locally when the work is ready. A conflict leaves the worktree unchanged. Long-running agent work needs persistent execution. Moving changes back to local code still needs explicit review. If you are building coding agents that need to keep working beyond one terminal session, install it: herdr plugin install blaxel-ai/herdr-blaxel-sandbox-plugin https://lnkd.in/gA7Gpzn8

  • Congratulations to our customer Sapiom on a huge day: a $35M Series A and the launch of Sapiom Router, Sapiom Agent Studio, and Sapiom Agent Runtime. We’ve had the chance to watch Ilan Zerbib and the team build up close. They move quickly and have stayed focused on a hard problem: getting agents from demos into production with cost and control built into execution. We’re proud to support the team. A big and well-deserved milestone. Congratulations to everyone at Sapiom!

    Eleven months ago, I founded Sapiom. Six months ago, we announced our $15 million seed. Today, we are announcing our $35 million Series A, led by Dragonfly, with participation from Accel, Anthropic, Gradient, Coinbase, Operator Collective 🔆, Formus Capital, and VanEck, alongside continued support from existing investors including Okta Ventures, Menlo Ventures, and Array Ventures, bringing total funding to $50 million. Alongside the round, we’re revealing what we’ve spent those eleven months building: Sapiom Router, Sapiom Agent Studio, and Sapiom Agent Runtime Every tool humans have ever built was designed for a human operator. For the first time, software can be the operator. Agents are deciding which tool to use, which service to call, and which action to take next on their own. Almost none of our software or financial infrastructure was built for that. Today, anyone can build a capable agent demo in a weekend. Getting it to run reliably at scale, at a cost the business can sustain, is much harder. Before moving to Sapiom, one customer running thousands of agents asked what should have been a reasonable question: How many agents ran yesterday, and what did they cost? The answer was $12,000, but nobody knew what it had paid for. They could not see which agents ran, which tasks succeeded, where agents got stuck, or how many times they retried the same failed step. Sapiom is production infrastructure for AI agents. It sits at the exact moment an agent is about to act. For every action, Sapiom selects the best allowed path across models, compute, tools, and services based on cost, performance, permissions, and the boundaries the business has set. Because we run our own inference stack on dedicated GPUs, you get the most affordable path while also keeping your data in the US. Budgets and permissions are enforced before anything runs, and every step is recorded with its cost and outcome. - Sapiom Router lowers what you pay per call by matching every call to the right model instead of defaulting to the most expensive one. It takes two lines of code to try against agents you're already running. - Sapiom Agent Studio is where builders create, test, inspect, and deploy agents as real code inside the coding environment they already use. - Sapiom Agent Runtime is the production infrastructure where those agents run, recover from failures, access outside capabilities, and operate within the boundaries you set. In our first six months, Sapiom has processed more than 270 million transactions across more than 100,000 daily agent runs. One customer reduced its inference costs by 75%. We're starting with cost because that's where the economics break first. Our ambition is to remove everything standing between builders and the next trillion agents. Bring the agents you already have, or start fresh. Your first agent can be running on Sapiom in under 10 minutes.

  • Blaxel (YC X25) reposted this

    Excited to welcome Aarjav Patni to the Blaxel team! 🎉 Aarjav joins us as an intern with a background in Computer Science and Mathematics from the University of Waterloo, having previously worked across full-stack and infrastructure engineering at fast-paced startups. Large-scale distributed systems are Aarjav's favorite thing, and he's already dived headfirst into Agent Drive, our distributed filesystem for AI agents, focusing on performance optimizations that create impact at scale. Welcome aboard, Aarjav - we're thrilled to have your talent and energy on the team!

    • No alternative text description for this image
  • View organization page for Blaxel (YC X25)

    3,267 followers

    What we like most about this benchmark is that nobody has to take our word for it. StarSling (YC X25) built it during their EC2 migration and has now open sourced the full harness. We’re proud Blaxel (YC X25) was the only provider to rank in the top two across all six measured dimensions. Now any team can inspect the methodology, rerun the tests, and see how the results hold up for their own workload.

    Last month we migrated all our workloads from AWS EC2 to sandboxes running microVMs, and it was a large undertaking. One of the biggest challenges was that we couldn’t find a reliable benchmark that actually measured sandbox performance for real workloads. They all focused on cold start times. We care about how long it takes for dependencies to install, artifacts to build and tests to complete. We had to build our own benchmarks internally to understand real world performance so we’re open sourcing what we built so that anyone can now do the same benchmarking for high performance workloads! Huge shout out to all the sandbox providers doing the hard work of abstracting away all the infra complexity: Blaxel (YC X25), Daytona, E2B, Modal and Novita AI. Special thank you to Paul S., Ivan Burazin and Junyu Huang for being awesome partners and helping to keep StarSling reliable for all our customers! Full details here + repo link in the blog post below 📈 https://lnkd.in/gqvR9bx9

  • New: Blaxel Agent Drive. Our biggest product since we launched sandboxes. It is a shared filesystem for AI agents. Mount Agent Drive to multiple sandboxes at the same time. Write a file in one, read it instantly from another. Full concurrent access. Agent Drive is fully durable, and it scales elastically with no capacity limits. Most importantly, it is purpose-built for agentic workloads: small-to-medium files, high R/W concurrency. First beta-testers report 5-10x better performance vs. S3-backed alternatives. Available now in private preview. Join the waitlist in the comments.

    Blaxel Agent Drive (Short)

    https://www.youtube.com/

  • Blaxel (YC X25) reposted this

    Agent Drive is the product I’m most excited about since we launched Blaxel. Why? A sandbox gives an agent compute. But compute is only one part of the environment. When agents work across multiple sandboxes, they also need storage that persists beyond a run and can be accessed concurrently. This is Agent Drive: a shared filesystem you can mount to multiple sandboxes with concurrent read-write access. Write a file in one sandbox, read it from another. Without it, teams either start every session from scratch or build export and import pipelines around object storage. Agent Drive removes this handoff. It's in private preview. If your agents need to share context across sandboxes, I’d love to hear what they need to share. Demo: https://lnkd.in/eptqpR82 Docs: https://lnkd.in/eTTS8Aa6

    Blaxel Agent Drive (Short)

    https://www.youtube.com/

Similar pages