Similar primitive, but with two fundamentally different architectural trade-offs.
Sprites are fantastic for persistent, hardware-isolated sandboxes. But to achieve those instant creation speeds, they start from a minimal base Linux environment rather than a standard OCI image.
herd solves the same problem (sub-second Firecracker cold boots) but optimizes for a different workflow:
I wanted to keep the standard Dockerfile developer experience. herd uses a containerd devmapper pipeline to instantly carve out copy-on-write snapshots directly from standard OCI images. You get the microVM isolation and speed, but you bring your existing containers.
Sprites are a managed cloud primitive. herd is built as an embeddable control plane, it's a single Go binary you can deploy directly onto your own servers or inside an air-gapped enterprise VPC.
It's the same core Firecracker magic, just optimized for teams who want to keep their Dockerfiles and own their metal.
- Building a Retool/Looker alternative for internal tools so non-technical teams can build their own without creating busywork for engineers.
- Works like Lovable/Replit with two differences: Got 3,000 integrations out of the box through Pipedream SDK and got access controls in place with embedded auth, backend (django) and database
Analysis done with Claude Code and then Codex to verify. Each agent was given API keys in free tiers to play around and test the sandboxes for various things.
Fair point the README focuses more on benchmarks than implementation here's the short version:
1. Use `git ls-files` instead of walking the filesystem (huge speed win - dropped Chromium 59GB scan from 6.6s to 0.46s)
2. Parse each file path into components (folders, filename, extension)
3. Score each file based on how query terms match path components, weighted by position and depth
4. Return top N matches sorted by score
The core insight: /services/stripe/webhook.handler.ts already encodes the semantic relationship between "stripe" and "webhook" through its structure. No need to read file contents or generate embeddings.
I should add an architecture doc to the repo, thanks for the nudge.
There was an old legendary HN comment around the following concept:
"All things being equal, people buy from their friends. So just make more friends"
If you are confident of your services, just make more friends. Talk to people more. If it is too salesly already, you lost the conversation. Instead try and learn about their lives. I sometimes even open up with "No agenda to sell, genuinely curious"
Note: If anyone finds the link to the comment, please drop it here to credit the author.
reply