| ▲ | echelon 2 hours ago | |
> Bedrock This sounds so enterprise. I've been wanting to talk to people that actually use it. Why use Bedrock instead of OpenRouter, Fal, etc.? Doesn't that tie you down to Amazon forever? Isn't the API worse? Aren't the p95 latencies worse? The costs higher? | ||
| ▲ | raw_anon_1111 2 hours ago | parent | next [-] | |
Given a choice between being “locked in” to a major cloud provider and trusting your business to a randomish little company, you are never going to get a compliance department to go for the latter. “no one ever got fired for choosing AWS”. This is the API - it’s basically the same for all supported languages https://docs.aws.amazon.com/code-library/latest/ug/python_3_... Real companies aren’t concerned about cost as much as working with other real companies, compliance, etc and are comparing cost or opportunities between doing a thing and not doing a thing. One of my specialties is call centers. Every call deflected by using AI vs talking to a human agent can save from $5 - $15. Even saving money by allowing your cheaper human agents to handle a problem where they are using AI in the background, can save money. $15 saved can buy a lot of inference. And the lock in boogeyman is something only geeks care about. Migrations from one provider to another costs so much money at even a medium scale they are hardly ever worth it between the costs, distractions from doing value added work, and risks of regressions and downtime. | ||
| ▲ | bangaladore 2 hours ago | parent | prev | next [-] | |
Bedrock is a lot more than just a standard endpoint. Also, the security guarantees. | ||
| ▲ | bibimsz 2 hours ago | parent | prev [-] | |
on less vendor to vet, one less contract to negotiate, one less 3rd party system to administer. you're already locked into AWS anyway. integrates with other AWS services. access control is already figured out. | ||