vishnukool

Agent37 also has full VM sandboxes as an option.

No we have sufficient reserve and new workspaces have limits on how many they can spawn till they add more spend.

A relay would be the right way of doing it. But for now we haven't taken on that complexity. So for cases like this just use our default sandbox and leave it on.. and you still only pay around $4.76 for a whole month..

For most cases where customers need control over that, there's other more useful levers, like their own web app where chat happens or something similar, where they can just intentionally wake it.

So as a user you have the choice of running tools/browsers etc. in the same VM. We don't currently offer a separate browser specific VM, but it really is upto the user on what they bundle into a sandbox.

Compared to any other sandbox provider I'm aware of agent37 is an order of magnitude better in price/performance ratio for any given task.

Our own scheduler. We strongly considered kubernetes, but it wasn't worth taking on that complexity. Part of the reason to not go with kubernetes was also the need to customize all these things around sandbox placement, managing live migration based on host resource utilization etc. which is all custom.

It's low for the default sandbox type, regardless of the template or custom image. What I find though is 80% of the times these are good enough.

But for the cases where you want Docker under Docker, KVM, kubernetees or android emulator etc. we added a new class that's both performant and supports these.

It's the same fore free vs paid users, around 200-300 ms if it's warm. The free users are only limited by number of hours we give per week. And often if they're a regular user it's still warm

Cold depends on the storage size. So a few seconds on average if it's not too big

We use gvisor and cloud hypervisor depending on the use case, which manages these things pretty well by default.

thank you!

If a host reaches critical memory, then it will start restarting memory heavy sandboxes, but it's own us to relieve pressure on such hosts by moving the new ones and sleep awake one's off of it.

So the 5-10 cents price is not achieved because of sandbox density, it's because we limit the number of awake hours a free user gets per week. Right now it's about 10 hrs/wk and it's quite managable.

It depends on how frequently your sandbox is awake. We do provision large disks so that warn boot time is directly from NvME disk and if it's warm, the coldstart is under a second.

But if it's rarely used then it's slower when it has to come from cold object storage.

Yes considering doing that, just haven't had the time to focus on it, among everything else, but it's in the cards.

Yes, I'll just offer you free credits meanwhile. Ping on the website chat and mention you were from hackernews.