ERS Weekly Update: Release Validation and the Move Toward AWS

ERS is in release validation. That means the work is less about adding features and more about confirming that what exists behaves correctly under real conditions: installing, signing in, creating and completing an errand, and handling things when they go wrong.

The move toward AWS for ERS deployment and hosting has started. It is ongoing, and we are not describing it as complete.

Hosting is a decision you live with. Moving it means revisiting infrastructure, configuration, security, monitoring, and connectivity, then validating that the release still behaves as it should afterwards. None of that is visible to a user, but all of it affects whether the product holds up.

This is additional engineering, and it affects launch timing. No launch date is confirmed, and we would rather say that plainly than offer a date we can’t stand behind.

Reliability is a property you earn through validation, not something you declare. Every layer you change is a layer you have to prove again. That slows things down, and it is the price of shipping something dependable.

ERS is our priority product, but it sits inside a wider ambition: a connected technology platform spanning software, AI, cloud infrastructure, and applications, with operating systems and devices as a long-term vision. Wanky OS is a direction we are working toward, not a product you can use today. ERS reaching production well is the foundation for everything else.

We continue the validation work, and we’ll share progress as it is verified. We will not promise dates we haven’t confirmed.

Building Wanky is a series of small, verified steps. This week’s step was foundational, and it won’t make headlines. It does make ERS more likely to work when you need it.