> We believe the missing layer is a durable session around the work itself

Curious as to how this will be different than K8s?

This sounds like given a coherent structure to “I want the prod code here to change the retry policy so pending retries are held in memory in this edge layer instead of the DB writers so load can be shed more cheaply” and it will usher things in from coding, testing, filing tickets, getting prod approvals, using the deploy tools to respond the containers, smoke testing the deploy, looking at Datadog or whatever to ensure the change is having the desired effect. All in one context, the tools and dev/qa/prod systems naturally being orchestrated within the same environment/ session. K8s is just the next to last 100 meters.

▲

bjt 4 hours ago | parent | prev [-]

I'm curious from the other direction; where do you see overlap between k8s and what's described on the Superlogical website?

	▲	jollyllama 4 hours ago \| parent \| next [-]
		Doesn't K8s already practically provide a layer of abstraction across all infrastructure? You might not think of it as being a session, but to the degree that it's responsible for managing scaling and failover, it kind of is. This isn't a statement of value, I'm genuinely curious myself. In fact, I bet this new thing will probably be better.
	▲	pphysch 4 hours ago \| parent \| prev [-]
		> For us, that means interactive work, automatic work, and production work would share one well-crafted underlying system instead of living in separate tools. Unless this is only for the narrow band of purely local work, I would be surprised if k8s didn't play a big role in the backend solution. It is the standard "well-crafted underlying system" for automatic production work. But, it isn't strong in the interactive-work/frontend aspect or other aspects, so it certainly wouldn't be the main focus of the final product. Random example: you want to multiplex some work across multiple (self-hosted) agents, using niche fine-tuned models. It would make good sense if those agents were automatically provisioned and deprovisioned (and isolated to your subtenant), and k8s is a great underlying system for that sort of thing.