Nobody has a use for this, and anybody who can look at this website and work out what it's for is kidding themselves. Even the demo gif playing just has them pausing a task and resuming the task.
If there's a criticism here, it's that they don't mention k8s right up front. It's completely opaque what this tool is. "Orchestration" can mean literally anything.
The web page presents ax as a typical developer tool, but it's actually not for developers.
> Disclaimer: I'm one of the co-creators of this project and working on Kubernetes so my opinions may be biased.
We met quite a large number of customers in the last few months, and several teams inside Google, who are asking for a stack that runs on any cluster.
There are several reasons for a layer like this.
(a) Today, it's extremely hard to deliver large agentic applications to someone else's compute, and it kills adoption for products that need to run closer on customer data plane, e.g. large scale code scanning product.
(b) It's tedious to build systems that set up the environment, deal with networking policies, provide integrations for session storage, memory curation, skills retrieval and mounting, etc while all you want to do is to focus on building applications.
(c) People want a truly transparent stack for compliance/auditing, and all other non functional capabilities most people don't usually think about until they have to.
weedfroglozenge · · focus · HN ↗
hsn915 · · focus · HN ↗
mirekrusin · · focus · HN ↗
jatora · · focus · HN ↗
imtringued · · focus · HN ↗
>A Model is not a model. It is a named model configuration: ...
Remember kids, a model is not a model.
philipwhiuk · · focus · HN ↗
<a href="https://github.com/google/ax/issues/356" rel="nofollow">https://github.com/google/ax/issues/356
vehemenz · · focus · HN ↗
The web page presents ax as a typical developer tool, but it's actually not for developers.
rakyll · · focus · HN ↗
rakyll · · focus · HN ↗
We met quite a large number of customers in the last few months, and several teams inside Google, who are asking for a stack that runs on any cluster.
There are several reasons for a layer like this.
(a) Today, it's extremely hard to deliver large agentic applications to someone else's compute, and it kills adoption for products that need to run closer on customer data plane, e.g. large scale code scanning product.
(b) It's tedious to build systems that set up the environment, deal with networking policies, provide integrations for session storage, memory curation, skills retrieval and mounting, etc while all you want to do is to focus on building applications.
(c) People want a truly transparent stack for compliance/auditing, and all other non functional capabilities most people don't usually think about until they have to.