3 ms·

It sounds like this is providing a sandboxed wasm runtime as a service is that right? I think in this case the landing page is lacking in technical details to

It sounds like this is providing a sandboxed wasm runtime as a service is that right? I think in this case the landing page is lacking in technical details to the point where it’s hard to understand what the product actually is. I like the general idea of firecracker as a service and sandboxed code as a service though. Even the webhook example doesn’t really show where scriptable fits in, I think what you’re trying to say is that the customer can write some code to integrate the product with their slack and then the service will call the customer’s code in a sandboxed environment which is how the customer can extend the product right?

cheerioty 4y ago
You're 100% on the money here. One way to use it is to fire off user-provided scripts tied to certain events in your product, similar to webhooks. But it's also flexible and quick enough to make your product extendable in terms of UI. It's 100% deploy-less (and stateless) as well, meaning you can just through whatever code at it, and it will quickly evaluate and respond with the result.
- esperent 4y ago
  > You're 100% on the money here Why isn't this in the first paragraph of the introduction on your website?
ponyous 4y ago
This is the only comment that clarified the product to me. Everything else including the website is just confusing.
- cheerioty 4y ago
  I'm glad at least this one gave you some clarity. We surely learned our lesson regarding our messaging here today.
  - tyingq 4y ago
    The comment does make the high level clear, but it's still confusing a level down. For example, your copy suggests I can use it to allow customers to write scripts that execute based on events from my application. But what's the interface for them? Is there a UI to add/manage/monitor scripts? Is there some multi-tenant concept that keeps each of my customers isolated from another? If not, what's the value add over just using something like Cloudflare Workers for this?

cheerioty 4y ago

You're 100% on the money here. One way to use it is to fire off user-provided scripts tied to certain events in your product, similar to webhooks. But it's also flexible and quick enough to make your product extendable in terms of UI. It's 100% deploy-less (and stateless) as well, meaning you can just through whatever code at it, and it will quickly evaluate and respond with the result.

esperent 4y ago
> You're 100% on the money here Why isn't this in the first paragraph of the introduction on your website?

ponyous 4y ago

This is the only comment that clarified the product to me. Everything else including the website is just confusing.

cheerioty 4y ago
I'm glad at least this one gave you some clarity. We surely learned our lesson regarding our messaging here today.
- tyingq 4y ago
  The comment does make the high level clear, but it's still confusing a level down. For example, your copy suggests I can use it to allow customers to write scripts that execute based on events from my application. But what's the interface for them? Is there a UI to add/manage/monitor scripts? Is there some multi-tenant concept that keeps each of my customers isolated from another? If not, what's the value add over just using something like Cloudflare Workers for this?