5 ms·

Steamship is Heroku for LLM apps. We're working on the mechanics of deploying and scaling all the amazing prompt-based backends everyone is building --- chaini

by eob 4y ago

Steamship is Heroku for LLM apps. We're working on the mechanics of deploying and scaling all the amazing prompt-based backends everyone is building --- chaining, prompt-search-prompt, image & audio generation. This link is a simplified hosting harness we built building & launching a Python + Prompt API endpoint.

icey 4y ago
This looks slick! You can generate images and audio with this?!? Seems a lot faster than doing it myself
- eob 4y ago
  Working on it! Right now our examples are pretty simple. But you can chain prompts manually and/or pull in services like DALL-E or voice gen. We're working on the rails to do that in a way that'll scale well cleanly across API users of your app.
terpimost 4y ago
The thing which could be a great offer is ability to supply data. I’m not sure if it involves up training or something else. Imagine I have a bunch of documents and I want answer to be based on my data.
- eob 4y ago
  That "Ask the Bible" service that went viral the other day on Twitter had me thinking the same thing. Especially for the set of problems with "Step 1: Hosting embeddings for some large corpus", it feels like there's a really useful role for offering static query/AKNN search atop popular datasets.
  - crosen99 4y ago
    Here’s a company doing that: https://www.usemeru.com/ https://www.usemeru.com/
jadbox 4y ago
How do third-party API services (me) earn? Otherwise as a developer, I'm providing a free service to users, and yet I'm paying steamship's hosting costs. Please provide an alternative to ShipQL or just drop it entirely. Most developers I know are very allergic to learning new company-specific DSLs.
- eob 4y ago
  Re: earning -- 100%. We'd love to talk to you if you've got thoughts / requests (crew@steamship.com). Re: DSLs -- what's the famous saying? "All services that survive eventually grow large enough to re-implement email"? :) We hear you though; if there's a way to support a standard QL atop the domain we're serving, we'll give it a good look.
- dkolas 4y ago
  The query problem is hard. If we provide a DSL, someone has to learn the DSL, which no one likes. If we provide you some standard QL, we still have to explain what parts of it are supported / unsupported, and how it applies to our specific data model. We started with a small DSL and will have to see how people want to use it. Thanks for the feedback!

by eob 4y ago

icey 4y ago

This looks slick! You can generate images and audio with this?!? Seems a lot faster than doing it myself

eob 4y ago
Working on it! Right now our examples are pretty simple. But you can chain prompts manually and/or pull in services like DALL-E or voice gen. We're working on the rails to do that in a way that'll scale well cleanly across API users of your app.

terpimost 4y ago

The thing which could be a great offer is ability to supply data. I’m not sure if it involves up training or something else. Imagine I have a bunch of documents and I want answer to be based on my data.

eob 4y ago
That "Ask the Bible" service that went viral the other day on Twitter had me thinking the same thing. Especially for the set of problems with "Step 1: Hosting embeddings for some large corpus", it feels like there's a really useful role for offering static query/AKNN search atop popular datasets.
- crosen99 4y ago
  Here’s a company doing that: https://www.usemeru.com/ https://www.usemeru.com/

jadbox 4y ago

How do third-party API services (me) earn? Otherwise as a developer, I'm providing a free service to users, and yet I'm paying steamship's hosting costs. Please provide an alternative to ShipQL or just drop it entirely. Most developers I know are very allergic to learning new company-specific DSLs.

eob 4y ago
Re: earning -- 100%. We'd love to talk to you if you've got thoughts / requests (crew@steamship.com). Re: DSLs -- what's the famous saying? "All services that survive eventually grow large enough to re-implement email"? :) We hear you though; if there's a way to support a standard QL atop the domain we're serving, we'll give it a good look.
dkolas 4y ago
The query problem is hard. If we provide a DSL, someone has to learn the DSL, which no one likes. If we provide you some standard QL, we still have to explain what parts of it are supported / unsupported, and how it applies to our specific data model. We started with a small DSL and will have to see how people want to use it. Thanks for the feedback!