Nhost is now running in Stockholm ๐ธ๐ช
Lower latency for Nordic users. Pick it when you create a project.
... yes, the moose is a real design decision.
Nhost is hiring an Infrastructure Engineer to own the multi-region cloud platform that every Nhost project runs on.
AWS, Kubernetes, Terraform, Go. Remote, lots of autonomy and ownership.
https://t.co/pAPu91zTC1
๐ฆ๐บ The Australia region is live!
Deploy closer to your users with Nhostโs new Sydney region.
Less latency, faster responses, happier users.
If your users are in Australia or APAC, your backend just moved a little closer. ๐
@LangChain@useapolloio Apollo ditching supervisor graphs for dynamic skill selection is the right call. multi-agent DAG routing looks clean in a demo and gets messy in prod fast
@AnthropicAI The judge meant to catch the sabotage shares the exact values that caused it, so your safety net and your failure mode are drawn from the same distribution.
@DanielLockyer Definitely still a thing. We use GraphQL at Nhost because it's a great fit for working with complex, connected data, especially when you're building agentic apps.
@LangChain Totally with you. Agents mostly assist humans today, but they're getting more and more autonomous. The infrastructure around them has to keep up.
@LangChain@bentannyhill Really like the shadow-production approach. Have you thought about running the agent against an isolated DB copy for the write-access problem instead of hand-mocking all the endpoints?
@jerryjliu0 The quiet shift here is that retrieval starts looking more like an agent exploring a filesystem: search, grep, read, follow the thread.
That's much closer to how people actually research a case
@GraphQL Good point on co-locating the fragment with the atomic component. The bit about a removed field making the dead UI obvious is the part people miss