Kind of weird that it is launched as "Experiments" platform and inference is the only experiment. Wish they had made up their minds about launching this and launched it as a alpha version or smt
I did build a very similar product putting emphasis on integrations and security. It was tough to churn anyone out from Replit, Lovable and then CC and Codex.
When I talked to Lovable team, they told me Lovable is used primarily for prototyping, not internal tools and they are having a rough time trying to change the use case.
Thanks for the feedback. From what we've gathered so far, non-eng are using CC or Codex to build one-off internal tools, but they're deploying them on their personal Vercel accounts and sending the url over Slack. That's the workflow we want to replace with a reasonable level of security and auditability. We're still trying to gauge interest in using the CLI to build and having everything deploy on Prized, we're working out whether that's valuable.
Hi! I'm one of the engineers at Extend that worked on this - one of our other engineers created a Rust XLSX/XLS parser that we ported to WASM to our @extend-ai/react-xlsx package which handles the rendering/charts. It exposes some hooks so users can use their own components for the toolbar
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.