splitter VS spawner

We've been building devtools for years now. We're really passionate about the field. The most recent thing we built is https://usedevbook.com. The goal was to build a simple framework/UI for companies to demo their APIs. Something like https://gradio.app but for API companies. It's been used for example by Prisma - we helped them build their playground with it - https://playground.prisma.io/

Our new project - e2b - is using some of the technology we built for Devbook in the past. Specifically the secure sandbox environments where the AI agents run are our custom Firecracker VMs that we run on Nomad.

You can follow my co-founder, me, and the project on Twitter:

- https://twitter.com/e2b_dev

- https://twitter.com/t_valenta

- https://twitter.com/mlejva

And we have a community Discord server - https://discord.gg/U7KEcGErtQ

Hey, thanks! Not the whole website but parts of it like our SDK for creating VMs on demand and some UI components are open sourced.

we've built this interactive playground of Prisma examples as a showcase of developer hubs made with Devbook. The goal of Devbook si to allow devtools projects and companies to showcase their tool in an interactive without any hassle for the devs. Everything is prepared and configured for you.

The goal of Devbook si to allow devtools projects and companies to showcase their tool in an interactive without any hassle for the devs. Everything is prepared and configured for you.

Every code snippet is runnable and editable. You get your own database thanks to CockroachDB. The code runs in a microVM (Firecracker) that's just for you. You also have an access to the terminal and even Prisma Studio. Go ahead and play with it!

I would love to hear your feedback and I'm happy to hang out and answer any questions!

[0] https://usedevbook.com

This is really really exciting! I hope it enables more product built on top of full VMs with fast UX/DX.

I just wish I knew about this earlier because from what I read, I think we at Devbook [1] built pretty similar service for our product. We are using Docker to "describe" the VM's environment, our booting times are in the similar numbers, we are using Nomad for orchestration, and we are also using Firecracker :). We basically built are own serverless platform. I need to compare our current pricing to Fly's.

[1] https://usedevbook.com

I found DevBook which is quite useful. It doesn't solve the searching issue but it cuts down on the results you get back. Not sure if it'd be useful for you or anyone scouring the comments

Not trying to undermine op here but I've recently been using a tool called Devbooks and it's really cool. It's not a vscode extension though. It lets you search stack overflow and almost any language's/library's documentation without leaving your current window.

I recommend creating a new email account solely dedicated to your journey into coding. I also recommend getting comfortable with MDN Web Docs, Stack Overflow and this nifty software called Devbook will help. (I just hit alt+space and a search engine to stack overflow pops up).

For the “jhub but for any container that speaks HTTP” use case, you might find our Spawner project interesting: https://github.com/drifting-in-space/spawner

We don’t have a good story for volumes yet, but I’m open to ideas.

Is the appeal of isolates in this case the cold start time or the isolation? We're working on some open source infrastructure for running sandboxed (gVisor) containers on the fly from web services[1], and one of the use cases people have is serving Jupyter notebooks which seems like it might resemble your use case?

[1] https://github.com/drifting-in-space/spawner/

yes! a fellow HN user e-mailed me about his project "Spawner"

https://github.com/drifting-in-space/spawner

check out the demo: https://www.youtube.com/watch?v=aGsxxcQRKa4

Drifting in Space | Full-time | NYC | https://driftingin.space

We make Jamsocket (https://jamsocket.com/), which allows application developers to spin up and connect to server-side compute. This allows browser-based applications to do computationally-intensive things that are otherwise impossible in the browser.

We went through YC and just raised a seed round and are looking to build up our team. We are based in NYC but are open to remote for experience candidates.

Our tech stack includes Rust, NATS, Docker, Postgres, TypeScript. We have lots of fun technical problems that get into the nitty-gritty of networking and operating systems. We are excited to build a diverse team and encourage non-traditional candidates to apply.

Email [email protected] or see more details here: https://www.ycombinator.com/companies/drifting-in-space/jobs...

Hi HN, we’re Paul and Taylor, and we’re launching Drifting in Space (https://driftingin.space). We build server software for performance-intensive browser-based applications. We make it easy to give every user of your app a dedicated server-side process, which starts when they open your application and stops when they close the tab.

Many high-end web apps give every user a dedicated connection to a server-side process. That is how they get the low latency that you need for ambitious products like full-fledged video editing tools and IDEs. This is hard for smaller teams to recreate, though, because it takes a significant ongoing engineering investment. That’s where we come in—we make this architecture available to everyone, so you can focus on your app instead of its infrastructure. You can think of it like Heroku, except that each of your users gets their own server instance.

I realized that something like this was needed while working on data-intensive tools at a hedge fund. I noticed that almost all new application software, whether it was built in-house or third-party SaaS, was delivered as a browser application rather than native. Although browsers are more powerful than ever, I knew from experience that industrial-scale data-heavy apps posed problems, because neither the browser or a traditional stateless server architecture could provide the compute resources needed for low-latency interaction with large datasets. I began talking about this with my friend Taylor, who had encountered similar limitations while working on data analysis and visualization tools at Datadog and Uber. We decided to team up and build a company around solving it.

We have two products, an open source package and a managed platform. Spawner, the open source part, provides an API for web apps to spawn a session-lived process. It manages the process’s lifecycle, exposing it over HTTPS, tracking inbound connections, and shutting it down when it becomes idle (i.e. when the user closes their tab). It’s open source (MIT) and available at https://github.com/drifting-in-space/spawner.

Jamsocket is our managed platform, which uses Spawner internally. It provides the same API, but frees you from having to deal with any cluster or network configuration to ship code. From an app developer’s point of view, using it is similar to using platforms like Netlify or Render. You stay in the web stack and never have to touch Kubernetes.

Here's an example. Imagine you make an application for investigating fraud in a large transaction database. Users want to interactively filter, aggregate, and visualize gigabytes of transactions as a graph. Instead of sending all of the data down to the browser and doing the work there, you would put your code in a container and upload it to our platform. Then, whenever a fraud analyst opens your application, you hit an API we provide to spin up a dedicated backend for that analyst. Your browser code then opens a WebSocket connection directly to that backend, which it uses to stream data as the analyst applies filters or zooms/pans the visualization.

We're different from most managed platforms because we give each user a dedicated process. That said, there are a few other services that do run long-lived processes for each user. Architecturally, we're most similar to Agones. Agones is targeted at games where the client can speak UDP to an arbitrary IP; we target applications that want to connect directly from browsers to a hostname over HTTPS. In the Erlang world, the OTP stack provides similar functionality, but you have to embrace Erlang/Elixir to get the benefits of it; we are entirely language-agnostic. Cloudflare Durable Objects support a form of long-lived processes, but are focused on use cases around program state synchronization rather than arbitrary high-compute/memory use cases.

We have a usage-based billing model, similar to Heroku. We charge you for the compute you use and take a cut. Usage billing scales to zero, so it’s approachable for weekend experiments. We have not solidified a price plan yet, but we’re aiming to provide an instance capable of running VS Code (as an example) for about 10 cents an hour, fractionally metered. High-memory and high-CPU backends will cost more, and heavy users will get volume discounts. Our target customers are desktop-like SaaS apps and internal data tools.

As mentioned, our core API is open source and available at https://github.com/drifting-in-space/spawner. The managed platform is in beta and we’re currently onboarding users from a waitlist, to make sure that we have the server capacity to scale. If you’re interested, you’re welcome to sign up for it here: https://driftingin.space.

Have you built a similar infrastructure for your application? We’re always interested in hearing the approaches people have already taken to this problem and learning what their pain points are.